"OpenTelemetry can decouple telemetry from vendors, letting developers emit consistent, high-quality data that explains real system behavior. Shared vocabularies and good telemetry make debugging faster and improve reliability, speed, and developer productivity."
"We're now building Serverless, Event Driven, Cell-based architectures, therefore the way we think about the telemetry, and ultimately observability around them, should also change."
"Good telemetry is data that's focused on describing how the system 'works' in production. It will allow you to understand what makes this interaction different from another, and what that caused to happen in the system."
Observability is evolving to meet the needs of serverless and event-driven architectures. OpenTelemetry allows developers to emit consistent, high-quality telemetry data that reflects real system behavior. This decoupling from specific vendors enables a focus on producing effective telemetry rather than adapting it to fit particular products. Good telemetry describes how systems operate in production, helping to identify differences in service interactions and their impacts on the system, including database calls and unique events.
Read at InfoQ
Unable to calculate read time
Collection
[
|
...
]