OpenTelemetry SDK Design and Implementation Values

Intro: Open Telemetry SDK Design and Implementation Values Sergey Kanzhelev, Google
OpenTelemetry Design and Implementation Values Sergey Kanzhelev, Google
Open Telemetry makes robust, portable telemetry a built-in feature of cloud-native software Open Telemetry provides a single set of API libraries, agents, and collector services to
The future of monitoring: By 2025, 50% of new cloud-native application monitoring will use open-source instrumentation instead of vendor-specific agents
Compatibility • Embrace standards. For example, Wac Trace Context specification is a recommended and built-in default for context propagation • Interoperability is a way for success. We value user's choice of a tool • OpenTelemetry is a built-in dependency. For example. OpenTelemtry APIs are being built-in in NET. It is more important than potential velocity slow down and exact specification conformance
Stability • Limited set of strongly-typed objects Name/value attributes based data collection allows to keep APIs and SDK stable There is no support for complicated cases. It is typical that the most interesting scenarios are expressed via stable set of simple APIs rather than introduction of specialized concepts
Use and give feedback Open Telemetry has no way of knowing how you use the project Tell us about your scenarios: What environments you use it - What's missing This and other feedback you can share via various communication options