| 2020-05-01 20:56:32 |
Zachary Zehring |
description |
Due to the migration of charms to use interface-grafana-dashboard to import dashboards to Grafana, prometheus needs to have a way to communicate to these charms various details needed for rendering the details of the dashboard. Grafana currently gets this information from interface-grafana-source, where prometheus provides the url to query metrics.
This new interface would need to relay the following information:
- datasource name: comprised of the service name, or the name of the application, and the description, currently set to Juju generated source)
- url: prometheus's URL used to query metrics. For example, in telegraf charm, there's logic around rendering the dashboard template regarding these metrics
With this interface, a provider for interface-grafana-dashboard can generate a template correctly, without any hardcoding of values, and pass the resulting dashboard along the relation to Grafana. |
Due to the migration of charms to use interface-grafana-dashboard to import dashboards to Grafana, prometheus needs to have a way to communicate to these charms various details needed for rendering the details of the dashboard. Grafana currently gets this information from interface-grafana-source, where prometheus provides the url to query metrics.
This new interface would need to relay the following information:
- datasource name: comprised of the service name, or the name of the application, and the description, currently set to Juju generated source)
- url: prometheus's URL used to query metrics. For example, in telegraf charm, there's logic around rendering the dashboard template regarding these metrics
With this interface, a provider for interface-grafana-dashboard can generate a template correctly, without any hardcoding of values, by grabbing them from the prometheus relation and passing the resulting dashboard along the relation to Grafana. |
|
