It looks like kubernetes-control-plane is related to telegraf via a `juju-info` relation which won't really include the info we need to generate the dashboard correctly. I don't see any other relation endpoints for telegraf that would be more appropriate.
So to fix this, I think we would either need to:
1. Add a `telegraf-hostname` config option to kubernetes-control-plane, or
2. Develop a `telegraf:kubernetes` endpoint to use instead of juju-info so we can get the hostname config from telegraf.
Realistically, I suspect this is a Won't Fix as we look toward the future of observability via the COS stack based on the grafana-agent charm[1] for exporting metrics. I'll leave this issue open for now until we have a better idea what's coming.
It looks like kubernetes- control- plane is related to telegraf via a `juju-info` relation which won't really include the info we need to generate the dashboard correctly. I don't see any other relation endpoints for telegraf that would be more appropriate.
So to fix this, I think we would either need to: control- plane, or kubernetes` endpoint to use instead of juju-info so we can get the hostname config from telegraf.
1. Add a `telegraf-hostname` config option to kubernetes-
2. Develop a `telegraf:
Realistically, I suspect this is a Won't Fix as we look toward the future of observability via the COS stack based on the grafana-agent charm[1] for exporting metrics. I'll leave this issue open for now until we have a better idea what's coming.
[1]: https:/ /charmhub. io/grafana- agent