ResourceLogs
OTLP - Signals- Semantic Conventions
Resource
LogRecord
severity_text
body
Attributes
host.name: my-host.xyz
service.name: my-service
Attributes
http.request.method: GET
http.route: /users/:userID
client.address: 11.12.13.14
OTLP data format
Semantic Conventions
(simplified)
OpenTelemetry Protocol Specification
● Protocol Buffers schema that is used for the payloads
● implemented over gRPC and HTTP
Resilience for Logs
API
SDKOTLP
…
Observability Backends
● Logs can contain crucial information and hence
SHOULD always be captured
● Sending Logs through OTLP over the network might not
provide the best reliability
● Writing OTLP Logs into local files (i.e. through stdout)
and then collecting them independently can enhance
resilience.
Resilience for Logs
●https://github.com/open-telemetry/opentelemetry-python/issues/4661
● https://gist.github.com/ChrsMark/dc36896f0e5755e7bbaab7c49b5aa5a8
The above output can be parsed back into OTLP by the following
Opentelemetry Collector components:
● otlpjsonfilereceiver
● filelogreceiver+otlpjsonconnector