-
Notifications
You must be signed in to change notification settings - Fork 431
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
[Feature]: Severity filter support in BatchLogProcessor #1881
Comments
You can do this upstream, even before OpenTelemetry itself. |
Any reason not to create a tokio tracing filter to achieve it, and so drop the event before reaching the otel pipeline. |
Sorry about not being clearer in my request. The idea is to be able to do this on a per exporter basis. For example, my application logs at |
mm.. 2 loggerproviders (1 with stdout, another with otlp), and create 2 layers with diff. filtering - this should be possible. These are things typically done at Collector level. |
No, not planning to use |
Also, should clarify that I'm using the rust log: https://crates.io/crates/log and not tracing: https://crates.io/crates/tracing for application logging. |
This is the right way to achieving it. Though it would more straightforward with |
Related Problems?
No response
Describe the solution you'd like:
I would like to be able to configure an exporter to only exports logs at a specified severity or above. For example, in my app, I want to log at a default level of
debug
, but only export logs of levelinfo
and above to an open telemetry collector.I looked at the
logs_level_enabled
feature, but based on what I saw in the implementation, it is just a place holder at this point as it is hardcoded to always return true.A way to accomplish this would be to have a parameter, say
export_severity
added to theBatchLogConfig
and have that be honored in theBatchLogProcessor
. I am happy to send a PR if there is agreement with this approach, but wanted to check if this is in line with the plans for full support for thelogs_level_enabled
feature.Considered Alternatives
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: