> For the complete documentation index, see [llms.txt](https://docs.trilio.io/openstack/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trilio.io/openstack/admin-guide/grafana-monitoring/trilio-snapshot-and-backup-exporter-metric-information.md).

# Trilio Snapshot and Backup exporter Metric Information

***

## Metrics Overview

| Metric                          | Description                         |
| ------------------------------- | ----------------------------------- |
| `mysql_trilio_snapshots_info`   | Snapshot counts grouped by state    |
| `mysql_trilio_restore_info`     | Restore metrics                     |
| `openstack_protected_vm`        | Number of protected VMs per project |
| `mysql_trilio_backup_size_info` | Snapshot storage usage in GB        |
| `mysql_trilio_snapshots_status` | Snapshot-level status information   |
| `trilio_allowed_quota_value`    | Allowed quota limits                |
| `trilio_quota_high_watermark`   | Highest observed quota usage        |
| `trilio_workload_info`          | Workload metadata                   |
| `trilio_workload_vm_info`       | VM metadata for workloads           |

***

## Metrics Details

### `mysql_trilio_snapshots_info`

Provides per-project snapshot counts grouped by snapshot state (`successful`, `failed`, `running`).

**Example**

```
mysql_trilio_snapshots_info{status="error"} 3
```

***

### `mysql_trilio_restore_info`

Provides information about restore operations.

**Example**

```
count(mysql_trilio_restore_info{status="error"})
```

***

### `openstack_protected_vm`

Shows the number of unique protected VMs per project.

**Example**

```
openstack_protected_vm{ProjectID="proj1"} 25
```

***

### `mysql_trilio_backup_size_info`

Provides aggregated snapshot storage metrics per project, normalized to **GB**.

**Example**

```
mysql_trilio_backup_size_info{ProjectID="proj1"} 450.75
```

***

### `mysql_trilio_snapshots_status`

Provides snapshot-level granularity, exposing individual snapshot identity and status.

**Example**

```
mysql_trilio_snapshots_status{ProjectID="p1",WorkloadID="w1",SnapshotID="123",SnapshotName="daily-backup",status="successful"} 1
```

***

### `trilio_allowed_quota_value`

Exposes allowed quota limits per project and quota type.

**Example**

```
trilio_allowed_quota_value{ProjectID="p1",QuotaName="Snapshots"} 100
```

***

### `trilio_quota_high_watermark`

Reports the highest observed quota usage for each quota type per project.

**Example**

```
trilio_quota_high_watermark{ProjectID="p1",QuotaName="Snapshots"} 80
```

***

### `trilio_workload_info`

Exports metadata for all workloads, including lifecycle and configuration details.

**Example**

```
trilio_workload_info{ID="123",ProjectID="p1",DisplayName="TestWorkload",Status="available"} 1
```

***

### `trilio_workload_vm_info`

Exports VM-level metadata associated with Trilio workloads.

**Example**

```
trilio_workload_vm_info{VMID="vm-123",WorkloadID="456",Status="protected"} 1
```

**Note:** The above are just a few examples for better understanding. Any other suitable examples may be used as required.


---

# 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 dynamically by asking a question.

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

```
GET https://docs.trilio.io/openstack/admin-guide/grafana-monitoring/trilio-snapshot-and-backup-exporter-metric-information.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.