> ## Documentation Index
> Fetch the complete documentation index at: https://auth0.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Metric Streams Tags Reference

> View a reference for tags, enum values, and cardinality for metric streams.

> [!WARNING]
>
> **The Metrics Streams feature is in .**

## Metric reference

### auth0.api\_request.count

Counts API requests to your Auth0 tenant with detailed filtering and aggregation tags. A new metric is emitted every 10 seconds and provides per second granularity.

#### Available tags

| Tag Name | Required | Description |
| - | - | - |
| `api` | Yes | API type: `AUTHENTICATION` or `MANAGEMENT` |
| `operation_name` | Yes | HTTP method and path (e.g., `POST /oauth/token`) |
| `operation_result` | Yes | Result: `SUCCESS` or `FAILURE` |
| `tenant` | Yes | Your Auth0 tenant name |
| `failure_code` | No | Failure reason: `RATE_LIMIT`, `ANOMALY_DETECTION`, or `CLIENT_SERVER_ERROR` |
| `country_code` | No | ISO country code from request IP address |
| `client_id` | No | Application Client ID (Authentication API only) |
| `connection_id` | No | Connection ID (Authentication API only) |
| `grant_type` | No | OAuth 2.0 grant type (Authentication API only) |
| `batch_seq` | Yes | Sequence number for metrics with identical tags and timestamp (temporary, will be removed after Beta) |

> [!WARNING]
>
> The `client_id` and `connection_id` tags can generate high cardinality in environments with many unique clients or connections, potentially increasing monitoring costs. Use these tags selectively.

> [!NOTE]
>
> Metric streams do not include API calls that are cached or blocked by Auth0's Web Application Firewall (WAF) at the edge to prevent system overload.

#### Enum values

**api**

* `AUTHENTICATION` - Authentication API requests
* `MANAGEMENT` - Management API requests

**operation\_result**

* `SUCCESS` - Request completed successfully
* `FAILURE` - Request failed with client or server error

**failure\_code** (only present when `operation_result` is `FAILURE`)

* `RATE_LIMIT` - Request exceeded rate limit
* `ANOMALY_DETECTION` - Blocked by Auth0's attack protection
* `CLIENT_SERVER_ERROR` - HTTP 4xx or 5xx error

## Metric cardinality

Cardinality refers to the number of unique time series generated by your metrics. Higher cardinality increases monitoring costs.

| Tag | Cardinality | Impact |
| - | - | - |
| `api` | Low | 2 unique values (Authentication, Management) |
| `operation_name` | Medium | Varies by API operations used |
| `operation_result` | Low | 2 unique values (Success, Failure) |
| `tenant` | Medium | 1 per Auth0 tenant |
| `failure_code` | Low | 3 unique values (only on failures) |
| `grant_type` | Low | Limited OAuth 2.0 grant types |
| `batch_seq` | Low | Temporary tag (removed after Beta) |

> [!WARNING]
>
> Use `client_id` and `connection_id` tags carefully. In environments with many applications or connections, these tags can significantly increase costs. Consider filtering to specific clients or aggregating these tags if detailed granularity isn't required.


## Related topics

- [About Metric Streams](https://auth0.com/docs/deploy-monitor/metric-streams.md)
- [How to Create Metric Streams](https://auth0.com/docs/deploy-monitor/metric-streams/create.md)