Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

There should be more observability around exporter helper start up and shutdown #10201

Open
splunkericl opened this issue May 21, 2024 · 2 comments · May be fixed by #10208
Open

There should be more observability around exporter helper start up and shutdown #10201

splunkericl opened this issue May 21, 2024 · 2 comments · May be fixed by #10208
Labels
area:exporter collector-telemetry healthchecker and other telemetry collection issues

Comments

@splunkericl
Copy link
Contributor

Important (read before submitting)

Is your feature request related to a problem? Please describe.
As a user of otel collector, I find it hard to see which exporter helper component is stuck starting up or shutting down. Some of the examples in the past:

When debugging these problems, it isn't clear that the components are stuck.

Describe the solution you'd like
A debug message is added at the beginning of startup/shutdown and at the end of the startup/shutdown. Components we should add:

  • retry sender
  • batch sender
  • queue sender

Describe alternatives you've considered
Add it as INFO logs but it can be too noisy

Additional context

@dmitryax
Copy link
Member

The logs should be debug level if it's for troubleshooting

@TylerHelmuth TylerHelmuth added area:exporter collector-telemetry healthchecker and other telemetry collection issues labels May 21, 2024
@timannguyen
Copy link
Contributor

i'll take this up

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:exporter collector-telemetry healthchecker and other telemetry collection issues
Projects
None yet
5 participants