Forum Discussion
Pure standards based instrumenting
atrauzzi :
Love the enthusiasm. As Microsoft, we are contributing heavily to open Telemetry; as you had pointed out our aim moving forward is to allow customers to use OTLP exporter (https://github.com/open-telemetry/opentelemetry-collector/blob/master/exporter/otlpexporter/README.md) to send in data to Azure Monitor as well. This allows customers to be vendor agnostic while welcoming the most community driven contributions.The most up to date roadmap for OTLP is available here(https://github.com/open-telemetry/opentelemetry-collector/blob/master/docs/roadmap.md); most SDK's and exporters are supposed to GA by end of this year.
As this is an opensource project feel free to join in community meetings to contribute or to provide us with any valuable feedback that you may have.
Microsoftatrauzzi We couldn't agree more, and our objective is for customers to be successful on Azure regardless of their choice of instrumentation or monitoring consumption tools. We are in fact, contributing to the OpenTelemetry effort, and Azure SDKs (including Application Insights SDKs) will be OpenTelemetry based. Stay tuned for updates in this space.
Any chance you can offer a timeline or any detail on what's coming? My apologies, I feel like it would be better to know early as I've been disappointed in the past over "stay tuned" and it ends up being a less than optimal solution. And then I'm stuck trying to convince Azure PMs and support channels that what was implemented wasn't actually helpful...
- SoubhagyaDash
atrauzzi We are on the OT GitHub repos, so what we are implementing/contributing to is public information. Please weigh in on the right repos like https://github.com/microsoft/opentelemetry-azure-monitor-python. From what I gather, you have concerns regarding supporting OT exporter based collection as opposed to the Collectors?