You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The logging engine currently works by adding entries to a text file, using a mutex to prevent parallel write issues. This works OKish but could use some improvements.
I'd also like to have logs be in a better format. We currently use
DATE, USER, MESSAGE, SEVERITY
I am proposing changing this to:
DATE, USER, TENANT, MESSAGE, SEVERITY
Each API should post to the log without exception. Severity levels should be:
DEBUG
INFO
WARN
ERROR
CRITICAL
By default, the log should only return the INFO/WARN/ERROR levels, and have a selection option for the full log.
The text was updated successfully, but these errors were encountered:
And with the latest additions to the logging engine we can close this out. Logging interface can still use improvements, and that is planned in a new issue for 1.3
Is your feature request related to a problem? Please describe.
The logging engine currently works by adding entries to a text file, using a mutex to prevent parallel write issues. This works OKish but could use some improvements.
I'd also like to have logs be in a better format. We currently use
I am proposing changing this to:
Each API should post to the log without exception. Severity levels should be:
By default, the log should only return the INFO/WARN/ERROR levels, and have a selection option for the full log.
The text was updated successfully, but these errors were encountered: