You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to explore if receivers built on top using confighttp.HTTPServerSettings generate useful metrics such as num of incoming requests, packets not forwarded to the processor(or exporter) etc. From the code I could see that the otelhttp instrumentation is used. However the /metrics endpoint on service.telemetry.metrics.address=:8888 endpoint reports no metrics(empty page) if we use telemetry.useOtelForInternalMetrics feature flag and basic obs views(exporter and processor metrics) otherwise.
Can anyone tell me if its the correct way to observe the collector?
Thanks
The text was updated successfully, but these errors were encountered:
I know how it sounds, but the collector has limited self-observability capabilities. It should start changing once the Go SDK has the features we need. See #4198.
I am trying to explore if receivers built on top using
confighttp.HTTPServerSettings
generate useful metrics such as num of incoming requests, packets not forwarded to the processor(or exporter) etc. From the code I could see that theotelhttp
instrumentation is used. However the/metrics
endpoint onservice.telemetry.metrics.address=:8888
endpoint reports no metrics(empty page) if we usetelemetry.useOtelForInternalMetrics
feature flag and basic obs views(exporter and processor metrics) otherwise.Can anyone tell me if its the correct way to observe the collector?
Thanks
The text was updated successfully, but these errors were encountered: