Add Additional Field(s) For Login History Information #11880

New Issue

adam · 2025-12-29T21:51:10+01:00

adam commented

2025-12-29 21:51:10 +01:00

Originally created by @mr1716 on GitHub (Nov 27, 2025).

NetBox version

v4.4.7

Feature type

Data model extension

Proposed functionality

Add a new field called ‘prior logins’ or something similar to allow for logging when users log into Netbox. It would store the value which is the last login date/time from the prior “Last Login” into a new field. The new field would be like an array of prior dates that the user has logged in,

Use case

Right now; if admins want to track usage of their Netbox instance, they will have to utilize an external platform django-tracking2 to help determine which users have logged in at what times.

This is helpful and extremely useful because admins will want to know who is using Netbox over time. Which will help show the value of Netbox to the company as well as potentially show that the team isn’t using Netbox enough.

Database changes

There would need to be a new Array Field or similar type field. This could be a field called “recent logins” that has the date and/or times that the users have logged in.

External dependencies

No response

Originally created by @mr1716 on GitHub (Nov 27, 2025). ### NetBox version v4.4.7 ### Feature type Data model extension ### Proposed functionality Add a new field called ‘prior logins’ or something similar to allow for logging when users log into Netbox. It would store the value which is the last login date/time from the prior “Last Login” into a new field. The new field would be like an array of prior dates that the user has logged in, ### Use case Right now; if admins want to track usage of their Netbox instance, they will have to utilize an external platform django-tracking2 to help determine which users have logged in at what times. This is helpful and extremely useful because admins will want to know who is using Netbox over time. Which will help show the value of Netbox to the company as well as potentially show that the team isn’t using Netbox enough. ### Database changes There would need to be a new Array Field or similar type field. This could be a field called “recent logins” that has the date and/or times that the users have logged in. ### External dependencies _No response_

adam added the type: feature status: under review netbox labels 2025-12-29 21:51:10 +01:00

adam commented

2025-12-29 21:51:10 +01:00

@mr1716 commented on GitHub (Nov 27, 2025):

This ticket is a stretch, and may be better served as a plug-in. But a big request that we’ve had when working with Netbox is better user information surrounding their logins. And they don’t need or want to track every single webpage visited, how long users spend on each page, how long users login for.

But rather the example: “Ok, so Bob last logged in today at 12:52pm, and hes asking for X, Y, and Z features. Netbox already does that. Is Bob asking for that because he hasn’t used the tool enough (ie not logged in and even tried) or does he need help using the tool (has tried but maybe needs to understand how Netbox works)?”

@mr1716 commented on GitHub (Nov 27, 2025): This ticket is a stretch, and may be better served as a plug-in. But a big request that we’ve had when working with Netbox is better user information surrounding their logins. And they don’t need or want to track every single webpage visited, how long users spend on each page, how long users login for. But rather the example: “Ok, so Bob last logged in today at 12:52pm, and hes asking for X, Y, and Z features. Netbox already does that. Is Bob asking for that because he hasn’t used the tool enough (ie not logged in and even tried) or does he need help using the tool (has tried but maybe needs to understand how Netbox works)?”

adam commented

2025-12-29 21:51:11 +01:00

@jeremystretch commented on GitHub (Dec 4, 2025):

NetBox already records the most recent successful authentication event for each user under the last_login field. I think for anything more complex, you should expect to devise a proper long-term auditing system.

@jeremystretch commented on GitHub (Dec 4, 2025): NetBox already records the most recent successful authentication event for each user under the `last_login` field. I think for anything more complex, you should expect to devise a proper long-term auditing system.

adam commented

2025-12-29 21:51:11 +01:00

@jeremystretch commented on GitHub (Dec 4, 2025):

I don't think this needs a plugin necessarily, but I think we'd have more success on this front by exploring means by which we might better expose this data to an external system, e.g. via improved logging.

@jeremystretch commented on GitHub (Dec 4, 2025): I don't think this needs a plugin necessarily, but I think we'd have more success on this front by exploring means by which we might better expose this data to an external system, e.g. via improved logging.

adam referenced this issue

2025-12-29 23:21:14 +01:00

[PR #11880] [MERGED] Add fieldsets functionality to scripts to allow for form field groupings #13865

adam referenced this issue

2025-12-29 23:21:27 +01:00

[PR #12079] [MERGED] Release v3.4.7 #13903

adam referenced this issue

2025-12-29 23:21:37 +01:00

[PR #12234] [MERGED] Release v3.4.8 #13933

Sign in to join this conversation.