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 Monitoring - Observium, LibreNMS..... #119

New Issue
Closed
opened 2025-12-29 15:33:53 +01:00 by adam · 4 comments
adam commented 2025-12-29 15:33:53 +01:00
Owner
Copy Link

Originally created by @x-zeroflux-x on GitHub (Jul 1, 2016).

Hi Everyone,

Commercial DCIM platforms seem to do it all - the monitoring, alerting, asset management, subnet management, etc.

Unfortunately from past experience that they are very overpriced, are vendor specific and when implemented only 20% of the actual feature sets are used because their not implemented properly.

Not wanting to turn netbox into a monitoring tool and given that there are plenty of good monitoring tools out there, I would like to open discussion on the possibility of connecting netbox to a 3rd party monitoring system many of them out there that uses an API.

Currently i see a basic polling and graphing feature is in place for v1 of the release which means some thought has been put into this from the original idea.

What is your vision with this?

Originally created by @x-zeroflux-x on GitHub (Jul 1, 2016). Hi Everyone, Commercial DCIM platforms seem to do it all - the monitoring, alerting, asset management, subnet management, etc. Unfortunately from past experience that they are very overpriced, are vendor specific and when implemented only 20% of the actual feature sets are used because their not implemented properly. Not wanting to turn netbox into a monitoring tool and given that there are plenty of good monitoring tools out there, I would like to open discussion on the possibility of connecting netbox to a 3rd party monitoring system many of them out there that uses an API. Currently i see a basic polling and graphing feature is in place for v1 of the release which means some thought has been put into this from the original idea. What is your vision with this?
adam closed this issue 2025-12-29 15:33:53 +01:00
adam commented 2025-12-29 15:33:54 +01:00
Author
Owner
Copy Link

@mdomore commented on GitHub (Jul 1, 2016):

Yes i can only dream to enter my device in netbox and it create an entry in my observium, and after pulling netbox get back for exemple inventory from observium :)

@mdomore commented on GitHub (Jul 1, 2016): Yes i can only dream to enter my device in netbox and it create an entry in my observium, and after pulling netbox get back for exemple inventory from observium :)
adam commented 2025-12-29 15:33:54 +01:00
Author
Owner
Copy Link

@bellwood commented on GitHub (Jul 1, 2016):

There is a hooks system / API that will be available to tie things into external services once it is completed.

Netbox is not slated to be an all-in-one system as it's design is IPAM/DCIM - not monitoring, ticketing, abuse, etc.

@bellwood commented on GitHub (Jul 1, 2016): There is a hooks system / API that will be available to tie things into external services once it is completed. Netbox is not slated to be an all-in-one system as it's design is IPAM/DCIM - not monitoring, ticketing, abuse, etc.
adam commented 2025-12-29 15:33:54 +01:00
Author
Owner
Copy Link

@mdomore commented on GitHub (Jul 1, 2016):

Sure observium is doing a fine job and netbox is not observium but there is some informations in common.

@mdomore commented on GitHub (Jul 1, 2016): Sure observium is doing a fine job and netbox is not observium but there is some informations in common.
adam commented 2025-12-29 15:33:55 +01:00
Author
Owner
Copy Link

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

The API should provide all the information necessary to populate monitoring systems with node data. I'm going to close out this issue, but if you encounter a specific limitation with the API which isn't already being addressed, feel free to open a new issue.

@jeremystretch commented on GitHub (Jul 19, 2016): The API should provide all the information necessary to populate monitoring systems with node data. I'm going to close out this issue, but if you encounter a specific limitation with the API which isn't already being addressed, feel free to open a new issue.
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#119
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?