-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[receiver/statsd] Missing obsreport metrics from statsdreceiver #24278
Comments
Pinging code owners: See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Looks like the call to |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners: See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners: See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been closed as inactive because it has been stale for 120 days with no activity. |
I'd like to reopen this issue as we need some metrics for the receiver to monitor it in production (right now there is none) |
/label receiver/statsd -Stale |
Pinging code owners for receiver/statsd: @jmacd @dmitryax. See Adding Labels via Comments if you do not have permissions to add labels yourself. |
I opened #31839 to address this. We are already using this code in production. |
Resolved by #33415 |
Component(s)
receiver/statsd
What happened?
Description
The
statsdreceiver
does not properly exposeobsreport
metrics.Steps to Reproduce
Send some OTLP and statsd metrics to a collector configured with both receivers.
Expected Result
I should see
otelcol_receiver_accepted_metric_points_total
timeseries for both receivers.Actual Result
I see only a
otelcol_receiver_accepted_metric_points_total
timeseries for theotlp
receiver.Collector version
v0.81.0
Environment information
Environment
Linux
OpenTelemetry Collector configuration
Log output
Additional context
The receiver does seem to be instrumented with obsreport
opentelemetry-collector-contrib/receiver/statsdreceiver/reporter.go
Line 92 in 5133f4c
The text was updated successfully, but these errors were encountered: