-
Notifications
You must be signed in to change notification settings - Fork 13
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
Filtering log entries #198
Comments
Hello No, and I think it would be useless, you could use a custom logging filter attached to this handler. Having said that we don't test the specific behaviour, but on the paper it should work since it's part of the framework Regards |
Probably we'd need a For filtering by log category, there's a link to #156 (i.e. be able to associate splunk handler to only specific loggers) though I'm not clear if you could also restrict log categories on the default log handler. Using purely configuration today, there's only the log level ( |
As @rquinio1A pointed out this requires the |
I have no idea what you're trying to say there. As for your screenshot, I don't see how that's useful to me. The SplunkLogHandler is not a CDI bean so I can't get a reference to it. Consider this a request to add the filter property such that I can attach a filter to the handler—if you're not interested in implementing it, I'll gladly look for other ways to get this done. |
Hey, I am just trying to help here, no need to be rude or impatient. You can ask for precision if you don't understand, I would happy to clarify my thoughts here. Anyway, for reference, I've been put on the wrong track because of the name of quarkusio/quarkus#27864.
Yes in a smart way because LogSetupRecorder will erase it with an instance of LogCleanupFilter, we would need to override setFilter() and compose the filters.
Good luck |
Does this extension support filtering log entries based on some criteria such that I can forward only a subset of my logs to Splunk? What I'm trying to do is log some entries to stdout and some to Splunk without having to build a Splunk client myself.
The text was updated successfully, but these errors were encountered: