Establish consistency in metric naming for span metrics connector

[vjsamuel]

Component(s)

connector/spanmetrics

Is your feature request related to a problem? Please describe.

span metrics connector today establishes metric names as calls_total and duration which lacks proper namespacing

Describe the solution you'd like

similar to service graph connector if we could do: traces_spanmetrics_.* for the metric names it would ensure consistency across all connectors

Describe alternatives you've considered

No response

Additional context

This would also help use the grafana service graph view when using the open telemetry collector directly.

[vjsamuel]

@jpkrohling

[github-actions[bot]]

Pinging code owners:

• connector/spanmetrics: @portertech @Frapschen

  See Adding Labels via Comments if you do not have permissions to add labels yourself.

[Frapschen]

similar to service graph connector

Can you give more context about the relate work of graph connector(issue or PR)?

[vjsamuel]

https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/connector/servicegraphconnector#metrics

as you can see here, the metrics are neatly namespaced with signal type followed by connector name and finally the actual metric.

[gouthamve]

Also see https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/32818

[Frapschen]

I agree that we need to add a component identification to the metrics name.

It's a big breaking change, we need to keep both traces_span_metrics_calls_total and calls_total for one or two releases and then remove calls_total WDYT @dmitryax