I'm looking at the Azure Monitor OpenTelemetry preview. Is it worth learning about and trying, and are there any setup issues to watch for?
Is Azure Monitor's OpenTelemetry preview worth trying?
Answers
Worth a small trial if you're already using or learning OpenTelemetry, but I wouldn't assume the preview will be a smooth drop-in. Setup has been described as rough, and moving an existing workspace to the new endpoints may take more effort than starting with a new one.
A test workspace would give you a chance to check the setup before changing an existing deployment.
Reply to this answer
The Azure credential requirement is the part I'd check first, especially for apps running outside Azure. Some apps and frameworks expect to authenticate OpenTelemetry exports with custom headers, so that can make this a less convenient fit than other backends.
Reply to this answer
OpenTelemetry itself is worth learning even if you don't settle on Azure Monitor. The collector gives you a routing layer between an instrumented app and a telemetry backend. A sidecar collector is one deployment option, for example alongside an ASP.NET API.
That portability is useful, but it doesn't mean every backend has the same setup or capabilities. I'd evaluate the Azure integration separately from the instrumentation.
Reply to this answer
Pay attention to metrics as well as logs when testing. The AppMetrics table in Log Analytics treats metrics as log data, while the newer ingestion path changes how metrics are stored. Check what that means for your queries and dashboards before migrating.
Reply to this answer
Add your answer
Answers are reviewed before publication.
_s62!velourstaple.8:
A collector can help separate the app's instrumentation from the destination. It may let you change where telemetry goes without changing the app, though you still need to solve authentication on the export path.