Implement application logging #3344

Closed
opened 2025-12-29 18:28:03 +01:00 by adam · 0 comments
Owner

Originally created by @jeremystretch on GitHub (Feb 18, 2020).

Originally assigned to: @jeremystretch on GitHub.

Proposed Changes

Add logging functions throughout NetBox wherever it makes sense to do so. At a minimum, we should be generating log output every time an object is created, modified, or deleted. This is likely going to be implemented in an iterative manner over time, rather than pushed as a single PR.

Areas we should evaluate include:

  • Utility CRUD views
  • API viewsets
  • User login/logout
  • Execution of reports and custom scripts

Justification

Logging helps users troubleshoot performance issues and bugs. Currently, NetBox does not generate any intentional logging other than for exceptions.

Originally created by @jeremystretch on GitHub (Feb 18, 2020). Originally assigned to: @jeremystretch on GitHub. ### Proposed Changes Add logging functions throughout NetBox wherever it makes sense to do so. At a minimum, we should be generating log output every time an object is created, modified, or deleted. This is likely going to be implemented in an iterative manner over time, rather than pushed as a single PR. Areas we should evaluate include: - [x] Utility CRUD views - [x] API viewsets - [x] User login/logout - [x] Execution of reports and custom scripts ### Justification Logging helps users troubleshoot performance issues and bugs. Currently, NetBox does not generate any intentional logging other than for exceptions.
adam added the status: acceptedtype: housekeeping labels 2025-12-29 18:28:03 +01:00
adam closed this issue 2025-12-29 18:28:04 +01:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#3344