http_requests_total, http_request_duration_seconds_sum, and http_request_duration_seconds_count #4165
-
Hi there, I'm working on a polyglot system that uses OpenTelemetry/Prometheus, and there are a couple common metrics I see get generated automagically in other components.
However, when I run the OpenTelemetry ASP.NET Core 6 Example project, all I see for ASP.NET/HttpClient are http_client_duration_ms_bucket, and http_server_duration_ms_bucket. Do you know why this would be? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
http_client_duration_ms_bucket, and http_server_duration_ms_bucket. The above are expected from OpenTelemetry instrumentaion for HttpClient, Asp.NEt Core respective, and they follow OTel semantic conventions : https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/semantic_conventions/http-metrics.md OpenTelemetry does not have any convention that would result in "http_requests" metric, so it wont be part of OTel instrumented app. |
Beta Was this translation helpful? Give feedback.
http_client_duration_ms_bucket, and http_server_duration_ms_bucket.
The above are expected from OpenTelemetry instrumentaion for HttpClient, Asp.NEt Core respective, and they follow OTel semantic conventions : https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/semantic_conventions/http-metrics.md
OpenTelemetry does not have any convention that would result in "http_requests" metric, so it wont be part of OTel instrumented app.
My best guess is that - its coming from a non-OTel component, like Prometheus Client in .NET/something else.