Status: Stable This section applies to Log, Metric, Resource, and Span, and describes requirement levels for attributes defined in semantic conventions. Attribute requirement levels apply to the instrumentation library. The following attribute requirement levels are specified: Required Conditionally Required Recommended Opt-In The requirement level for an attribute is specified by semantic conventions depending on attribute availability across instrumented entities, performance, security, and...| OpenTelemetry
If you’ve been following OpenTelemetry for a while, you’ve probably heard a lot about logs. Log bridges, Logs API, events, you name it, we’ve talked about it. This blog post is intended to be a discussion of the rationale and current design direction of logging in OpenTelemetry. Definitions Let’s get started with a basic definition of how OpenTelemetry thinks about logs. Broadly, logs are any telemetry that is emitted through a log pipeline, and are created by calling the Logs API. Th...| OpenTelemetry
This quote from Charity Majors is probably the best summary of the current state of observability in the tech industry - a total, mass confusion.| isburmistrov.substack.com
Tracking where the time goes in your CI pipeline is an important step towards being able to make it go even faster. Up until somewhat recently, the only way of tracking how long tasks took in CI was either hoping people had wrapped all their commands in time ..., or by reading a timestamped build log and calculating the difference between numbers. Which isn’t great or fun, if we’re being honest.| andydote.co.uk
