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

# Metrics

Define project measurements that Workflows can emit and Monitoring can chart.

Metrics defines named measurements for operational execution.

![The Metrics page showing current metric definitions with type, unit and creation metadata.](https://3370306531-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlgSglJDQZxDZdn20CUcl%2Fuploads%2Fgit-blob-487fc7fabb5b9311b40c0c021b10db6747d793f7%2Fcontrol-metrics.png?alt=media)

This Control page defines **what a metric is**. It does not show recorded metric values, charts or history. Runtime executions write values against these definitions; Monitoring is where those values are used for operational charts and aggregates.

### Definition

A Metric has a name, description and value type. Current value types are:

* **Number**;
* **String**;
* **Boolean**;
* **Enum**, with configured allowed values.

A unit can be supplied as free text, for example `EUR` or `days`.

Enum definitions must contain at least **two distinct values**. Duplicate enum values are rejected, and updates are validated when values are removed.

### Access

Project members can read Metric definitions. Creating and changing them requires Builder-level Project access. Operators do not see Control in the current navigation.

Metric names are unique among active Metrics in a Project. Deletion is soft, so historical data can remain associated with the old definition.

### Referenced Metrics cannot be deleted

Lleverage blocks deletion while a Workflow still references the Metric. Dynamic/template-style references also fail closed rather than allowing the definition to disappear while a Workflow may still depend on it.

Use Metrics for measurements that should become part of operational Monitoring. Do not use them as a general-purpose data store.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.lleverage.ai/administer-and-govern/control/metrics.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.