From e119403ebc8f140444028ac41fde8e366075ffce Mon Sep 17 00:00:00 2001
From: Simplychee <simplychee@gmail.com>
Date: Thu, 2 Nov 2023 11:02:00 +0200
Subject: [PATCH] Adding deployment (#2488)

* deploy

* typo

* button

* k360

* go to commit

* break?

* no break

* updates

* name

* url

* we need to switch
---
 .../distributed-tracing/services.md           | 18 +++++++++++++++
 _source/user-guide/k360/index.md              | 23 +++++++++++++++++++
 2 files changed, 41 insertions(+)

diff --git a/_source/user-guide/distributed-tracing/services.md b/_source/user-guide/distributed-tracing/services.md
index fb919bf7e..62934a54b 100644
--- a/_source/user-guide/distributed-tracing/services.md
+++ b/_source/user-guide/distributed-tracing/services.md
@@ -71,6 +71,24 @@ Hovering over the graphs provides values for the specific time point, allowing y
 
 You can toggle your view between pods and nodes inside the service.
 
+## Track Deployment Data
+
+You can enrich your Service Overview graphs by adding an indication of recent deployments, helping you determine if a deployment has increased response times for end-users, altered your application's memory/CPU footprint, or introduced any other performance-related changes.
+
+To enable deployment tracking ability, run the [**Telemetry Collector**](https://app.logz.io/#/dashboard/send-your-data/agent/new) on your Kubernetes clusters. You can also activate this process **manually** by installing [Logz.io Kubernetes events Helm chart](https://app.logz.io/#/dashboard/integrations/Kubernetes:~:text=user%20guide.-,Send%20your%20deploy%20events%20logs,-This%20integration%20sends) and sending Kubernetes deploy events logs.
+
+Once enabled, navigate to [Services](https://app.logz.io/#/dashboard/spm/service-list/table?timeFrame=2h&compareTo=1d) and choose one of your running services. The deployment marker will appear in your graphs, marked by a dotted vertical line.
+
+![deployment popup](https://dytvr9ot2sszz.cloudfront.net/logz-docs/services/deplyment-popup.png)
+
+You can view additional deployment data by clicking on the line. This data includes the deployment time, the associated service and environment, and a quick link to view the commit in your logs.
+
+Click **Go to commit** to access and view your own code related to this deployment, allowing you to probe deeper into the relevant data.
+
+To activate the **Go to Commit** button, go to **your app or service** and add the following annotation to the metadata of each resource's versioning you want to track: `logzio/commit_url: ""`, and the URL structure should be: "https://github.com/`<account>`/`<repository>`/commit/`<commit-hash>`". [Learn more](https://github.com/logzio/logzio-helm/tree/master/charts/logzio-k8s-events#deployment-events-versioning).
+{:.info-box.note}
+
+
 <!-- ### Logs overview
 
 All of the logs related to the service are shown at the bottom of the page. This view includes a graph view of the log levels and a table view with the following:
diff --git a/_source/user-guide/k360/index.md b/_source/user-guide/k360/index.md
index 5b3c02f71..0f4a643c4 100644
--- a/_source/user-guide/k360/index.md
+++ b/_source/user-guide/k360/index.md
@@ -155,6 +155,29 @@ The **Metrics** tab presents useful data in graph form. These graphs provides a
 
 ![Stateful menu Overview](https://dytvr9ot2sszz.cloudfront.net/logz-docs/k360/metrics-quick-view.png)
 
+#### Track Deployment Data
+{:.no_toc}
+
+You can enrich your Kubernetes 360 graphs by adding an indication of recent deployments, helping you determine if a deployment has increased response times for end-users, altered your application's memory/CPU footprint, or introduced any other performance-related changes.
+
+To enable deployment tracking ability, run the [**Telemetry Collector**](https://app.logz.io/#/dashboard/send-your-data/agent/new) on your Kubernetes clusters. You can also activate this process **manually** by installing [Logz.io Kubernetes events Helm chart](https://app.logz.io/#/dashboard/integrations/Kubernetes:~:text=user%20guide.-,Send%20your%20deploy%20events%20logs,-This%20integration%20sends). 
+
+Once enabled, the graphs will include a deployment marker, marked by a dotted vertical line.
+
+You can view additional deployment data by clicking on the line. This data includes the deployment time, the associated service and environment, and a quick link to view the commit in your logs.
+
+Click **Go to commit** to access and view your own code related to this deployment, allowing you to probe deeper into the relevant data.
+
+
+To activate the **Go to Commit** button, go to **your app or service** and add the following annotation to the metadata of each resource's versioning you want to track: `logzio/commit_url: ""`, and the URL structure should be: "https://github.com/`<account>`/`<repository>`/commit/`<commit-hash>`". [Learn more](https://github.com/logzio/logzio-helm/tree/master/charts/logzio-k8s-events#deployment-events-versioning).
+{:.info-box.note}
+
+
+logzio/commit_url: ""
+
+![deployment menu](https://dytvr9ot2sszz.cloudfront.net/logz-docs/k360/k360-deploy.png)
+
+
 ### Traces tab
 {:.no_toc}