starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Device history (user activity) / searchable history #531

New Issue
Closed
opened 2025-12-29 16:22:55 +01:00 by adam · 10 comments
adam commented 2025-12-29 16:22:55 +01:00
Owner
Copy Link

Originally created by @quentinsch on GitHub (Nov 11, 2016).

It would be great if the history user activity can be shown for a device. This can be useful for auditing purposes and keeping track of changes.
For example if the 'last updated' is made clickable that you can see the history of the device.

schermafbeelding 2016-11-11 om 10 55 54

Originally created by @quentinsch on GitHub (Nov 11, 2016). It would be great if the history user activity can be shown for a device. This can be useful for auditing purposes and keeping track of changes. For example if the 'last updated' is made clickable that you can see the history of the device. ![schermafbeelding 2016-11-11 om 10 55 54](https://cloud.githubusercontent.com/assets/7438854/20211227/d98a36f0-a7fd-11e6-80e8-068410dabf59.png)
adam added the status: acceptedtype: feature labels 2025-12-29 16:22:55 +01:00
adam closed this issue 2025-12-29 16:22:55 +01:00
adam commented 2025-12-29 16:22:55 +01:00
Author
Owner
Copy Link

@aoyawale commented on GitHub (Dec 12, 2016):

agree. some of the logs and changes does not necessary mention what was changed but, that something happened.

@aoyawale commented on GitHub (Dec 12, 2016): agree. some of the logs and changes does not necessary mention what was changed but, that something happened.
adam commented 2025-12-29 16:22:56 +01:00
Author
Owner
Copy Link

@john-arvid commented on GitHub (Dec 21, 2016):

I think this could be very usefull when a non-technical user is making an error. Which will happen several times.

@john-arvid commented on GitHub (Dec 21, 2016): I think this could be very usefull when a non-technical user is making an error. Which will happen several times.
adam commented 2025-12-29 16:22:56 +01:00
Author
Owner
Copy Link

@croax commented on GitHub (Mar 24, 2017):

Same for circuits and such. A fully searchable audit history log would be great so it would be possible to drill down which entities have been changed, when, how, by who etc..

@croax commented on GitHub (Mar 24, 2017): Same for circuits and such. A fully searchable audit history log would be great so it would be possible to drill down which entities have been changed, when, how, by who etc..
adam commented 2025-12-29 16:22:56 +01:00
Author
Owner
Copy Link

@Zimeon- commented on GitHub (Sep 20, 2017):

We've received the same request from our users to have a log of who updated the device/ip/prefix/vlan. A more in depth log with what has changed could be a long term addition.

@Zimeon- commented on GitHub (Sep 20, 2017): We've received the same request from our users to have a log of who updated the device/ip/prefix/vlan. A more in depth log with what has changed could be a long term addition.
adam commented 2025-12-29 16:22:56 +01:00
Author
Owner
Copy Link

@MHammett commented on GitHub (Dec 2, 2017):

Would a snapshot of what a rack\device\circuit\etc. was like at a certain prior date\time be an acceptable extension of this? IE: What was in this rack and how was it cabled three weeks ago?

@MHammett commented on GitHub (Dec 2, 2017): Would a snapshot of what a rack\device\circuit\etc. was like at a certain prior date\time be an acceptable extension of this? IE: What was in this rack and how was it cabled three weeks ago?
adam commented 2025-12-29 16:22:56 +01:00
Author
Owner
Copy Link

@Zimeon- commented on GitHub (Dec 2, 2017):

That would be cool for racks. Was more thinking of showing the log rows. Like "User x added device nnn". User Y modified device nnn" and user x removed device".

@Zimeon- commented on GitHub (Dec 2, 2017): That would be cool for racks. Was more thinking of showing the log rows. Like "User x added device nnn". User Y modified device nnn" and user x removed device".
adam commented 2025-12-29 16:22:56 +01:00
Author
Owner
Copy Link

@MHammett commented on GitHub (Dec 2, 2017):

nods You could essentially have a diff of beginning and end date\times of things that affected the scope of your search (rack, device, etc.). How it's presented isn't incredibly important.

@MHammett commented on GitHub (Dec 2, 2017): *nods* You could essentially have a diff of beginning and end date\times of things that affected the scope of your search (rack, device, etc.). How it's presented isn't incredibly important.
adam commented 2025-12-29 16:22:56 +01:00
Author
Owner
Copy Link

@mk311d commented on GitHub (Dec 4, 2017):

Also logging the device port allocation, who added/changed/modified something... Would be nice to have it right there for each port showing when and who modified it last time and let's say a button on which the user could click and would show the whole history of changes including the previous status.
The same type of logging could be applicable for IPs, racks, ports, child devices, ...

@mk311d commented on GitHub (Dec 4, 2017): Also logging the device port allocation, who added/changed/modified something... Would be nice to have it right there for each port showing when and who modified it last time and let's say a button on which the user could click and would show the whole history of changes including the previous status. The same type of logging could be applicable for IPs, racks, ports, child devices, ...
adam commented 2025-12-29 16:22:57 +01:00
Author
Owner
Copy Link

@awfki commented on GitHub (Jun 14, 2018):

+1
This would be fine as a NetBox feature but sending syslogs with relevant info would be even better.

@awfki commented on GitHub (Jun 14, 2018): +1 This would be fine as a NetBox feature but sending syslogs with relevant info would be even better.
adam commented 2025-12-29 16:22:57 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 18, 2018):

Looks like this was covered by #1898 (change logging). This functionality will be incorporated in the v2.4 release.

@jeremystretch commented on GitHub (Jun 18, 2018): Looks like this was covered by #1898 (change logging). This functionality will be incorporated in the v2.4 release.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label status: accepted type: feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#531
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?