diff --git a/faq/serverless-containers.mdx b/faq/serverless-containers.mdx
index a9eebbcc74..e912500221 100644
--- a/faq/serverless-containers.mdx
+++ b/faq/serverless-containers.mdx
@@ -126,7 +126,7 @@ Yes. Many traditional applications can be containerized and deployed to Serverle
Insufficient vCPU, RAM or ephemeral storage can lead to containers going to error status. Make sure to provision enough resources for your container.
-We recommend you set high values, [use metrics to monitor](/serverless/containers/how-to/monitor-container/) the resource usage of your container, then adjust the values accordingly.
+We recommend you set high values, [use metrics to monitor](/serverless-containers/how-to/monitor-container/) the resource usage of your container, then adjust the values accordingly.
### How can I reduce the cold-starts of Serverless Containers ?
@@ -141,7 +141,7 @@ Ensure that your code avoids heavy computations or long-running initialization a
### What are the limitations of Serverless Containers?
-Refer to our dedicated page about [Serverless Containers limitations and configuration restrictions](/serverless/containers/reference-content/containers-limitations/) for more information.
+Refer to our dedicated page about [Serverless Containers limitations and configuration restrictions](/serverless-containers/reference-content/containers-limitations/) for more information.
### Why does my container have an instance running after deployment, even with min-scale 0?
@@ -152,11 +152,11 @@ scale is set to 0. This behavior is not configurable at this time.
### How can I deploy my containers?
-There are several ways to deploy containers. Refer to the [dedicated documentation](/serverless/containers/reference-content/deploy-container/) to determine the best method for your use case.
+There are several ways to deploy containers. Refer to the [dedicated documentation](/serverless-containers/reference-content/deploy-container/) to determine the best method for your use case.
### How do I integrate my serverless solutions with other Scaleway services?
-Integration is straightforward. Serverless Functions and Containers can be triggered by events from [Queues](/serverless/messaging/concepts/#queues) and [Topics and Events](/serverless/messaging/concepts/#topics-and-events), and can easily communicate with services like [Managed Databases](/managed-databases/) or [Serverless databases](/serverless/sql-databases/). [Serverless Jobs](/serverless/jobs/) can pull data from [Object Storage](/storage/object), or output processed results into a database. With managed connectors, APIs, and built-in integrations, linking to the broader Scaleway ecosystem is seamless.
+Integration is straightforward. Serverless Functions and Containers can be triggered by events from [Queues](/messaging/concepts/#queues) and [Topics and Events](/messaging/concepts/#topics-and-events), and can easily communicate with services like [Managed Databases](/managed-databases-for-postgresql-and-mysql/) or [Serverless databases](/serverless-sql-databases/). [Serverless Jobs](/serverless-jobs/) can pull data from [Object Storage](/object-storage/), or output processed results into a database. With managed connectors, APIs, and built-in integrations, linking to the broader Scaleway ecosystem is seamless.
### Where should I host my container images for deployment ?
@@ -164,7 +164,7 @@ Integration is straightforward. Serverless Functions and Containers can be trigg
### How can I copy an image from an external registry to Scaleway Container Registry?
-You can copy an image from an external registry using the Docker CLI, or open source third-party tools such as [Skopeo](https://github.com/containers/skopeo). Refer to the [dedicated documentation](/serverless/containers/api-cli/migrate-external-image-to-scaleway-registry/) for more information.
+You can copy an image from an external registry using the Docker CLI, or open source third-party tools such as [Skopeo](https://github.com/containers/skopeo). Refer to the [dedicated documentation](/serverless-containers/api-cli/migrate-external-image-to-scaleway-registry/) for more information.
### How do Serverless Containers health checks work ?
@@ -201,26 +201,26 @@ solutions like Scaleway Object Storage.
### How can I store data in my Serverless resource?
-Serverless resources are by default [stateless](/serverless/containers/concepts/#stateless), local storage is ephemeral.
+Serverless resources are by default [stateless](/serverless-containers/concepts/#stateless), local storage is ephemeral.
For certain use cases, such as saving analysis results or exporting data, it can be important to have permanent storage to save data. Serverless resources can be connected to other resources from the Scaleway ecosystem for this purpose:
#### Databases
-* [Serverless Databases](/serverless/sql-databases/): Go full serverless and take the complexity out of PostgreSQL database operations.
-* [Managed MySQL / PostgreSQL](/managed-databases/postgresql-and-mysql/): Ensure scalability of your infrastructure and storage with our new generation of Managed Databases designed to scale on-demand according to your needs.
-* [Managed Database for Redis®](/managed-databases/redis/): Fully managed Redis®* in seconds.
-* [Managed MongoDB®](/managed-databases/mongodb/): Get the best of MongoDB® and Scaleway in one database.
+* [Serverless Databases](/serverless-sql-databases/): Go full serverless and take the complexity out of PostgreSQL database operations.
+* [Managed MySQL / PostgreSQL](/managed-databases-for-postgresql-and-mysql/): Ensure scalability of your infrastructure and storage with our new generation of Managed Databases designed to scale on-demand according to your needs.
+* [Managed Database for Redis®](/managed-databases-for-redis/): Fully managed Redis®* in seconds.
+* [Managed MongoDB®](/managed-mongodb-databases/): Get the best of MongoDB® and Scaleway in one database.
#### Storage
-* [Object Storage](/storage/object/): Multi-AZ resilient object storage service ensuring high availability for your data.
-* [Scaleway Glacier](/storage/object/): Our outstanding Cold Storage class to secure long-term object storage. Ideal for deep archived data.
+* [Object Storage](/object-storage/): Multi-AZ resilient object storage service ensuring high availability for your data.
+* [Scaleway Glacier](/object-storage/): Our outstanding Cold Storage class to secure long-term object storage. Ideal for deep archived data.
Explore all Scaleway products in the console and select the right product for your use case.
-Further integrations are also possible even if not listed above, for example, [Secret Manager](/identity-and-access-management/secret-manager/) can help you to store information that requires versioning.
+Further integrations are also possible even if not listed above, for example, [Secret Manager](/secret-manager/) can help you to store information that requires versioning.
### Can I use Serverless Containers with Edge Services?
diff --git a/faq/serverless-functions.mdx b/faq/serverless-functions.mdx
index 25fcbfbf83..1787251780 100644
--- a/faq/serverless-functions.mdx
+++ b/faq/serverless-functions.mdx
@@ -133,7 +133,7 @@ The scheme below illustrates our billing model:
Insufficient vCPU and RAM resources can lead to functions going to error status. Make sure to provision enough resources for your function.
-We recommend you set high values, [use metrics to monitor](/serverless/functions/how-to/monitor-function/) the resource usage of your function, then adjust the value accordingly.
+We recommend you set high values, [use metrics to monitor](/serverless-functions/how-to/monitor-function/) the resource usage of your function, then adjust the value accordingly.
### How does scaling work in these serverless services?
@@ -167,13 +167,13 @@ Ensure that your code avoids heavy computations or long-running initialization a
### What are the limitations of Serverless Functions?
-Refer to our dedicated page about [Serverless Functions limitations and configuration restrictions](/serverless/functions/reference-content/functions-limitations/) for more information.
+Refer to our dedicated page about [Serverless Functions limitations and configuration restrictions](/serverless-functions/reference-content/functions-limitations/) for more information.
### What runtimes are available on Serverless Functions?
Serverless Functions enables you to deploy functions using popular languages: `Go`, `Node`, `Python`, `PHP`, and `Rust`.
-Refer to our dedicated page about [Serverless Functions Runtimes Lifecycle](/serverless/functions/reference-content/functions-lifecycle/)
+Refer to our dedicated page about [Serverless Functions Runtimes Lifecycle](/serverless-functions/reference-content/functions-lifecycle/)
### Why does my function have an instance running after deployment, even with min-scale 0?
@@ -184,11 +184,11 @@ scale is set to `0`. This behavior is not configurable at this time.
### How can I deploy my functions?
-There are [several ways to deploy Serverless Functions](/serverless/functions/reference-content/deploy-function/), to accommodate a broad range of use cases.
+There are [several ways to deploy Serverless Functions](/serverless-functions/reference-content/deploy-function/), to accommodate a broad range of use cases.
### How do I integrate my serverless solutions with other Scaleway services?
-Integration is straightforward. Serverless Functions and Containers can be triggered by events from [Queues](/serverless/messaging/concepts/#queues) and [Topics and Events](/serverless/messaging/concepts/#topics-and-events), and can easily communicate with services like [Managed Databases](/managed-databases/) or [Serverless databases](/serverless/sql-databases/). [Serverless Jobs](/serverless/jobs/) can pull data from [Object Storage](/storage/object), or output processed results into a database. With managed connectors, APIs, and built-in integrations, linking to the broader Scaleway ecosystem is seamless.
+Integration is straightforward. Serverless Functions and Containers can be triggered by events from [Queues](/messaging/concepts/#queues) and [Topics and Events](/messaging/concepts/#topics-and-events), and can easily communicate with services like [Managed Databases](/managed-databases-for-postgresql-and-mysql/) or [Serverless databases](/serverless-sql-databases/). [Serverless Jobs](/serverless-jobs/) can pull data from [Object Storage](/object-storage/), or output processed results into a database. With managed connectors, APIs, and built-in integrations, linking to the broader Scaleway ecosystem is seamless.
### How can I check build errors?
@@ -201,7 +201,7 @@ In the `Serverless Functions Logs` dashboard, you will then be able to read info
### How can I test my functions locally?
- Scaleway provides libraries to run your functions locally, for debugging, profiling, and testing purposes. Refer to the [dedicated documentation](/serverless/functions/reference-content/local-testing/) for more information.
+ Scaleway provides libraries to run your functions locally, for debugging, profiling, and testing purposes. Refer to the [dedicated documentation](/serverless-functions/reference-content/local-testing/) for more information.
### Where can I find some advanced code examples for functions?
@@ -210,7 +210,7 @@ Check out our [serverless-examples repository](https://github.com/scaleway/serve
### How to migrate runtimes?
There are no constraints when changing a function runtime, you simply need to choose the runtime version you want.
-Upgrading a runtime is highly recommended in case of deprecation, and for runtimes that have reached end-of-support or end-of-life. See the [functions runtimes lifecycle documentation](/serverless/functions/reference-content/functions-lifecycle/) for more information.
+Upgrading a runtime is highly recommended in case of deprecation, and for runtimes that have reached end-of-support or end-of-life. See the [functions runtimes lifecycle documentation](/serverless-functions/reference-content/functions-lifecycle/) for more information.
## Network and storage
@@ -240,21 +240,21 @@ solutions like Scaleway Object Storage.
### How can I store data in my Serverless resource?
-Serverless resources are by default [stateless](/serverless/functions/concepts/#stateless), local storage is ephemeral.
+Serverless resources are by default [stateless](/serverless-functions/concepts/#stateless), local storage is ephemeral.
For some use cases, such as saving analysis results, exporting data etc., it can be important to save data. Serverless resources can be connected to other resources from the Scaleway ecosystem for this purpose:
#### Databases
-* [Serverless Databases](/serverless/sql-databases/): Go full serverless and take the complexity out of PostgreSQL database operations.
-* [Managed MySQL / PostgreSQL](/managed-databases/postgresql-and-mysql/): Ensure scalability of your infrastructure and storage with our new generation of Managed Databases designed to scale on-demand according to your needs.
-* [Managed Database for Redis®](/managed-databases/redis/): Fully managed Redis®* in seconds.
-* [Managed MongoDB®](/managed-databases/mongodb/): Get the best of MongoDB® and Scaleway in one database.
+* [Serverless Databases](/serverless-sql-databases/): Go full serverless and take the complexity out of PostgreSQL database operations.
+* [Managed MySQL / PostgreSQL](/managed-databases-for-postgresql-and-mysql/): Ensure scalability of your infrastructure and storage with our new generation of Managed Databases designed to scale on-demand according to your needs.
+* [Managed Database for Redis®](/managed-databases-for-redis/): Fully managed Redis®* in seconds.
+* [Managed MongoDB®](/managed-mongodb-databases/): Get the best of MongoDB® and Scaleway in one database.
#### Storage
-* [Object Storage](/storage/object/): Multi-AZ resilient object storage service ensuring high availability for your data.
-* [Scaleway Glacier](/storage/object/): Our outstanding Cold Storage class to secure long-term object storage. Ideal for deep archived data.
+* [Object Storage](/object-storage/): Multi-AZ resilient object storage service ensuring high availability for your data.
+* [Scaleway Glacier](/object-storage/): Our outstanding Cold Storage class to secure long-term object storage. Ideal for deep archived data.
Explore all Scaleway products in the console and select the right product for your use case.
diff --git a/faq/serverless-jobs.mdx b/faq/serverless-jobs.mdx
index d903f013cd..23f4c5b51b 100644
--- a/faq/serverless-jobs.mdx
+++ b/faq/serverless-jobs.mdx
@@ -94,7 +94,7 @@ Serverless Jobs are billed on a pay-as-you-go basis, strictly on resource consum
### How do I integrate my serverless solutions with other Scaleway services?
-Integration is straightforward. Serverless Functions and Containers can be triggered by events from [Queues](/serverless/messaging/concepts/#queues) and [Topics and Events](/serverless/messaging/concepts/#topics-and-events), and can easily communicate with services like [Managed Databases](/managed-databases/) or [Serverless databases](/serverless/sql-databases/). [Serverless Jobs](/serverless/jobs/) can pull data from [Object Storage](/storage/object), or output processed results into a database. With managed connectors, APIs, and built-in integrations, linking to the broader Scaleway ecosystem is seamless.
+Integration is straightforward. Serverless Functions and Containers can be triggered by events from [Queues](/messaging/concepts/#queues) and [Topics and Events](/messaging/concepts/#topics-and-events), and can easily communicate with services like [Managed Databases](/managed-databases-for-postgresql-and-mysql/) or [Serverless databases](/serverless-sql-databases/). [Serverless Jobs](/serverless-jobs/) can pull data from [Object Storage](/object-storage/), or output processed results into a database. With managed connectors, APIs, and built-in integrations, linking to the broader Scaleway ecosystem is seamless.
### Can I update Serverless Jobs resources (vCPU and RAM) at any time?
@@ -106,19 +106,19 @@ Ongoing job runs will keep using the resources defined when they started.
### How can I monitor the activity of my Serverless Jobs?
-Serverless Jobs are integrated with [Cockpit](/observability/cockpit/quickstart/), Scaleway's Observability service. Cockpit allows you to [see all the logs and metrics associated with your job runs](/serverless/jobs/concepts/#job-run). Additionally, each job run has a status that provides you with real-time information on your job's execution.
+Serverless Jobs are integrated with [Cockpit](/cockpit/quickstart/), Scaleway's Observability service. Cockpit allows you to [see all the logs and metrics associated with your job runs](/serverless-jobs/concepts/#job-run). Additionally, each job run has a status that provides you with real-time information on your job's execution.
### Can I cancel or modify a Serverless Job after it has started?
-An ongoing Serverless Job can be interrupted during its execution from the **Job runs** section of a job's **Overview** tab. Refer to the [dedicated documentation](/serverless/jobs/how-to/stop-job/) for more information.
+An ongoing Serverless Job can be interrupted during its execution from the **Job runs** section of a job's **Overview** tab. Refer to the [dedicated documentation](/serverless-jobs/how-to/stop-job/) for more information.
### How can I automate the deployment and management of Scaleway Serverless Jobs?
-Scaleway Serverless Jobs is part of the Scaleway ecosystem, it can therefore be driven using the [Scaleway CLI](/developer-tools/scaleway-cli/quickstart/), the [Scaleway API](https://www.scaleway.com/en/developers/api/), and other [developer tools](https://www.scaleway.com/en/developers/). Our serverless ecosystem offers a lot of possibilities with event-driven architectures, and integrations with more products of the Scaleway ecosystem are under active development.
+Scaleway Serverless Jobs is part of the Scaleway ecosystem, it can therefore be driven using the [Scaleway CLI](/scaleway-cli/quickstart/), the [Scaleway API](https://www.scaleway.com/en/developers/api/), and other [developer tools](https://www.scaleway.com/en/developers/). Our serverless ecosystem offers a lot of possibilities with event-driven architectures, and integrations with more products of the Scaleway ecosystem are under active development.
### Can I run multiple Serverless Jobs at the same time?
-When starting a job, you can use contextual options to define the number of jobs to execute at the same time. Refer to the [dedicated documentation](/serverless/jobs/how-to/run-job/#how-to-run-a-job-with-contextual-options) for more information.
+When starting a job, you can use contextual options to define the number of jobs to execute at the same time. Refer to the [dedicated documentation](/serverless-jobs/how-to/run-job/#how-to-run-a-job-with-contextual-options) for more information.
### Where should I host my jobs images for deployment?
@@ -126,7 +126,7 @@ When starting a job, you can use contextual options to define the number of jobs
### How can I copy an image from an external registry to Scaleway Container Registry?
-You can copy an image from an external registry by [logging in to the Scaleway Container Registry](/containers/container-registry/how-to/connect-docker-cli/) using the Docker CLI, and by copying the image as shown below:
+You can copy an image from an external registry by [logging in to the Scaleway Container Registry](/container-registry/how-to/connect-docker-cli/) using the Docker CLI, and by copying the image as shown below:
```sh
docker pull alpine:latest
@@ -143,7 +143,7 @@ skopeo copy --override-os linux docker://docker.io/alpine:latest docker://rg.fr-
### Can I securely use sensitive information with Serverless Jobs?
-Yes, you can use sensitive data such as API secret keys, passwords, TLS/SSL certificates, or tokens. Serverless Jobs seamlessly integrates with [Secret Manager](/identity-and-access-management/secret-manager/), which allows you to securely reference sensitive information within your jobs. Refer to the [dedicated documentation](/serverless/jobs/how-to/reference-secret-in-job/) for more information.
+Yes, you can use sensitive data such as API secret keys, passwords, TLS/SSL certificates, or tokens. Serverless Jobs seamlessly integrates with [Secret Manager](/secret-manager/), which allows you to securely reference sensitive information within your jobs. Refer to the [dedicated documentation](/serverless-jobs/how-to/reference-secret-in-job/) for more information.
## Network and storage
@@ -155,20 +155,20 @@ To add network restrictions on your resource, consult the [list of prefixes used
### How can I store data in my Serverless resource?
-Serverless resources are by default [stateless](/serverless/functions/concepts/#stateless), local storage is ephemeral.
+Serverless resources are by default [stateless](/serverless-functions/concepts/#stateless), local storage is ephemeral.
For some use cases, such as saving analysis results, exporting data etc., it can be important to save data. Serverless resources can be connected to other resources from the Scaleway ecosystem for this purpose:
#### Databases
-* [Serverless Databases](/serverless/sql-databases/): Go full serverless and take the complexity out of PostgreSQL database operations.
-* [Managed MySQL / PostgreSQL](/managed-databases/postgresql-and-mysql/): Ensure scalability of your infrastructure and storage with our new generation of Managed Databases designed to scale on-demand according to your needs.
-* [Managed MongoDB®](/managed-databases/mongodb/): Get the best of MongoDB® and Scaleway in one database.
+* [Serverless Databases](/serverless-sql-databases/): Go full serverless and take the complexity out of PostgreSQL database operations.
+* [Managed MySQL / PostgreSQL](/managed-databases-for-postgresql-and-mysql/): Ensure scalability of your infrastructure and storage with our new generation of Managed Databases designed to scale on-demand according to your needs.
+* [Managed MongoDB®](/managed-mongodb-databases/): Get the best of MongoDB® and Scaleway in one database.
#### Storage
-* [Object Storage](/storage/object/): Multi-AZ resilient object storage service ensuring high availability for your data.
-* [Scaleway Glacier](/storage/object/): Our outstanding Cold Storage class to secure long-term object storage. Ideal for deep archived data.
+* [Object Storage](/object-storage/): Multi-AZ resilient object storage service ensuring high availability for your data.
+* [Scaleway Glacier](/object-storage/): Our outstanding Cold Storage class to secure long-term object storage. Ideal for deep archived data.
Explore all Scaleway products in the console and select the right product for your use case.
diff --git a/menu/navigation.json b/menu/navigation.json
index 7eea0b5e9b..abde72a31a 100644
--- a/menu/navigation.json
+++ b/menu/navigation.json
@@ -2288,7 +2288,7 @@
}
],
"label": "PostgreSQL and MySQL",
- "slug": "postgresql-and-mysql"
+ "slug": "managed-databases-for-postgresql-and-mysql"
},
{
"items": [
diff --git a/pages/cockpit/how-to/assets/scaleway-cpt-k8s-terraform-logs.webp b/pages/cockpit/how-to/assets/scaleway-cpt-k8s-terraform-logs.webp
new file mode 100644
index 0000000000..d1020a4041
Binary files /dev/null and b/pages/cockpit/how-to/assets/scaleway-cpt-k8s-terraform-logs.webp differ
diff --git a/pages/cockpit/how-to/assets/scaleway-cpt-k8s-terraform-metrics.webp b/pages/cockpit/how-to/assets/scaleway-cpt-k8s-terraform-metrics.webp
new file mode 100644
index 0000000000..6a0d7c86f0
Binary files /dev/null and b/pages/cockpit/how-to/assets/scaleway-cpt-k8s-terraform-metrics.webp differ
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
new file mode 100644
index 0000000000..1e3c0907ac
--- /dev/null
+++ b/pages/cockpit/how-to/send-logs-from-k8s-to-cockpit.mdx
@@ -0,0 +1,148 @@
+---
+meta:
+ 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.
+content:
+ h1: How to send logs from your Kubernetes cluster to your Cockpit
+ paragraph: 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
+categories:
+ - observability
+dates:
+ validation: 2025-01-20
+ posted: 2025-01-20
+---
+
+In this page, we will show you how to send application logs from your Kubernetes cluster to your Cockpit using either a Helm chart or deploying a Helm chart with [Terraform](https://www.terraform.io/).
+
+We will use the [k8s-monitoring](https://artifacthub.io/packages/helm/grafana/k8s-monitoring/1.6.16) Helm Chart, which installs an Alloy Daemon set to export your Kubernetes cluster's logs to your Cockpit.
+
+
+
+ - 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-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
+
+
+ - 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.
+
+
+## Configure the Helm chart
+
+Create a `values.yml` file to configure your Helm chart, using the example below. Make sure that you replace `$SCW_CLUSTER_NAME` with the name of your Scaleway Kubernetes cluster, `COCKPIT_CUSTOM_LOGS_DATASOURCE_URL` with the URL of your custom logs data source (you can find it under the "API URL" section in the [Data sources tab](https://console.scaleway.com/cockpit/dataSource) of the Scaleway console), and `$COCKPIT_TOKEN` with your Cockpit token.
+
+```yaml
+cluster:
+ name: "$SCW_CLUSTER_NAME"
+global:
+ scrape_interval: 60s
+destinations:
+ - name: "my-cockpit-logs"
+ type: "loki"
+ protocol: "http"
+ logs:
+ enabled: true
+ url: "$COCKPIT_CUSTOM_LOGS_DATASOURCE_URL/loki/api/v1/push" ##You can find your logs URL in the **Data sources** tab of the Scaleway console under the "API URL" section of the relevant data source
+ tenantId: "$COCKPIT_TOKEN"
+
+ metrics:
+ enabled: false
+ traces:
+ enabled: false
+clusterEvents:
+ enabled: true
+ destinations: ["my-cockpit-logs"]
+# -- Node logs.
+nodeLogs:
+ enabled: true
+ destinations: ["my-cockpit-logs"]
+# -- Pod logs.
+podLogs:
+ enabled: true
+ destinations: ["my-cockpit-logs"]
+ volumeGatherSettings:
+ onlyGatherNewLogLines: true
+
+# An Alloy instance for collecting log data.
+alloy-logs:
+ enabled: true
+ logging:
+ level: info
+ format: logfmt
+alloy-singleton:
+ enabled: true
+```
+
+
+ The template above is for sending logs to your Cockpit. You can also configure it to send metrics to Cockpit using this Helm chart.
+ Refer to our dedicated documentation to [send metrics from your cluster to Cockpit](/cockpit/how-to/send-metrics-from-k8s-to-cockpit).
+
+
+## Send Kubernetes logs using Helm chart
+
+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:
+ ```
+ helm install -f /your-path/to/values.yml name-of-your-choice-for-your-log-ingester k8s-monitoring --version 1.6.16
+ ```
+ 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:
+
+ ```
+ helm list
+ ```
+
+## Send Kubernetes logs using Helm chart with Terraform
+
+You can also use Terraform to manage and deploy Helm charts, providing you with more automation and consistency to manage your Kubernetes resources.
+
+1. Create a `provider.tf` file and paste the following template to set up the Helm Terraform provider:
+ ```terraform
+ provider "helm" {
+ kubernetes {
+ host = your_k8s_cluster_host # The URL of your Kubernetes API server.
+ token = your_k8s_cluster_token # Authentication token to access the cluster.
+ cluster_ca_certificate = base64decode(
+ your_k8s_cluster_ca_certificate # The cluster's CA certificate.
+ )
+ }
+ }
+ ```
+2. Create a `maint.tf` file and paste the following template to create a Helm release resource. Make sure that you replace `/your-path/to/values.yml` with the actual path to your values file.
+ ```
+ resource "helm_release" "alloy" {
+ name = "name-of-your-log-ingester"
+ repository = "https://grafana.github.io/helm-charts"
+ chart = "k8s-monitoring"
+ version = "2.0.2"
+
+ namespace = "log-ingester"
+ create_namespace = true
+ values = [file("/your-path/to/values.yml")]
+ }
+ ```
+3. Save your changes.
+4. Run `terraform init` to initialize your Terraform configuration and download any necessary providers.
+5. Run `terraform apply` to apply your configuration.
+6. Type `yes` when prompted to confirm the actions.
+
+## Explore your logs in Cockpit
+
+1. Click **Cockpit** in the Observability section of the Scaleway [console](https://console.scaleway.com/) side menu. The **Cockpit Overview** page displays.
+2. Click **Open dashboards** to open your managed dashboards in Grafana. You are redirected to the Grafana website.
+3. Log in to Grafana using your [Grafana credentials](/cockpit/how-to/retrieve-grafana-credentials/).
+4. Click the **Home** icon, then click **Explore**.
+5. Select your custom data source in the search drop-down on the upper left corner of your screen.
+6. In the **Labels filter** drop-down, select the `cluster` label and in the **Value** drop-down, select your cluster.
+7. Optionally, click the **Clock** icon on the top right corner of your screen and filter by time range.
+8. Click **Run query** to see your logs. An output similar to the following should display.
+
+
\ No newline at end of file
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
new file mode 100644
index 0000000000..ffc6d1f220
--- /dev/null
+++ b/pages/cockpit/how-to/send-metrics-from-k8s-to-cockpit.mdx
@@ -0,0 +1,176 @@
+---
+meta:
+ 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.
+content:
+ h1: How to send metrics from your Kubernetes cluster to your Cockpit
+ paragraph: 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
+categories:
+ - observability
+dates:
+ validation: 2025-01-20
+ posted: 2025-01-20
+---
+
+
+In this page we will show you how to send application metrics from your Kubernetes cluster to your Cockpit, either by using a Helm chart or deploying a Helm chart with [Terraform](https://www.terraform.io/).
+
+We will use the [k8s-monitoring](https://artifacthub.io/packages/helm/grafana/k8s-monitoring/1.6.16) Helm Chart, which installs an Alloy Daemon set to export your Kubernetes cluster's metrics to your Cockpit.
+
+
+
+ - A Scaleway account metricsged 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 [metrics type](/cockpit/concepts/#data-types)
+ - [Created](/cockpit/how-to/create-token/) a Cockpit token in the same region as the metrics 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
+
+
+ - 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.
+
+
+
+## Configure the Helm chart
+
+Create a `values.yml` file to configure your Helm chart, using the example below. Make sure that you replace `$SCW_CLUSTER_NAME` with the name of your Scaleway Kubernetes cluster, `$COCKPIT_CUSTOM_METRICS_DATASOURCE_URL` with the URL of your custom metrics data source (you can find it under the "API URL" section in the [Data sources tab](https://console.scaleway.com/cockpit/dataSource) of the Scaleway console), and `$COCKPIT_TOKEN` with your Cockpit token.
+
+```yaml
+cluster:
+ name: "$SCW_CLUSTER_NAME"
+global:
+ scrape_interval: 60s
+destinations:
+ - name: "my-cockpit-metrics"
+ type: "prometheus"
+ protocol: "http"
+ metrics:
+ enabled: true
+ url: "$COCKPIT_CUSTOM_METRICS_DATASOURCE_URL/api/v1/push"
+ tenantId: "$COCKPIT_TOKEN"
+
+ logs:
+ enabled: false
+ traces:
+ enabled: false
+
+annotationAutodiscovery:
+ enabled: true
+ destinations: ["my-cockpit-metrics"]
+
+alloy-metrics:
+ enabled: true
+alloy-singleton:
+ enabled: true
+```
+
+
+ The template above is for sending metrics to your Cockpit. You can also configure it to send logs to Cockpit using this Helm chart.
+ Refer to our dedicated documentation to [send logs from your cluster to Cockpit](/cockpit/how-to/send-logs-from-k8s-to-cockpit)
+
+
+## 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.
+
+### Kubernetes deployment template
+
+```yaml
+apiVersion: apps/v1
+kind: Deployment
+metadata:
+ ...
+ annotations:
+ "k8s.grafana.com/metrics.portNumber" = "$METRICS_PORT"
+ "k8s.grafana.com/scrape" = "true"
+spec:
+ ...
+```
+
+### Terraform deployment template
+
+```terraform
+resource "kubernetes_deployment_v1" "your_application_deployment" {
+ ...
+ spec {
+ ...
+ template {
+ metadata {
+ ...
+ annotations = {
+ "k8s.grafana.com/metrics.portNumber" = "$METRICS_PORT"
+ "k8s.grafana.com/scrape" = "true"
+ }
+ }
+ ...
+ }
+ }
+}
+```
+
+## Send Kubernetes metrics using Helm chart with Terraform
+
+1. Create a `provider.tf` file and paste the following template to set up the Helm Terraform provider:
+ ```terraform
+ provider "helm" {
+ kubernetes {
+ host = your_k8s_cluster_host # The URL of your Kubernetes API server.
+ token = your_k8s_cluster_token # Authentication token to access the cluster.
+ cluster_ca_certificate = base64decode(
+ your_k8s_cluster_ca_certificate # The cluster's CA certificate.
+ )
+ }
+ }
+ ```
+2. Create a `maint.tf` file and paste the following template to create a Helm release resource. Make sure that you replace `/your-path/to/values.yml` with the actual path to your values file.
+ ```
+ resource "helm_release" "alloy" {
+ name = "name-of-your-metrics-ingester"
+ repository = "https://grafana.github.io/helm-charts"
+ chart = "k8s-monitoring"
+ version = "2.0.2"
+
+ namespace = "metrics-ingester"
+ create_namespace = true
+ values = [file("/your-path/to/values.yml")]
+ }
+ ```
+3. Save your changes.
+4. Run `terraform init` to initialize your Terraform configuration and download any necessary providers.
+5. Run `terraform apply` to apply your configuration.
+6. Type `yes` when prompted to confirm the actions.
+
+## Send Kubernetes metrics using Helm chart
+
+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:
+ ```
+ helm install -f /your-path/to/values.yml name-of-your-choice-for-your-metric-ingester k8s-monitoring --version 1.6.16
+ ```
+ 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.
+
+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.
+
+1. Click **Cockpit** in the Observability section of the Scaleway [console](https://console.scaleway.com/) side menu. The **Cockpit Overview** page displays.
+2. Click **Open dashboards** to open your managed dashboards in Grafana. You are redirected to the Grafana website.
+3. Log in to Grafana using your [Grafana credentials](/cockpit/how-to/retrieve-grafana-credentials/).
+4. Click the **Home** icon, then click **Explore**.
+5. Select your custom data source in the search drop-down on the upper left corner of your screen.
+6. In the **Labels filter** drop-down, select the `cluster` label and in the **Value** drop-down, select your cluster.
+7. Optionally, click the **Clock** icon on the top right corner of your screen and filter by time range.
+8. Click **Run query** to see your metrics. An output similar to the following should display.
+
\ No newline at end of file
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
index b662afa054..278a6d6abb 100644
--- a/pages/domains-and-dns/how-to/manage-nameservers-internal-domain.mdx
+++ b/pages/domains-and-dns/how-to/manage-nameservers-internal-domain.mdx
@@ -15,9 +15,9 @@ categories:
Scaleway Domains and DNS provides a managed DNS solution by providing default name servers for each domain name. If you want to use your own DNS servers, you can edit the name servers associated with your domain name.
-When adding name servers with Domains and DNS, you must ensure that they are [resolvable](/network/domains-and-dns/concepts/#domain-name-resolution) in the DNS. Each name server must have [A](/network/domains-and-dns/reference-content/understanding-dns-records/#a-record) and/or [AAAA](/network/domains-and-dns/reference-content/understanding-dns-records/#aaaa-record) records. These records link the name server's domain name (for example `ns0.mydomain.com`) to its corresponding IP address.
+When adding name servers with Domains and DNS, you must ensure that they are [resolvable](/domains-and-dns/concepts/#domain-name-resolution) in the DNS. Each name server must have [A](/domains-and-dns/reference-content/understanding-dns-records/#a-record) and/or [AAAA](/domains-and-dns/reference-content/understanding-dns-records/#aaaa-record) records. These records link the name server's domain name (for example `ns0.mydomain.com`) to its corresponding IP address.
-This is a critical step, especially when configuring [glue records](/network/domains-and-dns/concepts/#glue-record), which are necessary for resolving domain names in cases where the name servers are within the same domain.
+This is a critical step, especially when configuring [glue records](/domains-and-dns/concepts/#glue-record), which are necessary for resolving domain names in cases where the name servers are within the same domain.
For example, if you own `mydomain.com` and want to use `ns0.mydomain.com` and `ns1.mydomain.com` as your name servers, you must first create A/AAAA records for `ns0` and `ns1` in the `mydomain.com` DNS zone. This links `ns0.mydomain.com` and `ns1.mydomain.com` to their respective IP addresses, making them resolvable.
@@ -26,7 +26,7 @@ For example, if you own `mydomain.com` and want to use `ns0.mydomain.com` and `n
- 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
- A domain name registered with Scaleway Domains and DNS
-- Created an [A record](/network/domains-and-dns/reference-content/understanding-dns-records/#a-record) or an [AAAA record](/network/domains-and-dns/reference-content/understanding-dns-records/#aaaa-record) for the name servers you want to manage
+- Created an [A record](/domains-and-dns/reference-content/understanding-dns-records/#a-record) or an [AAAA record](/domains-and-dns/reference-content/understanding-dns-records/#aaaa-record) for the name servers you want to manage
1. Click **Domains and DNS** in the **Network** 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.
diff --git a/tutorials/web-deploy-windows-instance/index.mdx b/tutorials/web-deploy-windows-instance/index.mdx
index 52bbcd3c00..1f4b01dc76 100644
--- a/tutorials/web-deploy-windows-instance/index.mdx
+++ b/tutorials/web-deploy-windows-instance/index.mdx
@@ -27,18 +27,18 @@ Throughout this guide, you will learn how to:
- A Scaleway account logged into the [console](https://console.scaleway.com)
-- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization
-- An [Instance](/compute/instances/how-to/create-an-instance/) running Windows Server or Windows Server Core
+- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
+- An [Instance](/instances/how-to/create-an-instance/) running Windows Server or Windows Server Core
- The Windows Server Instance must have an [IPV4 address attached](/compute/instances/concepts/#dynamic-ip).
+ The Windows Server Instance must have an [IPV4 address attached](/instances/concepts/#dynamic-ip).
## Configuring Windows Server to accept Web Deploy
In Windows Server, IIS and its remote management components are not installed by default and need to be added as features. Web Deploy, a tool for deploying web applications, is distributed separately by Microsoft. Here is how to set up your Windows Server to accept Web Deploy:
-1. [Connect](/compute/instances/how-to/connect-to-instance/) to your Windows Server Instance and open a PowerShell prompt.
+1. [Connect](/instances/how-to/connect-to-instance/) to your Windows Server Instance and open a PowerShell prompt.
2. Install the necessary IIS features and management tools:
```powershell