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

Prometheus external_labels not available in Grafana #3049

Closed
bkupidura opened this Issue Aug 10, 2017 · 4 comments

Comments

Projects
None yet
2 participants
@bkupidura
Copy link

bkupidura commented Aug 10, 2017

Probably this is intentional behavior, but prometheus dosen't add external_labels to queries send by Grafana.

This can be useful for ex. exposing information about region name.

Can we treat that as feature requests? ;)

@brian-brazil

This comment has been minimized.

Copy link
Member

brian-brazil commented Aug 10, 2017

Yes, that's intended currently. The presumption is you already know that due to the data source. If that not sufficient for you use case?

@bkupidura

This comment has been minimized.

Copy link
Author

bkupidura commented Aug 10, 2017

Right now we are thinking how we can support multi-region deployments. So we are researching about what options do we have, but we dont have ready architecture yet.

But you have a point, in case we choose to federate "side-prometheuses" to "global-prometheus" external_labels will be there.

Region name available in "side-prometheuses" would be useful for us because we have already region_name in our logging solution. From user perspective it would be nice to be 100% sure that you are watching metrics from right environment. (in case federation would not be used)

@brian-brazil

This comment has been minimized.

Copy link
Member

brian-brazil commented Aug 10, 2017

Grafana should generally talk directly to the Prometheus that has the data you want. Likely via data source templating in your case.

@lock

This comment has been minimized.

Copy link

lock bot commented Mar 23, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Mar 23, 2019

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.