docs(cpt): feedback

Author: nerda-codes

pages/cockpit/how-to/configure-alerts-for-scw-resources.mdx

@@ -8,12 +8,12 @@ content:
 categories:
   - observability cockpit
 dates:
-  validation: 2025-05-09
+  validation: 2025-05-12
   posted: 2023-11-06
 ---
 
 
-Cockpit does not support Grafana-managed alerting. It integrates with Grafana to visualize metrics, but alerts are managed through the Scaleway alert manager. You should use Grafana only to define alert rules, not to evaluate or receive alert notifications. Once the conditions of your alert rule are met, the Scaleway alert manager evaluates the rule and sends a notification to the **contact points you have configured in the Scaleway console**.
+Cockpit does not support Grafana-managed alerting. It integrates with Grafana to visualize metrics, but alerts are managed through the Scaleway alert manager. You should use Grafana only to define alert rules, not to evaluate or receive alert notifications. Once the conditions of your alert rule are met, the Scaleway alert manager evaluates the rule and sends a notification to the contact points you have configured in the Scaleway console or in Grafana.
 
 This page shows you how to create alert rules in Grafana for monitoring Scaleway resources integrated with Cockpit, such as Instances, Object Storage, and Kubernetes. These alerts rely on Scaleway-provided metrics, which are preconfigured and available in the **Metrics browser** drop-down when using the **Scaleway Metrics data source** in the Grafana interface. This page explains how to use the `Scaleway Metrics` data source, interpret metrics, set alert conditions, and activate alerts.
 
@@ -24,8 +24,7 @@ This page shows you how to create alert rules in Grafana for monitoring Scaleway
   - Scaleway resources you can monitor
   - [Created Grafana credentials](/cockpit/how-to/retrieve-grafana-credentials/) with the **Editor** role
   - [Enabled](/cockpit/how-to/enable-alert-manager/) the Scaleway alert manager
-  - [Created](/cockpit/how-to/add-contact-points/) at least one contact point **in the Scaleway console**, otherwise, alerts will not be delivered
-  - Selected the **Scaleway Alerting** alert manager in Grafana
+  - [Created](/cockpit/how-to/add-contact-points/) a contact point in the Scaleway console or in Grafana (with the `Scaleway Alerting` alert manager of the same region as your `Scaleway Metrics` data source), otherwise alerts will not be delivered
 
 ## Switch to data source managed alert rules
 
@@ -45,8 +44,8 @@ Switch between the tabs below to create alerts for a Scaleway Instance, an Objec
   <TabsTab label="Scaleway Instance">
     The steps below explain how to create the metric selection and configure an alert condition that triggers when **your Instance consumes more than 10% of a single CPU core over the past 5 minutes.**
 
-    1. Type a name for your alert.
-    2. Select the data source you want to configure alerts for. For the sake of this documentation, we are choosing the **Scaleway Metrics** data source.
+    1. Type a name for your alert. For example, `alert-for-high-cpu-usage`.
+    2. Select the **Scaleway Metrics** data source.
     3. Click the **Metrics browser** drop-down.
         <Lightbox src="scaleway-metrics-browser.webp" alt="" />
         <Lightbox src="scaleway-metrics-displayed.webp" alt="" />
@@ -57,26 +56,26 @@ Switch between the tabs below to create alerts for a Scaleway Instance, an Objec
     5. Select the appropriate labels to filter your metric and target specific resources.
     6. Choose values for your selected labels. The **Resulting selector** field displays your final query selector.
         <Lightbox src="scaleway-metric-selection.webp" alt="" />
-    7. Click **Use query** to validate your metric selection. Your selection displays in the query field next to the **Metrics browser** button. This prepares it for use in the alert condition, which we will define in the next steps.
-    8. In the query field, paste the following query. Make sure that the values for the labels you have selected (for example, `resource_id` and `resource_name`) correspond to those of the target resource.
+    7. Click **Use query** to validate your metric selection.
+    8. In the query field next to the **Metrics browser** button, paste the following query. Make sure that the values for the labels you have selected (for example, `resource_id` and `resource_name`) correspond to those of the target resource.
         ```bash
         rate(instance_server_cpu_seconds_total{resource_id="xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",resource_name="name-of-your-resource"}[5m]) > 0.1
         ```
     9. In the **Set alert evaluation behavior** field, specify how long the condition must be true before triggering the alert.
+    10. Enter a name in the **Namespace** and **Group** fields to categorize and manage your alert, and optionally, add annotations.
+    11. Enter a label in the **Labels** field and a name in the **Value** field.
         <Message type="note">
-         For example, to wait until the condition has been met continuously for 5 minutes, type `5` and select `minutes` in the drop-down.
+         In Grafana, notifications are sent by matching alerts to notification policies based on labels. This step is about deciding how alerts will reach you or your team (Slack, email, etc.) based on labels you attach to them. Then, you can set up rules that define who receives notifications in the **Notification policies** page.
+         For example, if an alert has the label `team = instances-team`, you are telling Grafana to send a notification to the Instances team when your alert `alert-for-high-cpu-usage` gets triggered. Find out how to [configure notification policies in Grafana](/tutorials/configure-slack-alerting/#configuring-a-notification-policy).
         </Message>
-    10. Enter a namespace in the **Namespace** field to help you categorize and manage your alert, then click **Enter**.
-    11. Enter a name in the **Group** field to help you categorize and manage your alert, then click **Enter**.
-    12. Optionally, add a summary and a description.
-    13. Click **Save rule** in the top right corner of your screen to save and activate your alert.
-    14. Optionally, check that your configuration works by temporarily lowering the threshold. This will trigger the alert and your [contact point](/cockpit/concepts/#contact-points) should receive an email informing them that the alert is firing.
+    12. Click **Save rule** in the top right corner of your screen to save and activate your alert.
+    13. Optionally, check that your configuration works by temporarily lowering the threshold. This will trigger the alert and notify your [contact point](/cockpit/concepts/#contact-points).
   </TabsTab>
   <TabsTab label="Object Storage bucket">
     The steps below explain how to create the metric selection and configure an alert condition that triggers when **the object count in your bucket exceeds a specific threshold**.
 
     1. Type a name for your alert.
-    2. Select the data source you want to configure alerts for. For the sake of this documentation, we are choosing the **Scaleway Metrics** data source.
+    2. Select the **Scaleway Metrics** data source.
     3. Click the **Metrics browser** drop-down.
         <Lightbox src="scaleway-metrics-browser.webp" alt="" />
         <Lightbox src="scaleway-metrics-displayed.webp" alt="" />
@@ -92,20 +91,20 @@ Switch between the tabs below to create alerts for a Scaleway Instance, an Objec
         object_storage_bucket_objects_total{region="fr-par", resource_id="my-bucket"} > 2000
         ```
     9. In the **Set alert evaluation behavior** field, specify how long the condition must be true before triggering the alert.
+    10. Enter a name in the **Namespace** and **Group** fields to categorize and manage your alert, and optionally, add annotations.
+    11. Enter a label in the **Labels** field and a name in the **Value** field.
         <Message type="note">
-         For example, to wait until the condition has been met continuously for 5 minutes, type `5` and select `minutes` in the drop-down.
+         In Grafana, notifications are sent by matching alerts to notification policies based on labels. This step is about deciding how alerts will reach you or your team (Slack, email, etc.) based on labels you attach to them. Then, you can set up rules that define who receives notifications in the **Notification policies** page.
+         For example, if an alert has the label `team = object-storage-team`, you are telling Grafana to send a notification to the Object Storage team when your alert is firing. Find out how to [configure notification policies in Grafana](/tutorials/configure-slack-alerting/#configuring-a-notification-policy).
         </Message>
-    10. Enter a namespace in the **Namespace** field to help you categorize and manage your alert, then click **Enter**.
-    11. Enter a name in the **Group** field to help you categorize and manage your alert, then click **Enter**.
-    12. Optionally, add a summary and a description.
-    13. Click **Save rule** in the top right corner of your screen to save and activate your alert.
-    14. Optionally, check that your configuration works by temporarily lowering the threshold. This will trigger the alert and your [contact point](/cockpit/concepts/#contact-points) should receive an email informing them that the alert is firing.
+    12. Click **Save rule** in the top right corner of your screen to save and activate your alert.
+    13. Optionally, check that your configuration works by temporarily lowering the threshold. This will trigger the alert and notify your [contact point](/cockpit/concepts/#contact-points).
   </TabsTab>
   <TabsTab label="Kubernetes pod">
     The steps below explain how to create the metric selection and configure an alert condition that triggers when **no new pod activity occurs, which could mean your cluster is stuck or unresponsive.**
 
     1. Type a name for your alert.
-    2. Select the data source you want to configure alerts for. For the sake of this documentation, we are choosing the **Scaleway Metrics** data source.
+    2. Select the **Scaleway Metrics** data source.
     3. Click the **Metrics browser** drop-down.
         <Lightbox src="scaleway-metrics-browser.webp" alt="" />
         <Lightbox src="scaleway-metrics-displayed.webp" alt="" />
@@ -121,20 +120,20 @@ Switch between the tabs below to create alerts for a Scaleway Instance, an Objec
         rate(kubernetes_cluster_k8s_shoot_nodes_pods_usage_total{resource_name="k8s-par-quizzical-chatelet"}[15m]) == 0
         ```
     9. In the **Set alert evaluation behavior** field, specify how long the condition must be true before triggering the alert.
+    10. Enter a name in the **Namespace** and **Group** fields to categorize and manage your alert, and optionally, add annotations.
+    11. Enter a label in the **Labels** field and a name in the **Value** field.
         <Message type="note">
-         For example, to wait until the condition has been met continuously for 5 minutes, type `5` and select `minutes` in the drop-down.
+         In Grafana, notifications are sent by matching alerts to notification policies based on labels. This step is about deciding how alerts will reach you or your team (Slack, email, etc.) based on labels you attach to them. Then, you can set up rules that define who receives notifications in the **Notification policies** page.
+         For example, if an alert has the label `team = kubernetes-team`, you are telling Grafana to send a notification to the Kubernetes team when your alert is firing. Find out how to [configure notification policies in Grafana](/tutorials/configure-slack-alerting/#configuring-a-notification-policy).
         </Message>
-    10. Enter a namespace in the **Namespace** field to help you categorize and manage your alert, then click **Enter**.
-    11. Enter a name in the **Group** field to help you categorize and manage your alert, then click **Enter**.
-    12. Optionally, add a summary and a description.
-    13. Click **Save rule** in the top right corner of your screen to save and activate your alert.
-    14. Optionally, check that your configuration works by temporarily lowering the threshold. This will trigger the alert and your [contact point](/cockpit/concepts/#contact-points) should receive an email informing them that the alert is firing.
+    12. Click **Save rule** in the top right corner of your screen to save and activate your alert.
+    13. Optionally, check that your configuration works by temporarily lowering the threshold. This will trigger the alert and notify your [contact point](/cockpit/concepts/#contact-points).
   </TabsTab>
   <TabsTab label="Cockpit logs">
     The steps below explain how to create the metric selection and configure an alert condition that triggers when **no logs are stored for 5 minutes, which may indicate your app or system is broken**.
 
     1. Type a name for your alert.
-    2. Select the data source you want to configure alerts for. For the sake of this documentation, we are choosing the **Scaleway Metrics** data source.
+    2. Select the **Scaleway Metrics** data source.
     3. Click the **Metrics browser** drop-down.
         <Lightbox src="scaleway-metrics-browser.webp" alt="" />
         <Lightbox src="scaleway-metrics-displayed.webp" alt="" />
@@ -150,18 +149,18 @@ Switch between the tabs below to create alerts for a Scaleway Instance, an Objec
         observability_cockpit_loki_chunk_store_stored_chunks_total:increase5m{resource_id="xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"} == 0
         ```
     9. In the **Set alert evaluation behavior** field, specify how long the condition must be true before triggering the alert.
+    10. Enter a name in the **Namespace** and **Group** fields to categorize and manage your alert, and optionally, add annotations.
+    11. Enter a label in the **Labels** field and a name in the **Value** field.
         <Message type="note">
-         For example, to wait until the condition has been met continuously for 5 minutes, type `5` and select `minutes` in the drop-down.
+         In Grafana, notifications are sent by matching alerts to notification policies based on labels. This step is about deciding how alerts will reach you or your team (Slack, email, etc.) based on labels you attach to them. Then, you can set up rules that define who receives notifications in the **Notification policies** page.
+         For example, if an alert has the label `team = cockpit-team`, you are telling Grafana to send a notification to the Cockpit team when your alert is firing. Find out how to [configure notification policies in Grafana](/tutorials/configure-slack-alerting/#configuring-a-notification-policy).
         </Message>
-    10. Enter a namespace in the **Namespace** field to help you categorize and manage your alert, then click **Enter**.
-    11. Enter a name in the **Group** field to help you categorize and manage your alert, then click **Enter**.
-    12. Optionally, add a summary and a description.
-    13. Click **Save rule** in the top right corner of your screen to save and activate your alert. Your alert will start evaluating based on the rule you have defined.
-    14. Optionally, check that your configuration works by temporarily lowering the threshold. This will trigger the alert and your [contact point](/cockpit/concepts/#contact-points) should receive an email informing them that the alert is firing.
+    12. Click **Save rule** in the top right corner of your screen to save and activate your alert.
+    13. Optionally, check that your configuration works by temporarily lowering the threshold. This will trigger the alert and notify your [contact point](/cockpit/concepts/#contact-points).
   </TabsTab>
 </Tabs>
 
-You can view your firing alerts in the **Alert rules** section of your Grafana (Home > Alerting > Alert rules).
+You can view your firing alerts in the **Alert rules** section of your Grafana (**Home** > **Alerting** > **Alert rules**).
 
 <Lightbox src="scaleway-alerts-firing.webp" alt="" />