[GH-ISSUE #78] Feature request: Better logging #48

Closed
opened 2026-03-02 12:03:24 +03:00 by kerem · 3 comments
Owner

Originally created by @KelvinTegelaar on GitHub (Oct 19, 2021).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/78

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.

Originally created by @KelvinTegelaar on GitHub (Oct 19, 2021). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/78 **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.
kerem 2026-03-02 12:03:24 +03:00
Author
Owner

@KelvinTegelaar commented on GitHub (Oct 19, 2021):

  • Added more logging into components
  • Added debug type logging
  • Added log filtering in API
<!-- gh-comment-id:946633200 --> @KelvinTegelaar commented on GitHub (Oct 19, 2021): - Added more logging into components - Added debug type logging - Added log filtering in API -
Author
Owner

@KelvinTegelaar commented on GitHub (Oct 19, 2021):

@redanthrax added logging to the graph function, with a critical level for any actual call failure.

<!-- gh-comment-id:947006000 --> @KelvinTegelaar commented on GitHub (Oct 19, 2021): @redanthrax added logging to the graph function, with a critical level for any actual call failure.
Author
Owner

@KelvinTegelaar commented on GitHub (Oct 26, 2021):

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

<!-- gh-comment-id:951891861 --> @KelvinTegelaar commented on GitHub (Oct 26, 2021): 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
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/CIPP#48
No description provided.