From bcecbb8efac58a531c97fd4b70541ef9f9d64f25 Mon Sep 17 00:00:00 2001
From: Simplychee <simplychee@gmail.com>
Date: Thu, 7 Nov 2024 14:10:53 +0200
Subject: [PATCH] k8s logs

---
 docs/user-guide/k8s-360/kubernetes-360-pre.md | 16 +++++++++++++++-
 1 file changed, 15 insertions(+), 1 deletion(-)

diff --git a/docs/user-guide/k8s-360/kubernetes-360-pre.md b/docs/user-guide/k8s-360/kubernetes-360-pre.md
index faeebd02..69a3d90d 100644
--- a/docs/user-guide/k8s-360/kubernetes-360-pre.md
+++ b/docs/user-guide/k8s-360/kubernetes-360-pre.md
@@ -21,7 +21,21 @@ Kubernetes 360 application provides an overview of your Kubernetes data, providi
 
 If you already have Kubernetes 360 data in your Logz.io account or prefer connecting Kubernetes [manually](https://app.logz.io/#/dashboard/integrations/collectors?tags=Tracing), you'll need an active **[Infrastructure Monitoring](https://app.logz.io/#/dashboard/metrics)** account, and ensure that your Kubernetes data is [connected to Logz.io](https://app.logz.io/#/dashboard/integrations/collectors?tags=Quick%20Setup).
 
-In addition, you'll need to ship your cluster metrics from the following sources:
+### Send Kubernetes logs
+
+To ensure your Kubernetes 360 dashboard is up and running, you'll need to ensure the following fields are properly propagated:
+
+| **Object** | **Field** |
+| -- | -- |
+| Pod | `kubernetes.pod_name` / `k8s_pod_name` |
+| namespace | `kubernetes.namespace_name` / `k8s_namespace_name` |
+| Nod | `k8s_nod_name` / `kubernetes.host` |
+| Cluster | `env_id` |
+
+
+### Send Kubernetes metrics
+
+Ship your cluster metrics from the following sources:
 
 * Node exporter (should be installed on every node).
 * CAdvisor.