-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Enable debug logging for ShardCoordinator/ShardRegion/Shard actors #7097
Comments
There is a setting that will do this for Akka.Cluster.Sharding already, have you tried setting this to
|
From the looks of it, that would still require us to enable debug logging for the whole system, this feature request is more around allowing debug logs without turning full system level log level to debug. |
I guess we could change that setting to accept a LOGLEVEL argument - that should do it |
Yeah that would work. Cheers |
@LeonHartley so I implemented a fix for this in #7118 but decided not to merge it for 1.5.18 because it's kind of weird / sloppy. What I think we're going to do instead is introduce a new "log filtering" feature on the backend that allows you to scrub out logs you don't care about at various log levels. I'll create a separate GH issue to spec it out, but I think that will be a much cleaner solution to your problems - it'll let you enable |
Yeah that sounds perfect, nice one @Aaronontheweb. |
Working on a preview of this feature here #7179 |
…ing emitted in first place (#7179) * create `LogFilter` infrastructure * Create evaluator from setup close #7097 * added sanity checks for `Regex`-based rules * integrated `LogFilterSetup` into `Settings` and `StandardOutLogger` * simplifying * added accurate end2end unit test * added API approvals * removed unnecessary API from `LogFilterBase` * small perf optimization for default cases * fixed bug with blended filter types * added API approvals * fixed race condition with tests * updated APIs to be more expansive * added docs * fixed reference to samples * fixed markdown linting rule --------- Co-authored-by: Gregorius Soedharmo <arkatufus@yahoo.com>
@LeonHartley just merged this in - should go live with it in a day or so. |
Documentation for it will be live on the website here in about 20 minutes or so: https://getakka.net/articles/utilities/logging.html - at the bottom of the page |
Is your feature request related to a problem? Please describe.
We are seeing potential issues with the shard coordinator when recovering millions of entities, where shard regions do not receive acknowledgement from the coordinator. We'd like to allow debug logs to be switched on for sharding system-level actors without having to enable debug logging for the whole system
Describe the solution you'd like
A configuration switch to perhaps change the log level of all logs from the shard coordinator and shard region actors, so we can view more information, even when the rest of the system is set to
Information
orWarning
level.Describe alternatives you've considered
We could switch debug logging on for the whole system but this would cause unnecessary stress on our logging infrastructure.
The text was updated successfully, but these errors were encountered: