When using COO UIPlugin monitoring and looking into dashboards provided, the metric naming configuration does not support OTLP scraped metrics which follow the semantic convention schema as documented in https://opentelemetry.io/docs/specs/otel/compatibility/prometheus_and_openmetrics/

Dashboards would than read

traces_span_metrics_calls 

instead of OTEL sc 

traces_span_metrics_calls_total 

A feature to toggle between OTEL semantic convention and Prometheus naming schema schould be made available to get more customers benefit of the Perses dashboards.