Observability
Fleeting- External reference: https://opentelemetry.io/docs/concepts/observability-primer/
Observability Primer
Observability lets you understand a system from the outside by letting you ask questions about that system without knowing its inner workings.
— https://opentelemetry.io/docs/concepts/observability-primer/ ()
Telemetry refers to data emitted from a system and its behavior. The data can come in the form of traces, metrics, and logs.
— https://opentelemetry.io/docs/concepts/observability-primer/ ()
SLI, or Service Level Indicator
— https://opentelemetry.io/docs/concepts/observability-primer/ ()
example SLI can be the speed at which a web page loads.
— https://opentelemetry.io/docs/concepts/observability-primer/ ()
SLO, or Service Level Objective
— https://opentelemetry.io/docs/concepts/observability-primer/ ()
means by which reliability is communicated to an organization/other teams. This is accomplished by attaching one or more SLIs to business value
— https://opentelemetry.io/docs/concepts/observability-primer/ ()
span represents a unit of work or operation
— https://opentelemetry.io/docs/concepts/observability-primer/ ()
span contains name, time-related data, structured log messages, and other metadata (that is, Attributes) to provide information about the operation it tracks.
— https://opentelemetry.io/docs/concepts/observability-primer/ ()
distributed trace, more commonly known as a trace, records the paths taken by requests (made by an application or end-user) as they propagate through multi-service architectures, like microservice and serverless applications
— https://opentelemetry.io/docs/concepts/observability-primer/ ()
trace is made of one or more spans
— https://opentelemetry.io/docs/concepts/observability-primer/ ()