-
Notifications
You must be signed in to change notification settings - Fork 352
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
Log smarter, not harder #778
Comments
Another thing I've noticed is that a ton of our log messages are at debug level but most people aren't using debug level logging. Oopsie Daisy |
from Ruchi
|
That's exactly what the initial ticket writeup suggested. Whomever wrote the ticket in the first place is a genius ;) |
I believe we're much smarter now that we no longer rely on detailed logs for test cases to pass. Closing for now |
This is more of an epic and not a right now thing, but I wanted to capture the thought for future consideration.
In the author's not-so-humble opinion we log way too much stuff, to the point that logs aren't particularly useful unless you know exactly what you're looking for.
We also know that Cromwell's logs are blowing apart loggly and stuff like that.
We also manage to log some stuff (e.g. stacktraces) multiple times for one incident.
We also have many issues where logs would be super helpful yet all we see is something like "an error occurred" without any context.
We should sit down as a group and with focus groups of downstream clients (e.g. firecloud, gotc) and go through what we're logging and look for ways to both massively debulk our logs as well as making sure that we're logging the most useful stuff.
The text was updated successfully, but these errors were encountered: