# Metrics

Uncover the deep insights into your Argo Workflows and Kubernetes environment and gain real-time insights into your system's health... for free!

## Sign up

To get started with Pipekit Workflow Metrics, sign up for a free account at [Pipekit](https://pipekit.io/metrics-signup). You will be prompted to create an [Organization](/pipekit/organization.md) and a [Cluster](/pipekit/clusters.md). Follow the on-screen prompts to install the [Pipekit Agent](/pipekit-agent.md) on your Kubernetes cluster.

Once connected, you should start to see metrics flowing into the dashboards at [Pipekit](https://pipekit.io/metrics).

## Data

The Pipekit Agent uses OpenTelemetry to collect metrics from your Kubernetes cluster. The metrics are sent to the Pipekit backend where they are sanitized, stored and retrieved for visualization.

We only collect metrics that are then shown in the Pipekit dashboard. We do not collect any other data from your cluster. You can view the OpenTelemetry configuration by inspecting the Pipekit Agent Collector configmap in your cluster.

### Data Retention

Pipekit retains your metrics data for 10 days before destroying it. If you need to extend this period, please contact us through your Slack support channel or email `hello@pipekit.io`.

## Existing Pipekit users

If you are an existing Pipekit user, contact us through your Slack support channel or email `hello@pipekit.io` and we will enable the metrics feature for your existing cluster(s).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.pipekit.io/pipekit/metrics.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.