Improve {Prometheus, Grafana} Install & Configuration UX - Githubissues

kumahq / kuma-website

🐻 The official website for Kuma, the control plane for modern service connectivity.

https://kuma.io

Apache License 2.0

112 stars 90 forks source link

Improve {Prometheus, Grafana} Install & Configuration UX #628

Open johnharris85 opened 2 years ago

johnharris85 commented 2 years ago

Description

We provide a great OOTB experience to play with the entire metrics stack using kumactl install... however most users are already going to have a monitoring stack (that is already configured, has existing complex customizations, etc....). Prometheus-operator has a lot of the share here so we should:

Add docs to install our monitoring assets (dashboards / plugin) to an existing prometheus-operator (kube-prometheus) installation
(Maybe?) provide additional tooling to help this process

Probably a lot of the above can be parsed from our existing golden metrics install YAML and just tidied / published somewhere and then automated maybe?

lahabana commented 2 years ago

We should probably improve our documentation. Tooling is tricky because there are so many possible setups and the tooling would always fall short.

github-actions[bot] commented 2 years ago

This issue was inactive for 30 days it will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant please comment on it promptly or attend the next triage meeting.

lahabana commented 2 years ago

Some of it is done. We still don't explain well how to get the plugins dashboards. I have an idea but it's an update to our plugin.

github-actions[bot] commented 1 year ago

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.

github-actions[bot] commented 1 year ago

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.

github-actions[bot] commented 1 year ago

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.

github-actions[bot] commented 1 year ago

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.

github-actions[bot] commented 11 months ago

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.

github-actions[bot] commented 8 months ago

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.

github-actions[bot] commented 5 months ago

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.

github-actions[bot] commented 2 months ago

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.