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

Log smarter, not harder #778

Closed
geoffjentry opened this issue May 4, 2016 · 5 comments
Closed

Log smarter, not harder #778

geoffjentry opened this issue May 4, 2016 · 5 comments

Comments

@geoffjentry
Copy link
Contributor

geoffjentry commented May 4, 2016

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.

@geoffjentry
Copy link
Contributor Author

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

@kcibul
Copy link
Contributor

kcibul commented Jul 13, 2016

from Ruchi

Currently we have a lot of information that gets logged by Cromwell and some of it seems like it may not be useful to our customers. For example, every actor state transition gets logged, but it's unclear who is using that information.

We tech talked today an the suggestion was to meet with some key customer's, figure out if there are aspects of our logging they don't need to help reduce, and instead just redirect the unwanted logging to debug level, so that it can still be used for debugging purposes.

@geoffjentry
Copy link
Contributor Author

That's exactly what the initial ticket writeup suggested. Whomever wrote the ticket in the first place is a genius ;)

@geoffjentry
Copy link
Contributor Author

@kcibul @ruchim Can we decide what exactly this ticket entails in terms of 0.21? I don't think what I originally meant it to be is really appropriate for feature party, but we've decided that this ticket is a placeholder for something which is currently ill defined

@kcibul kcibul removed the 0.21 label Aug 16, 2016
@kcibul kcibul removed this from the 0.21 milestone Aug 16, 2016
@cjllanwarne
Copy link
Contributor

I believe we're much smarter now that we no longer rely on detailed logs for test cases to pass. Closing for now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants