docs(review): weekly review (#5359)

nerda-codes · SamyOubouaziz · commit ad923ff3ab20 · 2025-08-05T17:03:09.000+02:00
diff --git a/pages/cockpit/concepts.mdx b/pages/cockpit/concepts.mdx
@@ -86,7 +86,7 @@ An endpoint is the point of entry in a communication channel when two systems ar
 
 <Message type="important">
  - Having the default configuration on your agents might lead to more of your resources' metrics being sent, a high consumption and a high bill at the end of the month.
- - Sending metrics, logs and traces for Scaleway resources or personal data using an external path is a billable feature. In addition, any data that you push yourself is billed, even if you send data from Scaleway products. Refer to the [product pricing](https://www.scaleway.com/en/pricing/?tags=available,managedservices-observability-cockpit) for more information.
+ - Sending metrics, logs and traces for Scaleway resources or personal data using an external path is a billable feature. In addition, any data that you push yourself is billed, even if you send data from Scaleway products. Refer to the [product pricing](https://www.scaleway.com/en/pricing/managed-services/#cockpit) for more information.
 </Message>
 
 ## Grafana users
diff --git a/pages/cockpit/faq.mdx b/pages/cockpit/faq.mdx
@@ -127,6 +127,6 @@ configure the Grafana Alloy agent, push your data, and visualize it in Grafana.
 Find out which Scaleway products are integrated into Cockpit in our [capabilities and limits documentation page](/cockpit/reference-content/cockpit-limitations/#product-integration-into-cockpit).
 
 <Message type="important">
-Sending metrics and logs using an external path is a billable feature. Any data that you push yourself is considered as "custom" and is billed, even if you collect that data from Scaleway products. Refer to the [product pricing](https://www.scaleway.com/en/pricing/?tags=available,managedservices-observability-cockpit) for more information.
+Sending metrics and logs using an external path is a billable feature. Any data that you push yourself is considered as "custom" and is billed, even if you collect that data from Scaleway products. Refer to the [product pricing](https://www.scaleway.com/en/pricing/managed-services/#cockpit) for more information.
 </Message>
 
diff --git a/pages/cockpit/how-to/create-token.mdx b/pages/cockpit/how-to/create-token.mdx
@@ -38,5 +38,5 @@ This page shows you how to create [tokens](/cockpit/concepts/#cockpit-tokens), t
 
 <Message type="important">
  - Having the default configuration on your agents might lead to more of your resources' metrics being sent, a high consumption, and a high bill at the end of the month.
- - Sending metrics and logs for Scaleway resources or personal data using an external path is a billable feature. In addition, any data that you push yourself is billed, even if you send data from Scaleway products. Refer to the [product pricing page](https://www.scaleway.com/en/pricing/?tags=available,managedservices-observability-cockpit) for more information.
+ - Sending metrics and logs for Scaleway resources or personal data using an external path is a billable feature. In addition, any data that you push yourself is billed, even if you send data from Scaleway products. Refer to the [product pricing page](https://www.scaleway.com/en/pricing/managed-services/#cockpit) for more information.
 </Message>
diff --git a/pages/cockpit/how-to/send-logs-from-k8s-to-cockpit.mdx b/pages/cockpit/how-to/send-logs-from-k8s-to-cockpit.mdx
@@ -3,7 +3,7 @@ title: How to send logs from your Kubernetes cluster to your Cockpit
 description: Learn how to send your pod logs to your Cockpit using Scaleway's comprehensive guide. This tutorial covers sending Kubernetes pods logs to Scaleway's Cockpit for centralized monitoring and analysis using Grafana, ensuring efficient monitoring and log analysis in your infrastructure.
 tags: kubernetes cockpit logs observability monitoring cluster
 dates:
-  validation: 2025-01-20
+  validation: 2025-07-31
   posted: 2025-01-20
 ---
 import Requirements from '@macros/iam/requirements.mdx'
@@ -19,13 +19,13 @@ We will use the [k8s-monitoring](https://artifacthub.io/packages/helm/grafana/k8
 
  - A Scaleway account logged into the [console](https://console.scaleway.com)
  - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
- - [Created](/cockpit/how-to/create-external-data-sources/) a custom external data source of the [logs type](/cockpit/concepts/#data-types)
+ - [Created](/cockpit/how-to/create-external-data-sources/) a [custom data source](/cockpit/concepts/#custom-data) of the [logs type](/cockpit/concepts/#data-types)
  - [Created](/cockpit/how-to/create-token/) a Cockpit token in the same region as the logs data source
  - A running Kubernetes cluster containing your deployed application
  - [Created](/iam/how-to/create-api-keys/) an API key and retrieved your API secret key
 
 <Message type="important">
-  - Sending logs for Scaleway resources or personal data using an external path is a billable feature. In addition, any data that you push yourself is billed, even if you send data from Scaleway products. Refer to the [product pricing](https://www.scaleway.com/en/pricing/?tags=available,managedservices-observability-cockpit) page for more information.
+  - Sending logs for Scaleway resources or personal data using an external path is a billable feature. In addition, any data that you push yourself is billed, even if you send data from Scaleway products. Refer to the [product pricing](https://www.scaleway.com/en/pricing/managed-services/#cockpit) page for more information.
 </Message>
 
 ## Configure the Helm chart
@@ -84,17 +84,18 @@ alloy-singleton:
 Once you have configured your `values.yml` file, you can use Helm to deploy the log-forwarding configuration to your Kubernetes cluster. Before installing the Helm chart, ensure that your `kubectl` tool is properly connected to your Kubernetes cluster. `kubectl` is the command-line tool for interacting with Kubernetes clusters.
 
 1. [Connect](/kubernetes/how-to/connect-cluster-kubectl/) `kubectl` to your Kubernetes cluster
-2. Run the command below to install the `k8s-monitoring` Helm chart:
+2. Run the commands below to install the `k8s-monitoring` Helm chart. Make sure that you replace `/your-path/to/values.yml` with the correct path where your `values.yml` file is stored. Make sure that you also replace `name-of-your-choice-for-your-log-ingester` with a clear name (ex. `alloy-logs-ingester`).
     ```
     helm repo add grafana https://grafana.github.io/helm-charts
     helm repo update
     helm install -f /your-path/to/values.yml name-of-your-choice-for-your-log-ingester grafana/k8s-monitoring --version 2.0.21
     ```
-      The `-f` flag specifies the path to your `values.yml` file, which contains the configuration for the Helm chart. Make sure that you replace `/your-path/to/values.yml` with the correct path where your `values.yml` file is stored. Make sure that you also replace `name-of-your-choice-for-your-log-ingester` with a clear name (ex. `alloy-logs-ingester`). In our configuration, we are using `alloy-lm-ingester`.
-      Helm installs the `k8s-monitoring` chart, which includes the Alloy DaemonSet configured to collect logs from your Kubernetes cluster.
-      The DaemonSet ensures that a pod is running on each node in your cluster, which collects logs and forwards them to the specified Loki endpoint in your Cockpit.
-
-3. Optionally, check the status of the release to ensure it was installed:
+      <Message type="iam">
+        The `-f` flag specifies the path to your `values.yml` file, which contains the configuration for the Helm chart. <br /><br />
+        Helm installs the `k8s-monitoring` chart, which includes the Alloy DaemonSet configured to collect logs from your Kubernetes cluster. <br /><br />
+        The DaemonSet ensures that a pod is running on each node in your cluster, which collects logs and forwards them to the specified Loki endpoint in your Cockpit.
+      </Message>
+3. Optionally, run the following command to check the status of the release and ensure it was installed:
 
       ```
       helm list
diff --git a/pages/cockpit/how-to/send-metrics-from-k8s-to-cockpit.mdx b/pages/cockpit/how-to/send-metrics-from-k8s-to-cockpit.mdx
@@ -3,7 +3,7 @@ title: How to send metrics from your Kubernetes cluster to your Cockpit
 description: Learn how to send your pod metrics to your Cockpit using Scaleway's comprehensive guide. This tutorial covers sending Kubernetes pods metrics to Scaleway's Cockpit for centralized monitoring and analysis using Grafana, ensuring efficient monitoring and metrics analysis in your infrastructure.
 tags: kubernetes cockpit metrics observability monitoring cluster
 dates:
-  validation: 2025-01-20
+  validation: 2025-07-31
   posted: 2025-01-20
 ---
 import Requirements from '@macros/iam/requirements.mdx'
@@ -26,7 +26,7 @@ We will use the [k8s-monitoring](https://artifacthub.io/packages/helm/grafana/k8
  - [Created](/iam/how-to/create-api-keys/) an API key and retrieved your API secret key
 
 <Message type="important">
-  - Sending metrics for Scaleway resources or personal data using an external path is a billable feature. In addition, any data that you push yourself is billed, even if you send data from Scaleway products. Refer to the [product pricing](https://www.scaleway.com/en/pricing/?tags=available,managedservices-observability-cockpit) page for more information.
+  - Sending metrics for Scaleway resources or personal data using an external path is a billable feature. In addition, any data that you push yourself is billed, even if you send data from Scaleway products. Refer to the [product pricing](https://www.scaleway.com/en/pricing/managed-services/#cockpit) page for more information.
 </Message>
 
 
@@ -70,7 +70,7 @@ alloy-singleton:
 
 ## Add annotations for auto-discovery
 
-Annotations in Kubernetes provide a way to attach metadata to your resources. For `k8s-monitoring`, these annotations signal which pods should be scraped for metrics, and what port to use. For the sake of this documentation, we are adding annotations to specify we want `k8s-monitoring` to scrape the pods from our deployment. Make sure that you replace `$METRICS_PORT` with the port where your application exposes Prometheus metrics.
+Annotations in Kubernetes provide a way to attach metadata to your resources. For `k8s-monitoring`, these annotations signal which pods should be scraped for metrics, and what port to use. In this documentation we are adding annotations to specify we want `k8s-monitoring` to scrape the pods from our deployment. Make sure that you replace `$METRICS_PORT` with the port where your application exposes Prometheus metrics.
 
 ### Kubernetes deployment template
 
@@ -144,23 +144,23 @@ resource "kubernetes_deployment_v1" "your_application_deployment" {
 Once you have configured your `values.yml` file, you can use Helm to deploy the metric-forwarding configuration to your Kubernetes cluster. Before installing the Helm chart, ensure that your `kubectl` tool is properly connected to your Kubernetes cluster. `kubectl` is the command-line tool for interacting with Kubernetes clusters.
 
 1. [Connect](/kubernetes/how-to/connect-cluster-kubectl/) `kubectl` to your Kubernetes cluster
-2. Run the command below to install the `k8s-monitoring` Helm chart:
+2. Run the command below to install the `k8s-monitoring` Helm chart. Make sure that you replace `/your-path/to/values.yml` with the correct path where your `values.yml` file is stored. Make sure that you also replace `name-of-your-choice-for-your-metric-ingester` with a clear name (ex. `alloy-metrics-ingester`).
     ```
     helm repo add grafana https://grafana.github.io/helm-charts
     helm repo update
     helm install -f /your-path/to/values.yml name-of-your-choice-for-your-metric-ingester grafana/k8s-monitoring --version 2.0.21
     ```
-      The `-f` flag specifies the path to your `values.yml` file, which contains the configuration for the Helm chart. Make sure that you replace `/your-path/to/values.yml` with the correct path where your `values.yml` file is stored. Make sure that you also replace `name-of-your-choice-for-your-metric-ingester` with a clear name (ex. `alloy-metrics-ingester`). In our configuration, we are using `alloy-lm-ingester`.
-      Helm installs the `k8s-monitoring` chart, which includes the Alloy DaemonSet configured to collect metrics from your Kubernetes cluster.
-      The DaemonSet ensures that a pod is running on each node in your cluster, which collects metrics and forwards them to the specified Prometheus endpoint in your Cockpit.
-
+      <Message type="iam">
+       The `-f` flag specifies the path to your `values.yml` file, which contains the configuration for the Helm chart. <br /><br />
+       Helm installs the `k8s-monitoring` chart, which includes the Alloy DaemonSet configured to collect metrics from your Kubernetes cluster. <br /><br />
+       The DaemonSet ensures that a pod is running on each node in your cluster, which collects metrics and forwards them to the specified Prometheus endpoint in your Cockpit.
+      </Message>
 3. Optionally, check the status of the release to ensure it was installed:
 
     ```
     helm list
     ```
 
-
 ## Explore your metrics in Cockpit
 
 Now that your metrics are exported to your Cockpit, you can access and query them.
diff --git a/pages/cockpit/how-to/send-metrics-logs-to-cockpit.mdx b/pages/cockpit/how-to/send-metrics-logs-to-cockpit.mdx
@@ -25,7 +25,7 @@ You can push logs with any Loki compatible agent such as the [Promtail](https://
 
 <Message type="important">
  - Having the default configuration on your agents might lead to more of your resources' metrics being sent, a high consumption, and a high bill at the end of the month.
- - Sending metrics and logs for Scaleway resources or personal data using an external path is a billable feature. In addition, any data that you push yourself is billed, even if you send data from Scaleway products. Refer to the [product pricing](https://www.scaleway.com/en/pricing/?tags=available,managedservices-observability-cockpit) for more information.
+ - Sending metrics and logs for Scaleway resources or personal data using an external path is a billable feature. In addition, any data that you push yourself is billed, even if you send data from Scaleway products. Refer to the [product pricing](https://www.scaleway.com/en/pricing/managed-services/#cockpit) for more information.
 </Message>
 
 ## Send metrics and logs to your Cockpit
diff --git a/pages/cockpit/how-to/send-metrics-with-grafana-alloy.mdx b/pages/cockpit/how-to/send-metrics-with-grafana-alloy.mdx
@@ -31,7 +31,7 @@ For the sake of this documentation, we are using Grafana Alloy on macOS. Refer t
 <Message type="important">
  - Having the default configuration on your agents might lead to more of your resources' metrics being sent, a high consumption and a high bill at the end of the month.
 
- - Sending metrics and logs for Scaleway resources or personal data using an external path is a billable feature. In addition, any data that you push yourself is billed, even if you send data from Scaleway products. Refer to the [product pricing](https://www.scaleway.com/en/pricing/?tags=available,managedservices-observability-cockpit) for more information.
+ - Sending metrics and logs for Scaleway resources or personal data using an external path is a billable feature. In addition, any data that you push yourself is billed, even if you send data from Scaleway products. Refer to the [product pricing](https://www.scaleway.com/en/pricing/managed-services/#cockpit) for more information.
 </Message>
 
 ## Configuring Grafana Alloy
diff --git a/pages/cockpit/quickstart.mdx b/pages/cockpit/quickstart.mdx
@@ -24,7 +24,7 @@ In this documentation, we show you how to retrieve your Grafana credentials to a
 
 <Message type="important">
  - Having the default configuration on your agents might lead to more of your resources' metrics being sent, a high consumption, and a high bill at the end of the month.
- - Sending metrics and logs for Scaleway resources or personal data using an external path is a billable feature. In addition, any data that you push yourself is billed, even if you send data from Scaleway products. Refer to the [product pricing](https://www.scaleway.com/en/pricing/?tags=available,managedservices-observability-cockpit) for more information.
+ - Sending metrics and logs for Scaleway resources or personal data using an external path is a billable feature. In addition, any data that you push yourself is billed, even if you send data from Scaleway products. Refer to the [product pricing](https://www.scaleway.com/en/pricing/managed-services/#cockpit) for more information.
 </Message>
 
 ## How to retrieve your Grafana credentials
@@ -57,8 +57,8 @@ In this documentation, we show you how to retrieve your Grafana credentials to a
     </Message>
 7. Click **Create token** to confirm. A pop-up displays with your secret key. Make sure that you save the secret key before closing the pop-up.
 
-<Message type="">
-**Going further** <br /><br />
+<Message type="iam">
+ **Going further** <br /><br />
 
   If you have not set up an agent yet, check out our [documentation](/cockpit/how-to/send-metrics-with-grafana-alloy/) to find out how to configure Grafana Alloy, push your metrics, and visualize them in Grafana.
   You must have created resources to monitor to push your data to Cockpit.
diff --git a/pages/cockpit/reference-content/cockpit-limitations.mdx b/pages/cockpit/reference-content/cockpit-limitations.mdx
@@ -62,7 +62,7 @@ The following table provides information about [Mimir](/cockpit/concepts/#mimir)
 
 The following table provides details about the products that are integrated into Cockpit. This means that you can have metrics and/or logs and/or alerts in your Cockpit for the products mentioned below.
 
-**Sending metrics and logs using an external path is a billable feature**. As such, any additional data that you may push yourself will be billed, even if you send data from Scaleway products that are **integrated into Cockpit**. Refer to the [product pricing](https://www.scaleway.com/en/pricing/?tags=available,managedservices-observability-cockpit) for more information.
+**Sending metrics and logs using an external path is a billable feature**. As such, any additional data that you may push yourself will be billed, even if you send data from Scaleway products that are **integrated into Cockpit**. Refer to the [product pricing](https://www.scaleway.com/en/pricing/managed-services/#cockpit) for more information.
 
 | **Product Name**           | **Metrics**     | **Logs**        | **Alerts**      |
 |----------------------------|-----------------|-----------------|-----------------|
diff --git a/pages/domains-and-dns/how-to/manage-nameservers-internal-domain.mdx b/pages/domains-and-dns/how-to/manage-nameservers-internal-domain.mdx
@@ -3,7 +3,7 @@ title: How to manage name servers for an internal domain
 description: Learn how to effectively manage name servers for your internal domains. This guide covers editing name server information, adding and removing name servers, and validating configurations through the intuitive Domains and DNS dashboard.
 tags: nameserver internal-domain domain dns
 dates:
-  validation: 2025-01-21
+  validation: 2025-07-31
   posted: 2022-10-31
 ---
 import Requirements from '@macros/iam/requirements.mdx'
@@ -26,20 +26,20 @@ For example, if you own `mydomain.com` and want to use `ns0.mydomain.com` and `n
 
 1. Click **Domains and DNS** in the **Domains & Web Hosting** section of the [Scaleway console](https://console.scaleway.com) side menu. The Domains and DNS dashboard displays.
 2. Click the domain name you want to configure. The **Overview** tab for your domain displays.
-3. Click **Edit** in the **Name servers** section.
+3. Scroll to the **Name servers** section and click **Edit**.
 4. Edit the name server information. For each name server, you can provide:
     * A name server
     * An IPv6 address
     * An IPv4 address
     <Message type="tip">
-      IP addresses are only required if you want to create **glue records**. A glue record provides the IP address of a name server so that DNS can resolve the domain name if the domain uses name servers hosted under that same domain name.
+      IP addresses are only required if you want to create **glue records**. A glue record provides the IP address of a name server to allow the DNS to resolve the domain if it uses name servers hosted under that same domain.
     </Message>
 5. Optionally, click **Add name server** to add more name servers and enter your server's information.
     <Message type="tip">
-      We recommend you configure a minimum of two and a maximum of seven DNS servers for each domain name.
+      We recommend you configure a minimum of two and a maximum of seven DNS servers for each domain.
     </Message>
 6. Click the <Icon name="delete" /> icon to delete a name server.
 7. Click the <Icon name="validate" /> icon to validate your configuration.
-8. Click the <Icon name="cancel" /> icon to cancel all the changes you have made.
+8. Click the <Icon name="cancel" /> icon to cancel all changes.
 
 
diff --git a/pages/elastic-metal/how-to/send-metrics-logs-to-cockpit.mdx b/pages/elastic-metal/how-to/send-metrics-logs-to-cockpit.mdx
diff --git a/pages/transactional-email/how-to/manage-blocklists.mdx b/pages/transactional-email/how-to/manage-blocklists.mdx
diff --git a/pages/transactional-email/how-to/manage-email-activity.mdx b/pages/transactional-email/how-to/manage-email-activity.mdx
diff --git a/tutorials/pushing-metrics-logs-from-scw-instance/index.mdx b/tutorials/pushing-metrics-logs-from-scw-instance/index.mdx
