-
Notifications
You must be signed in to change notification settings - Fork 11
Investigate log verbosity and suggest a solution #45
Comments
LoggingThis is a suggestion how we should implement logging in command line tools. Note that the commands and their output here might be fictional. ConfigurationWe should be using our service logging level conventions as a base, using the same terminology as well as their definitions: One additional level could be added if we seem fit: SILENT. The numeric mapping would be:
The environment variable is useful in e.g. Circle CI to avoid modifying scripts that already runs corectl commands. OutputThe output should, at minimum, be designed for humans. This means plain english and no too cryptic log formats. In addition, it would be useful to support logging in different formats: Human readable
JSONThis format could (with benefit) use the logging conventions JSON output, but perhaps defined as an JSON array.
|
I have looked into adding a logging framework in corectl for logging in either plain text and json. Since we are aiming for being able to customize the output e.g. log keys, format of timestamps and log levels there are atleast two suitable options: Switching to using either of these framework for logging standard messages (INFO, DEBUG, FATAL etc.) or json traffic from our modules seems doable in a small timeframe. I have a branch where I have started the work on using As I see it there is two bigger tasks that needs to be resolved/discussed before we choose either of these options:
|
Removing the |
I think we should revisit this issue! |
Investigate how we can balance log output from different tools against cluttering the cli output.
The text was updated successfully, but these errors were encountered: