> For the complete documentation index, see [llms.txt](https://docs.pipekit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pipekit.io/using-pipekit/metrics-and-alerts.md).

# Metrics & Alerts

Pipekit Workflow Metrics

Pipekit collects OpenTelemetry metrics from your Argo Workflows and Kubernetes cluster and displays them as dashboards at [Pipekit](https://pipekit.io/metrics).

Metrics are free and run on every cluster. You do not need to ask us to turn them on.

To stop the collector reading your cluster, set `features.metrics.scrapeCluster` to `false` in the Pipekit Agent chart. The collector still runs but sends no cluster telemetry. The collector's chip on the Clusters page stays green, because the collector keeps reporting on itself.

## 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, contact us through your Slack support channel or email `hello@pipekit.io`.

## Troubleshooting

### Missing node and pod metrics

The collector reads the Kubernetes API server and the kubelet on each node over HTTPS. Many clusters give their kubelets a self-signed serving certificate. When the collector cannot verify one, it stops reporting node and pod metrics. Your Argo Workflows metrics keep arriving, because those come from the workflow controller instead.

Set `features.metrics.insecureK8s` to `true` in the Pipekit Agent chart to stop the collector checking these certificates.

{% hint style="info" %}
This also stops the collector checking the Kubernetes API server certificate, which it verifies with the cluster's service account CA.
{% endhint %}