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

feature: reference graphs through API to remote system with token #1198

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

Originally created by @InsaneSplash on GitHub (Aug 28, 2017).

Issue type

[X ] Feature request
[ ] Bug report
[ ] Documentation

Environment

  • Python version: 2.7
  • NetBox version: 2.1.3

Description

A number of monitoring and graphing systems make available device/port graphs through an API rather than a direct unauthed URL. It would be helpful to be able to reference these graphs using an API call with a token to improve on the graph integration.

Having said this, sometimes it is also necessary to to pull the graph information from multiple sources depending on the device being referenced. Based on the current implementation there isn't a way to set a specific graph template per customer/site.

Originally created by @InsaneSplash on GitHub (Aug 28, 2017). ### Issue type [X ] Feature request <!-- Requesting the implementation of a new feature --> [ ] Bug report <!-- Reporting unexpected or erroneous behavior --> [ ] Documentation <!-- Proposing a modification to the documentation --> ### Environment * Python version: 2.7 * NetBox version: 2.1.3 ### Description A number of monitoring and graphing systems make available device/port graphs through an API rather than a direct unauthed URL. It would be helpful to be able to reference these graphs using an API call with a token to improve on the graph integration. Having said this, sometimes it is also necessary to to pull the graph information from multiple sources depending on the device being referenced. Based on the current implementation there isn't a way to set a specific graph template per customer/site.
adam closed this issue 2025-12-29 16:29:59 +01:00
adam commented 2025-12-29 16:30:00 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 28, 2017):

This was discussed on the mailing list recently. Because the graphs are embedded using <img> tags, there is no mechanism available for sending an authorization header with the request. It might be possible with an AJAX request but you have to jump through some hoops to embed the retrieved image and I'm not interested in going down that path.

Having said this, sometimes it is also necessary to to pull the graph information from multiple sources depending on the device being referenced.

The embedded graphs were only ever meant to be a convenience feature. If you have a single NMS with no or basic authentication, great. If not, it won't fit your needs; #969 should provide a better solution in that case.

@jeremystretch commented on GitHub (Aug 28, 2017): This was [discussed on the mailing list](https://groups.google.com/forum/#!topic/netbox-discuss/h7HAIPbylUo) recently. Because the graphs are embedded using `<img>` tags, there is no mechanism available for sending an authorization header with the request. It might be possible with an AJAX request but you have to jump through some hoops to embed the retrieved image and I'm not interested in going down that path. > Having said this, sometimes it is also necessary to to pull the graph information from multiple sources depending on the device being referenced. The embedded graphs were only ever meant to be a convenience feature. If you have a single NMS with no or basic authentication, great. If not, it won't fit your needs; #969 should provide a better solution in that case.
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#1198
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?