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

[service] logs emitted by collector don't follow severity #11717

Open
codeboten opened this issue Nov 20, 2024 · 1 comment · May be fixed by #11718
Open

[service] logs emitted by collector don't follow severity #11717

codeboten opened this issue Nov 20, 2024 · 1 comment · May be fixed by #11718
Labels
area:service bug Something isn't working

Comments

@codeboten
Copy link
Contributor

The collector supports emitting its internal logs via OTLP. After testing this functionality, it appears that logs of all severities are emitted via the logger provider configured. This is because the otelzap bridge doesn't have a configuration for severity level. This requires a separate processor (minsev) which is currently not supported by the otel configuration schema.

I will submit a pull request that proposes wrapping the Tee'd zap core into another zap core that will apply the filtering before logs are sent to the logger provider.

@codeboten codeboten added bug Something isn't working area:service labels Nov 20, 2024
@codeboten codeboten added this to the Self observability milestone Nov 20, 2024
codeboten added a commit to codeboten/opentelemetry-collector that referenced this issue Nov 20, 2024
@skandragon
Copy link

I was coming here to report this exact issue. Will the level be set per provider?

I would like to not get debug messages for sure, generally :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:service bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants