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

[azure-eventhub] Change input v1 tracing configuration to opt-in #41931

Closed
zmoog opened this issue Dec 6, 2024 · 2 comments · Fixed by #41932
Closed

[azure-eventhub] Change input v1 tracing configuration to opt-in #41931

zmoog opened this issue Dec 6, 2024 · 2 comments · Fixed by #41932
Assignees
Labels
input:azure-eventhub Team:obs-ds-hosted-services Label for the Observability Hosted Services team

Comments

@zmoog
Copy link
Contributor

zmoog commented Dec 6, 2024

With #40451, we added a tracing option in the input v1 that allows the internal Event Hubs SDK logs to reach the main input logger.

This allows better visibility into the internal SDK workings. During normal operations, with log level set to INFO, the input logs no messages.

However, a few customers reported higher than anticipated error logs. These error logs are an essential signal to troubleshoot the root cause. However, event if these are edge cases, we should give the option to completely opt out from tracing when needed.

@zmoog zmoog added Team:obs-ds-hosted-services Label for the Observability Hosted Services team input:azure-eventhub labels Dec 6, 2024
@elasticmachine
Copy link
Collaborator

Pinging @elastic/obs-ds-hosted-services (Team:obs-ds-hosted-services)

@zmoog
Copy link
Contributor Author

zmoog commented Dec 6, 2024

The logs tracer uses the same log level as Beats. However, in a few circumstances, the number of error logs can be very high.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
input:azure-eventhub Team:obs-ds-hosted-services Label for the Observability Hosted Services team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants