Open table of contents
Conclusion
Assign tools by signal ingress, transformation and delivery responsibility.
Context
Legacy logs and instrumented telemetry differ in format and delivery behavior. Assign transformation and delivery responsibility per path.
Design and verification scope
Assess the following responsibilities and boundaries when designing and verifying a configuration.
- Legacy and container logs
- OTLP
- Traces
- Instrumented telemetry
- Buffers
- Backpressure
- Failure handling
Decision rationale
Use the relationship between Legacy and container logs and Failure handling to compare the responsibilities of the selected approach and alternatives. Separate retained constraints from what the new boundary can change.
Trade-offs
Compare the implementation, maintenance and review work introduced by OTLP with the control it provides. Include failure paths, operator effort and conditions in which the approach should not be adopted.
Limitations
Review paths, retries, duplicates, drops and redaction. This division is a design choice, not a universal product rule.
Related case context
These cases provide attributed design context. They do not establish that the proposed experiments or configurations were delivered in those engagements.