Skip to content

Commit

Permalink
k360
Browse files Browse the repository at this point in the history
  • Loading branch information
Simplychee committed Oct 30, 2023
1 parent d76f7b6 commit 889fdc6
Showing 1 changed file with 16 additions and 0 deletions.
16 changes: 16 additions & 0 deletions _source/user-guide/k360/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -155,6 +155,22 @@ 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) and sending Kubernetes deploy events logs.

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.

![deployment menu](https://dytvr9ot2sszz.cloudfront.net/logz-docs/k360/k360-deploy.png)


### Traces tab
{:.no_toc}

Expand Down

0 comments on commit 889fdc6

Please sign in to comment.