Add verbosity level to log messages #30
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit adds a verbosity level to log messages. The verbosity level can be configure in the .cnf file or else Note will be assumed by default. This is to avoid the scheduler from flooding the logs with messages that indicate the scheduler is running as expected. There are 4 log levels: - Info - Note - Warning - Error The last two are obvious, but the first two are as follows: - Info: This is just and information, the action that follow this will not change the state of the proxy. - Note: This is a note to the user that the action that follows this will most likely change the state of the proxy. Closes #16
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit adds a verbosity level to log messages. The verbosity level can be configure in the .cnf file or else Note will be assumed by default. This is to avoid the scheduler from flooding the logs with messages that indicate the scheduler is running as expected.
There are 4 log levels:
The last two are obvious, but the first two are as follows:
Closes #16