-
Notifications
You must be signed in to change notification settings - Fork 85
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
Consider supporting pass-through for OTLP metrics #515
Comments
Yes -- this is already on the roadmap for sometime "soon" -- meaning we plan to do it but don't have a time commitment yet. |
Dupe of #449? |
It seems like this is still a problem? SEVERE: Failed to export metrics. Server responded with UNIMPLEMENTED. This usually means that your collector is not configured with an otlp receiver in the "pipelines" section of the configuration. If export is not desired and you are using OpenTelemetry autoconfiguration or the javaagent, disable export by setting OTEL_METRICS_EXPORTER=none. Full error message: unknown service opentelemetry.proto.collector.metrics.v1.MetricsService |
@rasharab are you using HTTP or gRPC? For HTTP it should already be supported, but not for gRPC. |
Grpc. Thank you for the heads up. |
For people who use refinery to sample traces and also send along metrics to honeycomb, it can be surprising that they can't "just point their metrics at refinery" and have them pass through. I've not seen anyone expect that the metrics should be sampled in some way, but having to set your endpoint differently for metrics can be surprising.
The text was updated successfully, but these errors were encountered: