04 Sep 2025
11:13 PM
- last edited on
16 Dec 2025
08:33 AM
by
IzabelaRokita
Hi Community,
Our customer is experiencing an issue in their Azure Service Fabric implementation. They asked why Dynatrace did not catch this problem.
From what I see, the only supported way to monitor Service Fabric applications is via OpenTelemetry instrumentation (https://docs.dynatrace.com/docs/ingest-from/microsoft-azure-services/azure-integrations/azure-servic... )
Installing OneAgent on the nodes is not enough for full visibility — for example, to get distributed traces, OpenTelemetry must be used.
At the same time, I noticed that Service Fabric also emits a lot of ETW (Event Tracing for Windows) events.
Is there a way to ingest these ETW events into Dynatrace Managed (e.g., via logs, metrics, or OpenTelemetry Collector) and possibly generate custom problems from them?
Or is OpenTelemetry really the only solution to get ETW-based visibility into Dynatrace?
Any guidance or best practices would be greatly appreciated.
Thanks in advance!
Regards, Deni
Solved! Go to Solution.
16 Dec 2025 08:33 AM
Hey @deni ,
I just wanted to check in and see if you still need help with this. If so, I’d be happy to look into it for you! 😊
Please let me know what works best for you.
30 Dec 2025 11:13 AM
Hi @IzabelaRokita ,
The customer decided to use a different monitoring tool for this specific case instead of implementing an OpenTelemetry solution.
As mentioned in my previous comment, I just wanted to double-check that I’m not missing anything. 🙂
Thanks!
Regards, Deni
Featured Posts