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 Details #222

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

Originally created by @tchmnkyz on GitHub (Jul 14, 2016).

It would be nice to be able to track the Memory, CPU, Disks (components) of a server. Also some kind of integration into maybe puppet and other configuration management applications would be nice also.

If possible, it would be nice to be able to Link a Specific graph to a interface as well as add specific graphs for each device (think CPU/Memory/etc).

Originally created by @tchmnkyz on GitHub (Jul 14, 2016). It would be nice to be able to track the Memory, CPU, Disks (components) of a server. Also some kind of integration into maybe puppet and other configuration management applications would be nice also. If possible, it would be nice to be able to Link a Specific graph to a interface as well as add specific graphs for each device (think CPU/Memory/etc).
adam closed this issue 2025-12-29 16:19:37 +01:00
adam commented 2025-12-29 16:19:37 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 14, 2016):

There are three unrelated features described here.

It would be nice to be able to track the Memory, CPU, Disks (components) of a server.

There are several existing feature requests around the modules system that probably cover this.

Also some kind of integration into maybe puppet and other configuration management applications would be nice also.

This is out of scope for the foreseeable future.

If possible, it would be nice to be able to Link a Specific graph to a interface as well as add specific graphs for each device (think CPU/Memory/etc).

Graphs can already be defined for interfaces. Module graphs might be workable but not until after the existing feature requests are implemented.

@jeremystretch commented on GitHub (Jul 14, 2016): There are three unrelated features described here. > It would be nice to be able to track the Memory, CPU, Disks (components) of a server. There are several existing feature requests around the modules system that probably cover this. > Also some kind of integration into maybe puppet and other configuration management applications would be nice also. This is out of scope for the foreseeable future. > If possible, it would be nice to be able to Link a Specific graph to a interface as well as add specific graphs for each device (think CPU/Memory/etc). Graphs can already be defined for interfaces. Module graphs might be workable but not until after the existing feature requests are implemented.
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
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#222
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?