fix alt-text for all remaining posts

1 files changed, 9 insertions, 0 deletions

diff --git a/content/blog/2024-09-20-prometheus-grafana-cloud.org b/content/blog/2024-09-20-prometheus-grafana-cloud.org
index 78ac68f..a00a9f3 100644
--- a/content/blog/2024-09-20-prometheus-grafana-cloud.org
+++ b/content/blog/2024-09-20-prometheus-grafana-cloud.org
@@ -276,6 +276,7 @@ and determine what Grafana should do when an alert is triggered.
 ** OnCall
 
 #+caption: OnCall
+#+attr_html: :alt View of the Grafana OnCall dashboard with metrics.
 [[https://img.cleberg.net/blog/20240920-prometheus-grafana-cloud/oncall.webp]]
 
 Within the Alerts & IRM section of Grafana (=/alerts-and-incidents=), open the
@@ -298,11 +299,13 @@ 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
+#+attr_html: :alt View of the grafanafd88 user with notification preferences.
 [[https://img.cleberg.net/blog/20240920-prometheus-grafana-cloud/irm_user_info.webp]]
 
 ** Alerting
 
 #+caption: Alerting Insights
+#+attr_html: :alt A dashboard with the current grafana-managed alert rules.
 [[https://img.cleberg.net/blog/20240920-prometheus-grafana-cloud/alerting_insights.webp]]
 
 Now that we have defined users and team associated with an on-call schedule and
@@ -322,12 +325,14 @@ evaluation group. This is connected to our Grafana email, but can be associated
 with any notification policy.
 
 #+caption: New Alert Rule
+#+attr_html: :alt All available seetings when creating a new alert.
 [[https://img.cleberg.net/blog/20240920-prometheus-grafana-cloud/new_alert.webp]]
 
 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
+#+attr_html: :alt An email showing that "High CPU Temps" alert is firing.
 [[https://img.cleberg.net/blog/20240920-prometheus-grafana-cloud/email_alert.webp]]
 
 ** Dashboards
@@ -336,13 +341,17 @@ As promised above, here are some dashboard screenshots based on the
 configurations above.
 
 #+caption: Nginx Dashboard
+#+attr_html: :alt Updated dashboard based on the new alert created above.
 [[https://img.cleberg.net/blog/20240920-prometheus-grafana-cloud/dashboard_nginx.webp]]
 
 #+caption: Node Dashboard
+#+attr_html: :alt Metrics of server nodes, including CPU, network, and memory.
 [[https://img.cleberg.net/blog/20240920-prometheus-grafana-cloud/dashboard_node.webp]]
 
 #+caption: OnCall Dashboard
+#+attr_html: :alt Full OnCall dashboard with metrics for alerts, mean time to respond, and more.
 [[https://img.cleberg.net/blog/20240920-prometheus-grafana-cloud/dashboard_oncall.webp]]
 
 #+caption: Prometheus Dashboard
+#+attr_html: :alt Dashboard showing Prometheus metrics, including scrape duration, head shunks, reload count, and more.
 [[https://img.cleberg.net/blog/20240920-prometheus-grafana-cloud/dashboard_prometheus.webp]]