-
Notifications
You must be signed in to change notification settings - Fork 773
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
Does MeterProvider support OTLP HttpExporter? #2522
Comments
Not for metrics. |
Thank you! Is the vision that eventually it should be supported? If yes - wonder whether it is already on a roadmap? |
Eventually yes. It's not planned for 1.2 stable release but @alanwest might know if the feature is small and can be included in the 1.2 release timeframe. |
On the 2nd of November (Tu.) there will be some internal company's planning / sync session. After that I can say if can pick it up. I can let you know during the next "OpenTelemetry .NET SDK SIG sync up" (also the 2nd of November). But if it's more urgent then @alanwest can pick it up as well. Theoretically implementation of metrics/logs export should be rather straightforward. Just one thing. It makes sense to merge the #2492 Otlp http exporter: allow endpoint override first. |
Tagging with metrics, enhancement labels. Not marking as "required-for-ga" for Metrics, as this is not a blocker for 1.2 Metric release (OTLP+grpc alone is sufficient for that). In other words, this'd be nice to have for 1.2, and may land in 1.2, but not required/won't block 1.2. |
@cijothomas Has it been confirmed whether or not the Http protocol will be included in the 1.2 release yet? |
I can add from my side that, unfortunately, there are some internal company's things popped up in the latest time and there is no possibility to make this contribution for me at the moment. |
Okay cool. Thank you for the update. |
Question
I'm trying to emit metrics using OTLP HttpExporter (ConsoleExporter works) but nothing is getting sent. I wonder whether HttpExporter is supported for Metrics path?
The text was updated successfully, but these errors were encountered: