Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
InsaneSplash opened this issue Aug 28, 2017 · 1 comment
Closed

Comments

@InsaneSplash
Copy link

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.

@InsaneSplash InsaneSplash changed the title feature: reference graphs through API to remote system with auth token, feature: reference graphs through API to remote system with token Aug 28, 2017
@jeremystretch
Copy link
Member

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.

@lock lock bot locked as resolved and limited conversation to collaborators Jan 18, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants