-
-
Notifications
You must be signed in to change notification settings - Fork 42
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
Change default logging to INFO #84
Conversation
Could this potentially break any ChatOps CI or similar in our e2e tests @humblearner where we grep for specific log messages? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will not only break chatopsCI, it will also break the self check script: https://github.com/StackStorm/st2chatops/blob/master/scripts/self-check.sh#L187 and it will add a step for new users, changing the debug level, who may have problem setting up st2chatops for the first time. It would be better to add step in docs to decrease verbosity.
This change was actually requested by a user, that the messages are too verbose, and I'm inclined to agree - INFO is a common default log level. I'd prefer that we make this change, and follow @armab suggestion of injecting a DEBUG loglevel for our CI use case. On a related note, the CircleCI checks have passed thus far, so if we're expecting CI to break, maybe something need adjusted. |
@Mierdin: I have seen the conversation in #chatops community channel. I agree with you that the default log level should be Please make changes at following locations as well:
However, I still don't agree with this change, because:
Also, note, you will still see
|
Q: how many other apps ship with DEBUG logs on by default? And if we are determined to ship with DEBUG, then surely we should at least sort out this other pack issue of no log rotate script? |
Closing for now, since this is a bit stale. Feel free to pick up where I left off on the branch. |
The change itself is good. Maybe @blag can pick it up in future and update the st2tests as part of the initiative to rectify st2chatops. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In order for the ansible smoke-test to succeed, it needs to be able to override this environment var. I suggest setting this to info only as a default if the var is not already set.
Co-Authored-By: armab <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
re @humblearner's objection
Maybe the self-check script (which I have not used or reviewed in detail) needs to modify the log level on the fly similar to how the ansible smoke-test sets the variable: |
Closes #77