How to configure alerts for Scaleway resources in Grafana

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 Scaleway Metrics data source.
3. Click the Metrics browser drop-down.
   
   
4. Select the metric you want to configure an alert for. For example, object_storage_bucket_objects_total.
   Tip

   The object_storage_bucket_objects_total metric indicates the total number of objects stored in a given Object Storage bucket. It is useful to monitor and control object growth in your bucket and avoid hitting thresholds.

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.
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 region) correspond to those of the target resource.

   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. You can skip this step if you want your alerts to be sent to the contact points you may already have created in the Scaleway console.
    Note

    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.

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.

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 Scaleway Metrics data source.
3. Click the Metrics browser drop-down.
   
   
4. Select the metric you want to configure an alert for. For example, kubernetes_cluster_k8s_shoot_nodes_pods_usage_total.
   Tip

   The kubernetes_cluster_k8s_shoot_nodes_pods_usage_total metric represents the total number of pods currently running across all nodes in your Kubernetes cluster. It is helpful to monitor current pod consumption per node pool or cluster, and help track resource saturation or unexpected workload spikes.

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.
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_name) correspond to those of the target resource.

   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. You can skip this step if you want your alerts to be sent to the contact points you may already have created in the Scaleway console.
    Note

    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.

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.

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 Scaleway Metrics data source.
3. Click the Metrics browser drop-down.
   
   
4. Select the metric you want to configure an alert for. For example, observability_cockpit_loki_chunk_store_stored_chunks_total:increase5m.
   Tip

   The observability_cockpit_loki_chunk_store_stored_chunks_total:increase5m metric represents the number of chunks (log storage blocks) that have been written over the last 5 minutes for a specific resource. It is useful to monitor log ingestion activity and detect issues such as a crash of the logging agent, or your application not producing logs.

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.
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_name) correspond to those of the target resource.

   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. You can skip this step if you want your alerts to be sent to the contact points you may already have created in the Scaleway console.
    Note

    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.

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.