26 Aug 2024 09:29 AM - last edited on 24 Sep 2024 03:05 PM by Michal_Gebacki
Hello
In most cases I notice: when you need manual instrumentation, use Otel.
So what is the status of the oneAgent SDK? Should this not be the first choice?
KR Henk
Solved! Go to Solution.
29 Aug 2024 12:53 AM
Hi @henk_stobbe ,
We recommend using the OneAgent SDK for instrumentation because it is fully supported and optimized by Dynatrace, ensuring robust integration with continuous technical support and updates. Based on my understanding, the following points reflect my perspective in response to your question:
Broad Adoption and Community: OpenTelemetry is a widely popular open standard known for its ability to integrate with multiple platforms. However, some community-contributed examples may not adhere to best practices, posing risks in terms of performance and security.
Documentation and Community Resources: OpenTelemetry’s extensive documentation makes it easier to adopt, but it also presents risks, as some examples may not always follow best practices, potentially leading to suboptimal implementations.
Agile Development and Risks: OpenTelemetry evolves rapidly, but as a community-driven project, it may include developments that haven't undergone a thorough testing cycle, increasing the risk of stability and security issues.
While OpenTelemetry offers certain advantages, the OneAgent SDK remains the preferred choice for secure and reliable integration with Dynatrace, ensuring optimal performance and support.
29 Aug 2024 06:32 AM
Thanks for the clear and extensive answer. very useful!
KR Henk Stobbe