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

JSON URL doesn't respect direct/browser datasource setting #13

Open
britcey opened this issue Aug 14, 2019 · 2 comments
Open

JSON URL doesn't respect direct/browser datasource setting #13

britcey opened this issue Aug 14, 2019 · 2 comments

Comments

@britcey
Copy link

britcey commented Aug 14, 2019

It would be nice if the JSON / JSONP URLs could either respect the datasource's access method [direct (server-side) or proxy (via the user's browser)] or be configured to explicitly do so.

My datasource is firewalled off but the Grafana server has access & I'd like to keep my location info there as well or just on the Grafana server and grab it via http://localhost/location_info.json

@amotl
Copy link

amotl commented Aug 14, 2019

Dear Ben,

thanks for writing in. As far as we can visualize your scenario, this feature would totally make sense to us.

While we can't promise any time frame, we will be happy to put it onto the general agenda and prioritize accordingly when we will be able to get back to the code.

For all others reading this: Contributions are very welcome.

With kind regards,
Andreas.

@britcey
Copy link
Author

britcey commented Aug 15, 2019

Thanks very much - BTW, I have 'direct' and 'proxy' reversed above - 'proxy' has the server fetch the URL, 'direct' has the user's browser fetch it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants