Skip to content

feat(docs): update ckpt docs with new grafana ui #5298

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion macros/edge-services/edge-services-bucket-benefits.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -2,9 +2,11 @@
macro: edge-services-bucket-benefits
---

import EdgeServicesPipelineNoWAF from './assets/scaleway-edge-services-pipeline-nowaf.webp'

- Customize your bucket's endpoint using a subdomain of your own domain
- Add your own SSL/TLS certificate, safeguarded in [Scaleway Secret Manager](/secret-manager/quickstart/), or generate a managed Let's Encrypt certificate, so your subdomain can serve content from your bucket over HTTPS
- Enhance performance by caching your stored objects, to be served directly by Edge Services from the cache
- Finely control your cached objects via purging (cache invalidation)

<Lightbox src="scaleway-edge-services-pipeline-nowaf.webp" alt="A diagram shows the elements and workflow of an Edge Services pipeline. The user connects to the customizable Edge Services endpoint (with its SSL/TLS certificate), which fetches content from the Edge Services cache, which itself fetches content to cache from an origin which is either an Object Storage bucket or Load Balancer" />
<Lightbox image={EdgeServicesPipelineNoWAF} alt="A diagram shows the elements and workflow of an Edge Services pipeline. The user connects to the customizable Edge Services endpoint (with its SSL/TLS certificate), which fetches content from the Edge Services cache, which itself fetches content to cache from an origin which is either an Object Storage bucket or Load Balancer" />
4 changes: 3 additions & 1 deletion macros/edge-services/edge-services-lb-benefits.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -2,9 +2,11 @@
macro: edge-services-lb-benefits
---

import EdgeServicesPipelineDiag from './assets/scaleway-edge-services-pipeline-diag.webp'

Creating an Edge Services pipeline for your Load Balancer helps to reduce load on your Load Balancer's backend servers. The origin configuration you define is used by Edge Services to connect to your Load Balancer and request content, which is then stored in the cache. Then, when your Load Balancer origin is accessed via its customizable Edge Services endpoint, the requested content is served from the cache (if present), without the need to fetch this content via the Load Balancer and its backend servers.

<Lightbox src="scaleway-edge-services-pipeline-diag.webp" alt="A diagram shows the elements and workflow of an Edge Services pipeline. The user connects to the customizable Edge Services endpoint (with its SSL/TLS certificate), which fetches content from the Edge Services cache, which itself fetches content to cache from an origin which is either an Object Storage bucket or Load Balancer" />
<Lightbox image={EdgeServicesPipelineDiag} alt="A diagram shows the elements and workflow of an Edge Services pipeline. The user connects to the customizable Edge Services endpoint (with its SSL/TLS certificate), which fetches content from the Edge Services cache, which itself fetches content to cache from an origin which is either an Object Storage bucket or Load Balancer" />

Edge Services lets you:

Expand Down
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
174 changes: 77 additions & 97 deletions pages/cockpit/how-to/configure-alerts-for-scw-resources.mdx

Large diffs are not rendered by default.

24 changes: 11 additions & 13 deletions tutorials/configure-slack-alerting/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -5,10 +5,10 @@ categories:
- cockpit
tags: cockpit alerts monitoring notifications slack
dates:
validation: 2025-02-18
validation: 2025-07-18
posted: 2025-02-18
---
import image from './assets/scaleway-slack-alerts-firing.webp'
import SlackNotification from './assets/scaleway-slack-alerts-firing.webp'

import Requirements from '@macros/iam/requirements.mdx'

Expand Down Expand Up @@ -52,34 +52,32 @@ As **we do not support Grafana managed alerts**, this documentation only shows y

## Creating your Slack integration in Grafana using the Scaleway Alerting alert manager

1. [Access](/cockpit/how-to/access-grafana-and-managed-dashboards/) your Grafana dashboard.
2. Click the **Toggle menu** icon next to **Home** in the top left corner of your screen.
3. Click **Alerting**, then click **Contact points**.
1. [Log in to Grafana](/cockpit/how-to/access-grafana-and-managed-dashboards/) using your credentials.
2. Click the Grafana icon in the top left side of your screen to open the menu.
3. Click the arrow next to **Alerting** on the left-side menu, then click **Contact points**.
4. Choose the **Scaleway Alerting** alert manager in the drop-down next to the **Choose Alertmanager** field.
5. Click **+ Add contact point**.
5. Click **+ Create contact point**.
6. Enter a contact point name. For example, `Slack alerts`.
7. Select **Slack** from the **Integration** drop-down.
8. In the **Channel** field, paste the name of the Slack channel or user to send notifications to.
9. Click **Optional Slack settings** and paste your Slack app Webhook URL in the **Webhook URL** field.
10. Click **Save contact point**.

<Message type="important">
If you have already created contact points, you need to [configure a nested notification policy](#configuring-a-notification-policy) to define which contact point should receive which alert.
If you have already created contact points, you need to [configure a child notification policy](#configuring-a-notification-policy) to define which contact point should receive which alert.
</Message>

## Configuring a notification policy

If you have created multiple contact points in Grafana, the default contact point will receive alerts by default. To make sure your alerts are sent to the desired contact point, you need to define notification policies.

1. [Access](/cockpit/how-to/access-grafana-and-managed-dashboards/) your Grafana dashboard.
2. Click the **Toggle menu** icon next to **Home** in the top left corner of your screen.
3. Click **Alerting**, then click **Notification policies**.
4. Click **+ New nested policy**.
1. Click **Alerting**, then click **Notification policies**.
4. Click **+ New child policy**.
5. In the **Label** field, enter the label `alertname`.
6. In the **Operator** field, select **Equals**.
7. In the **Value** field, enter the name of an existing alert you want your contact point to be notified for. For example, `alert-for-high-cpu-usage`.
8. Optionally, click **+Add matcher** to add more labels.
9. In the **Contact point** field, select the contact point you have configured for Slack.
9. In the **Contact point** drop-down, select the contact point you have configured for Slack.
10. Click **Save policy**. Your nested policy displays. You should now get notified on Slack.

<Lightbox image={image} alt="Grafana alert for high CPU usage notification on Slack" />
<Lightbox image={SlackNotification} alt="Grafana alert for high CPU usage notification on Slack" />
6 changes: 3 additions & 3 deletions tutorials/silence-grafana-alerts/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ tags: cockpit alerts mute silence monitoring notifications
categories:
- cockpit
dates:
validation: 2025-06-16
validation: 2025-07-18
posted: 2025-06-16
---
import image from './assets/scaleway-silenced-alert.webp'
Expand All @@ -27,8 +27,8 @@ This page shows you how to temporarily mute (silence) alerts without disabling t


1. [Access](/cockpit/how-to/access-grafana-and-managed-dashboards/) your Grafana dashboard.
2. Click the **Toggle menu** icon next to **Home** in the top left corner of your screen.
3. Click **Alerting**, then **Silences**. Make sure that **Scaleway Alerting** is selected in the **Choose Alertmanager** drop-down.
2. Click the **Grafana** icon in the top left corner of your screen to open the menu.
3. Click the arrow next to **Alerting** then **Silences**. Make sure that **Scaleway Alerting** is selected in the **Choose Alertmanager** drop-down.
4. Click **Create silence**.
5. Click the drop-down in the **Silence start and end** section.
6. Click the **Calendar** icon and select a time range during which you want to silence alerts.
Expand Down
Loading