In the rapidly evolving application development landscape, the need for robust and flexible observability tools has never been greater. Developers often face challenges with inconsistent instrumentation, as different libraries and frameworks may use varying methods, leading to fragmented and inconsistent telemetry data.
Additionally, non-standard vendor APIs can be restrictive, making it difficult for developers to create and integrate their own telemetry solutions.
We’ve seen this particular issue crop up firsthand with our customers since rolling out our OpenTelemetry-powered SDKs. Customers need compatibility between instrumentation built on the standardized OTel APIs and the Embrace SDK. Achieving this compatibility in a truly seamless way has not been without its challenges.