diff options
| author | Christian Cleberg <[email protected]> | 2025-03-11 16:09:26 -0500 |
|---|---|---|
| committer | Christian Cleberg <[email protected]> | 2025-03-11 16:09:26 -0500 |
| commit | 8314ccc5364cbc9afa9653c2b02c5c58d433ade5 (patch) | |
| tree | fddf8653aa26a9486ed9e2f56c2215b1742f9f92 /content/blog/2024-09-20-prometheus-grafana-cloud.org | |
| parent | 526f853c7fdde80478b408ef78c42dcf8e3cdcf9 (diff) | |
| download | cleberg.net-8314ccc5364cbc9afa9653c2b02c5c58d433ade5.tar.gz cleberg.net-8314ccc5364cbc9afa9653c2b02c5c58d433ade5.tar.bz2 cleberg.net-8314ccc5364cbc9afa9653c2b02c5c58d433ade5.zip | |
move from cleberg.net to cmc.pub
Diffstat (limited to 'content/blog/2024-09-20-prometheus-grafana-cloud.org')
| -rw-r--r-- | content/blog/2024-09-20-prometheus-grafana-cloud.org | 18 |
1 files changed, 9 insertions, 9 deletions
diff --git a/content/blog/2024-09-20-prometheus-grafana-cloud.org b/content/blog/2024-09-20-prometheus-grafana-cloud.org index 4eb05aa..c0e9603 100644 --- a/content/blog/2024-09-20-prometheus-grafana-cloud.org +++ b/content/blog/2024-09-20-prometheus-grafana-cloud.org @@ -277,7 +277,7 @@ and determine what Grafana should do when an alert is triggered. ** OnCall #+caption: OnCall -[[https://img.cleberg.net/blog/20240920-prometheus-grafana-cloud/oncall.png]] +[[https://img.cmc.pub/blog/20240920-prometheus-grafana-cloud/oncall.png]] Within the Alerts & IRM section of Grafana (=/alerts-and-incidents=), open the Users page. @@ -299,12 +299,12 @@ users and teams to be on call for specific date and time ranges. For my purposes, I put myself on-call 24/7 so that I receive all alerts. #+caption: User Information -[[https://img.cleberg.net/blog/20240920-prometheus-grafana-cloud/irm_user_info.png]] +[[https://img.cmc.pub/blog/20240920-prometheus-grafana-cloud/irm_user_info.png]] ** Alerting #+caption: Alerting Insights -[[https://img.cleberg.net/blog/20240920-prometheus-grafana-cloud/alerting_insights.png]] +[[https://img.cmc.pub/blog/20240920-prometheus-grafana-cloud/alerting_insights.png]] Now that we have defined users and team associated with an on-call schedule and configured to receive the proper alerts, let's define a rule that will generate @@ -323,13 +323,13 @@ evaluation group. This is connected to our Grafana email, but can be associated with any notification policy. #+caption: New Alert Rule -[[https://img.cleberg.net/blog/20240920-prometheus-grafana-cloud/new_alert.png]] +[[https://img.cmc.pub/blog/20240920-prometheus-grafana-cloud/new_alert.png]] When the alert fires, it will generate an email (or whatever notification policy you assigned) and will look something like the following image. #+caption: Alerting Example -[[https://img.cleberg.net/blog/20240920-prometheus-grafana-cloud/email_alert.png]] +[[https://img.cmc.pub/blog/20240920-prometheus-grafana-cloud/email_alert.png]] ** Dashboards @@ -337,13 +337,13 @@ As promised above, here are some dashboard screenshots based on the configurations above. #+caption: Nginx Dashboard -[[https://img.cleberg.net/blog/20240920-prometheus-grafana-cloud/dashboard_nginx.png]] +[[https://img.cmc.pub/blog/20240920-prometheus-grafana-cloud/dashboard_nginx.png]] #+caption: Node Dashboard -[[https://img.cleberg.net/blog/20240920-prometheus-grafana-cloud/dashboard_node.png]] +[[https://img.cmc.pub/blog/20240920-prometheus-grafana-cloud/dashboard_node.png]] #+caption: OnCall Dashboard -[[https://img.cleberg.net/blog/20240920-prometheus-grafana-cloud/dashboard_oncall.png]] +[[https://img.cmc.pub/blog/20240920-prometheus-grafana-cloud/dashboard_oncall.png]] #+caption: Prometheus Dashboard -[[https://img.cleberg.net/blog/20240920-prometheus-grafana-cloud/dashboard_prometheus.png]] +[[https://img.cmc.pub/blog/20240920-prometheus-grafana-cloud/dashboard_prometheus.png]] |
