Skip to content

Telemetry and Application Monitoring ADR#915

Open
coilysiren wants to merge 2 commits intomainfrom
coilysiren-patch-1
Open

Telemetry and Application Monitoring ADR#915
coilysiren wants to merge 2 commits intomainfrom
coilysiren-patch-1

Conversation

@coilysiren
Copy link
Copy Markdown
Contributor

@coilysiren coilysiren commented Mar 21, 2025

Ticket

Resolves #715

Copy link
Copy Markdown
Contributor

@lorenyu lorenyu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i think the ADR is conflating two things:

  1. whether or not to use the OpenTelemetry protocol vs use vendor-specific protocols
  2. which implementation of the OpenTelemetry protocol to use

i think those two things should be more clearly separated. for "whether to use OTLP", i think it's clear we should use OpenTelemetry protocol because:

  • it abstracts away the monitoring service which decouples the monitoring service from the application, reducing lock-in
  • most monitoring services accept it and some require it
    the downside is that (a) there's an extra layer of indirection which adds some complexity to the architecture and (b) in many cases requires a separate container rather than direct integration with the monitoring service through an SDK. (i'm not sure about (b) you may want to verify my reasoning).

for "which implementation of OTLP", fluentbit says they support the opentelemetry protocol so i think it's a choice between OpenTelemetry Collector and Fluent Bit (not sure if there are others). i'd like to see some pros/cons of the implementations, and happy to go with whatever you choose. can also ask others at Nava to see what they think.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Write OpenTelemetry ADR

2 participants