tempo span metric

[chenfango]

What is the difference between traces_spanmetrics_latency_count and traces_spanmetrics_calls_total

[mapno]

Hi @chenfango. Good question. traces_spanmetrics_latency_count and traces_spanmetrics_calls_total are semantically equivalent, both measure occurrences of received spans. The series traces_spanmetrics_latency_count belongs to a histogram, whereas traces_spanmetrics_calls_total is a standalone counter. We allow configuring spanmetrics subprocessors to generate one or the other metric, so both are emitted. You can read more about spanmetrics here: https://grafana.com/docs/tempo/latest/metrics-generator/span_metrics/#metrics.

[chenfango]

Hi @chenfango. Good question. traces_spanmetrics_latency_count and traces_spanmetrics_calls_total are semantically equivalent, both measure occurrences of received spans. The series traces_spanmetrics_latency_count belongs to a histogram, whereas traces_spanmetrics_calls_total is a standalone counter. We allow configuring spanmetrics subprocessors to generate one or the other metric, so both are emitted. You can read more about spanmetrics here: https://grafana.com/docs/tempo/latest/metrics-generator/span_metrics/#metrics.

Thanks for your answer. I have another question: What is the difference between the http_server_request_duration_seconds_count metric and the traces_spanmetrics_latency_count metric?

The http_client_request_duration_seconds_sum metric is generated by the opentelemetry agent. It is the number of requests to the http api. What is the difference between them?

[chenfango]

Is the span metric scope larger? Are there other metric scopes besides http?