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

Overriding the datasource location #35

Closed
rfc1036 opened this issue Nov 25, 2020 · 3 comments
Closed

Overriding the datasource location #35

rfc1036 opened this issue Nov 25, 2020 · 3 comments

Comments

@rfc1036
Copy link

rfc1036 commented Nov 25, 2020

Feature request: I use this great plugin to enhance the HVAC graphs of our data centers, but since they are located at very different latitudes I need to be able to override the global datasource location at least per dashboard (even better: per panel).

@fetzerch
Copy link
Owner

That's on my list for long time.

Would this work for you:

grafik

@rfc1036
Copy link
Author

rfc1036 commented Nov 25, 2020

I was wondering if it could be possible to use the new generic override mechanism but sure, this would work fine.

@fetzerch
Copy link
Owner

I do know that it's possible to use this for aliases, but i haven't seen anything for dashboard options.
What's still missing in my prototype is that variables can't be entered. I suppose that's useful as well.

fetzerch added a commit that referenced this issue Nov 27, 2020
Add latitude/longitude fields to the query editor so that the location
can be overridden on a per query basis. The fields support variables.

Fixes: #35, Fixes: #5.
fetzerch added a commit that referenced this issue Nov 27, 2020
Add latitude/longitude fields to the query editor so that the location
can be overridden on a per query basis. The fields support variables.

Fixes: #35, Fixes: #5.
fetzerch added a commit that referenced this issue Nov 27, 2020
Add latitude/longitude fields to the query editor so that the location
can be overridden on a per query basis. The fields support variables.

Fixes: #35, Fixes: #5.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants