docs(cockpit): neda review

Co-authored-by: Jessica <[email protected]>

Author: nerda-codes

observability/cockpit/how-to/send-log-from-k8s-to-cockpit.mdx

@@ -9,39 +9,30 @@ tags: kubernetes cockpit logs observability monitoring cluster
 categories:
   - observability
 dates:
-  validation: TBD
-  posted: TBD
+  validation: 2025/01/03
+  posted: 2025/01/03
 ---
 
-This page shows you how to send your application logs created in a Kubernetes cluster to your Cockpit either by using a Helm Chart or by deploying this Helm chart with Terraform.
+This page shows you how to send application logs created in a Kubernetes cluster to your Cockpit either by using a Helm chart or by deploying a Helm chart with [Terraform](https://www.terraform.io/).
 
-In this example, we use [k8s-monitoring](https://artifacthub.io/packages/helm/grafana/k8s-monitoring/1.6.16) which install an Alloy Daemon set to your Kubernetes Cluster to export logs to your Cockpit.
+In this example, we use [k8s-monitoring](https://artifacthub.io/packages/helm/grafana/k8s-monitoring/1.6.16) which installs an Alloy Daemon set to your Kubernetes cluster to export logs to your Cockpit.
 
 <Macro id="requirements" />
 
  - 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
- - [Created](/observability/cockpit/how-to/create-external-data-sources/) an custom external data source
- - [Created](/observability/cockpit/how-to/create-token/) a Cockpit Token for the same region as the data source
- - A running Kubernetes Cluster containing your application deployed
- - For Terraform : [Created](/identity-and-access-management/iam/how-to/create-api-keys/) an API key and retrieved your API secret key
-
-
+ - [Created](/observability/cockpit/how-to/create-external-data-sources/) a custom external data source
+ - [Created](/observability/cockpit/how-to/create-token/) a Cockpit token for the same region as the data source
+ - A running Kubernetes cluster containing your application deployed
+ - [Created](/identity-and-access-management/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) for more information.
 <Message/>
 
 ## Configure the Helm chart
 
-Create a `values.yml` file to configure your Helm chart, here is an example: 
-
-<Message type="Note">
-  Do not forget to replace: 
-  - `$SCW_CLUSTER_NAME` by the name of your Scaleway Cluster
-  - `$COCKPIT_CUSTOM_DATASOURCE_HOST` by the hostname of your custom endpoint (do not include the `/loki/api/v1/push` )
-  - `$COCKPIT_TOKEN` by your Cockpit Token
-<Message/>
+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_DATASOURCE_HOST` with the hostname of your custom endpoint (excluding the `/loki/api/v1/push` part), and `$COCKPIT_TOKEN` with your Cockpit token.
 
 ```yaml
 cluster:
@@ -95,21 +86,21 @@ alloy-logs:
 ```
 
 <Message type="info">
-- Note that this is only an example to send logs to your cockpit, you can also send metrics to cockpit using this Helm chart
+The template above is only an example to send logs to your Cockpit. You can also send metrics to Cockpit using this Helm chart.
 </Message>
 
 ## Send Kubernetes logs to your Cockpit using Helm chart
 
-1. Connect your kubectl to your Scaleway Cluster
-2. Apply your Helm chart with the `values.yml` file by running
+1. Connect your kubectl to your Kubernetes cluster
+2. Run the following command to apply your Helm chart with the `values.yml` file:
   ```
   helm install -f /your-path/to/values.yml my-log-ingester k8s-monitoring --version 1.6.16
   ```
-  Do not forget to change the -f flag with the correct path to your `values.yml` file
+  Make sure to replace `-f` flag with the correct path to your `values.yml` file.
 
 ## Send Kubernetes logs to your Cockpit using Helm chart with Terraform
 
-1. Set up the Helm Terraform provider
+1. Set up the Helm Terraform provider:
   ```terraform
   provider "helm" {
     kubernetes {
@@ -121,7 +112,7 @@ alloy-logs:
     }
   }
   ```
-2. Create a Helm release ressource with the path to your `values.yml`
+2. Create a Helm release resource with the path to your `values.yml`:
   ```
   resource "helm_release" "log-ingester" {
     name = "my-log-ingester"
@@ -134,12 +125,13 @@ alloy-logs:
     values = [file("/your-path/to/values.yml")]
   }
   ```
-3. Apply the new terraform configuration with `terraform apply`
+3. Run `terraform apply` to apply the new Terraform configuration.
 
-## Explore your logs 
+## Explore your logs in Grafana
 
 Now that your logs are exported to your Cockpit, you can access and query them.
 
-1. Open your Cockpit Dashboard
-2. Click the **Home** icon > **Explore**. Select your custom data source in the upper left corner.
-3. Filter the query by only searching for the label `cluster` with the value corresponding to your cluster name and your log should display
+1. Click **Cockpit** in the Observability section of the [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. Click the **Home** icon > **Explore**. Select your custom data source in the upper left corner.
+4. Filter the query by only searching for the label `cluster` with the value corresponding to your cluster name and your logs should display.