Merge branch 'main' into serverless-containers-product-doc

Author: thomas-tacquet

blocks/mainLinks.json

@@ -18,6 +18,12 @@
       "package": "docs",
       "to": "/troubleshooting/"
     },
+    {
+      "icon": "billing",
+      "label": "Interactive Demos",
+      "package": "docs",
+      "to": "/demos/"
+    },
     {
       "icon": "documentation",
       "label": "FAQs",

changelog/june2025/2025-06-03-audit-trail-added-audit-trail-available-in-the-warsaw-r.mdx

@@ -0,0 +1,9 @@
+---
+title: Audit trail available in the Warsaw region
+status: added
+date: 2025-06-03
+category: monitoring
+product: audit-trail
+---
+
+Audit Trail is now available in the Warsaw region. Events can be consulted in both the Scaleway console and via the [Audit Trail API](https://www.scaleway.com/en/developers/api/audit-trail/#path-events-list-events). 

changelog/june2025/2025-06-03-generative-apis-changed-mistral-small-31-and-deepseek-r.mdx

@@ -0,0 +1,12 @@
+---
+title: Mistral Small 3.1 and Deepseek R1 Distilled Lama are now in General Availability
+status: changed
+date: 2025-06-03
+category: ai-data
+product: generative-apis
+---
+
+The [Mistral-small-3.1-24b-instruct-2503](/generative-apis/reference-content/supported-models/#multimodal-models-chat-and-vision) and [Deepseek-R1-Distill-Llama-70b](/generative-apis/reference-content/supported-models/#chat-models) models are now in General Availability.
+
+Their lifecycle will now follow the lifecycle for `Active` status models in our [model lifecycle policy](https://www.scaleway.com/en/docs/generative-apis/reference-content/model-lifecycle/).
+

changelog/june2025/2025-06-04-containers-added-commands-and-arguments-customizable.mdx

@@ -0,0 +1,10 @@
+---
+title: Customizable commands and arguments for Serverless Containers
+status: added
+date: 2025-06-04
+category: serverless
+product: containers
+---
+
+Serverless Containers now supports custom commands and arguments in container configurations. This gives you greater control over container startup behavior, enabling more flexible and customizable service deployments.
+

changelog/march2023/2023-03-02-cockpit-added-devtools-for-cockpit-!.mdx renamed to changelog/march2023/2023-03-02-cockpit-added-devtools-for-cockpit.mdx

@@ -1,5 +1,5 @@
 ---
-title: Devtools for Cockpit are now in production!
+title: Devtools for Cockpit are now in production
 status: added
 author:
     fullname: 'Join the #observability-beta channel on Slack'

changelog/may2025/2025-05-28-containers-fixed-serverless-containers-healthcheck.mdx

@@ -0,0 +1,10 @@
+---
+title: Serverless Containers healthcheck
+status: fixed
+date: 2025-05-28
+category: serverless
+product: containers
+---
+
+Fixed a bug with custom healthcheck where in specific conditions, Serverless Containers reported status was incorrect during a deployment.
+

changelog/november2024/2024-11-05-transactional-email-changed-webhook-event-update-to-ema.mdx

@@ -9,5 +9,5 @@ category: managed-services
 product: transactional-email
 ---
 
-The `email_error` field has been replaced by two new fields: `response_code` and `response_message`. This change allows for more precise error identification and improved tracking of response details. See the [documentation](/transactional-email/api-cli/webhook-events-payloads/) for full details.
+The `email_error` field has been replaced by two new fields: `response_code` and `response_message`. This change allows for more precise error identification and improved tracking of response details. See the [documentation](/transactional-email/reference-content/webhook-events-payloads) for full details.
 

macros/cockpit/no-data-grafana-dashboards.mdx

@@ -0,0 +1,22 @@
+---
+macro: troubleshooting-no-data-grafana-dashboards
+---
+
+## Problem
+
+I am experiencing one of the following issues:
+
+- I am missing data on my Grafana dashboards
+- A `No data` message displays
+- An error banner stating `Failed to upgrade legacy queries datasource was not found` displays
+- My Cockpit is unavailable.
+- I cannot view my logs and/or metrics in Grafana.
+- I cannot view my dashboards in Grafana.
+
+## Cause
+
+These issues often occur due to synchronization failures between Cockpit and Grafana, preventing dashboards from displaying the latest logs and metrics as expected.
+
+## Solution
+
+Refer to the [dedicated troubleshooting documentation](/cockpit/troubleshooting/synchronize-grafana-data-sources/) on how to synchronize Grafana sources.

macros/network/lb-create-backend-2-traffic-mgnt.mdx

@@ -11,7 +11,7 @@ Traffic management configuration lets you define how your Load Balancer's backen
         * **Least connections**: Requests are forwarded to the backend server with the fewest current connections. 
         * **First available**: Requests are forwarded to the first backend server with available connection slots.
 
-2. Add the **Server IP addresses** of the servers the Load Balancer will forward requests/connections to. These will be your backend servers. 
+2. Add the **Server IP addresses** of the servers the Load Balancer will forward requests/connections to. These will be your backend servers. They must be Scaleway resources (Instances, Elastic Metal or Dedibox servers) unless you have a [Multi-Cloud](/load-balancer/faq/#what-is-the-difference-between-multi-cloud-and-non-multi-cloud-offers) Load Balancer, in which case this restriction does not apply. Scaleway backend servers can be in any AZ, and are not restricted to the same AZ as the Load Balancer.
 
         <Message type="note">
         If you want your Load Balancer to communicate with its backend servers over an attached [Private Network](/vpc/concepts/#private-networks), ensure that you enter the servers' private IP addresses. This is necessary in the case of a [private Load Balancer](/load-balancer/reference-content/public-private-accessibility/#private-load-balancers), but may also be desired for public Load Balancers attached to Private Networks where backend servers are in the same VPC. As Load Balancers are compatible with [VPC routing](/vpc/reference-content/understanding-routing/), they will be able to direct requests to any backend server within the same VPC, via its private IP address. The Load Balancer and backend server do not have to be on the same Private Network in that VPC.

macros/tem/webhook-event-status.mdx

@@ -0,0 +1,16 @@
+---
+macro: webhook-event-status
+---
+
+The Webhook event status indicates the status of the webhook delivery.
+
+These are the different event statuses:
+
+- `unknown_status`: The status of the event is unknown by default. This status is used when the event status has not been specified.
+- `sending`: The webhook event is being sent. This means that the notification is in transit to the configured URL.
+- `sent`: The webhook event was successfully sent. This status indicates that the configured URL received the notification.
+- `failed`: The webhook event could not be sent after multiple attempts. This status means there were repeated errors during the attempt to send the notification.
+
+<Message type="note">
+  Refer to the [Transactional Email API documentation](https://www.scaleway.com/en/developers/api/transactional-email/) for more information about event statuses.
+</Message>