Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upPrometheus external_labels not available in Grafana #3049
Comments
This comment has been minimized.
This comment has been minimized.
|
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? |
This comment has been minimized.
This comment has been minimized.
|
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) |
This comment has been minimized.
This comment has been minimized.
|
Grafana should generally talk directly to the Prometheus that has the data you want. Likely via data source templating in your case. |
brian-brazil
closed this
Aug 21, 2017
This comment has been minimized.
This comment has been minimized.
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. |
bkupidura commentedAug 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? ;)