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

Add Stats and Images view to Locations #4751

New Issue
Closed
opened 2025-12-29 19:20:07 +01:00 by adam · 1 comment
adam commented 2025-12-29 19:20:07 +01:00
Owner
Copy Link

Originally created by @jcralbino on GitHub (Apr 12, 2021).

NetBox version

v2.11

Feature type

Change to existing functionality

Proposed functionality

Much like we have in the Site option (https://beta.netbox.dev/dcim/sites/24/). where a specific page is show for Stats where racks, devices or circuits is shown like the image bellow
image

In the new design where a location may represent a room, or some other nested object( room/aisle), it will be interesting to have the same stats information provided.
When Location represents a DC Room we can easily identify all the Racks inside, and most important we can also use the Images tab to document to room layout.

Use case

When Locations represent specific DC Rooms, or technical rooms the introduction of these fields under the Location main page (https://beta.netbox.dev/dcim/locations/8/) can be used to improve the documentation of the environment:

  • Images can be used to identify the rack layouts, and details on how to reach the locations
  • Stats can be used to summarize the total number of devices and racks inside that location.

Database changes

Additional fields are required to add the details for Images associated with a location.

External dependencies

none

Originally created by @jcralbino on GitHub (Apr 12, 2021). ### NetBox version v2.11 ### Feature type Change to existing functionality ### Proposed functionality Much like we have in the Site option (https://beta.netbox.dev/dcim/sites/24/). where a specific page is show for Stats where racks, devices or circuits is shown like the image bellow ![image](https://user-images.githubusercontent.com/44149262/114430636-eef42000-9bbe-11eb-8c1d-368c00632c7f.png) In the new design where a location may represent a room, or some other nested object( room/aisle), it will be interesting to have the same stats information provided. When Location represents a DC Room we can easily identify all the Racks inside, and most important we can also use the Images tab to document to room layout. ### Use case When Locations represent specific DC Rooms, or technical rooms the introduction of these fields under the Location main page (https://beta.netbox.dev/dcim/locations/8/) can be used to improve the documentation of the environment: - Images can be used to identify the rack layouts, and details on how to reach the locations - Stats can be used to summarize the total number of devices and racks inside that location. ### Database changes Additional fields are required to add the details for Images associated with a location. ### External dependencies none
adam added the type: featurestatus: duplicatebeta labels 2025-12-29 19:20:07 +01:00
adam closed this issue 2025-12-29 19:20:07 +01:00
adam commented 2025-12-29 19:20:08 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 12, 2021):

In the new design where a location may represent a room, or some other nested object( room/aisle), it will be interesting to have the same stats information provided.

This was proposed in #6126; please see the discussion there.

When Location represents a DC Room we can easily identify all the Racks inside, and most important we can also use the Images tab to document to room layout.

Please open a separate feature request for this.

@jeremystretch commented on GitHub (Apr 12, 2021): > In the new design where a location may represent a room, or some other nested object( room/aisle), it will be interesting to have the same stats information provided. This was proposed in #6126; please see the discussion there. > When Location represents a DC Room we can easily identify all the Racks inside, and most important we can also use the Images tab to document to room layout. Please open a separate feature request for this.
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 beta status: duplicate 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#4751
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?