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

# Conduktor Schema Registry Proxy metrics reference

> Prometheus metrics exposed by Conduktor Schema Registry Proxy: request, authentication and license metrics, plus JVM runtime metrics. Use with Grafana or any Prometheus-compatible system.

Schema Registry Proxy exposes metrics in the Prometheus format that you can scrape and send to your external monitoring system.

## Metrics endpoint

Schema Registry Proxy serves Prometheus metrics on a dedicated port:

```shell title="cURL example" theme={null}
curl -s http://<srp_host>:${OTEL_PROMETHEUS_PORT}/metrics
```

Set the port with [`OTEL_PROMETHEUS_PORT`](/guide/reference/schema-registry-proxy-environment-variables#opentelemetry-configuration) (default `9464`).

<Warning>
  Schema Registry Proxy only starts the metrics endpoint when `OTEL_EXPORTER_OTLP_ENDPOINT` is set. Without it, OpenTelemetry stays disabled and nothing listens on the Prometheus port, even though `OTEL_PROMETHEUS_PORT` has a default. Set `OTEL_EXPORTER_OTLP_ENDPOINT` to your collector address to enable the endpoint.
</Warning>

Setting `OTEL_METRICS_ENABLED` to `false` only stops Schema Registry Proxy from pushing metrics to the OTLP collector. The Prometheus endpoint stays available.

## Request metrics

Schema Registry Proxy records these metrics for every request it handles.

| Prometheus metric name | Metric type | Labels | Description |
| - | - | - | - |
| `schema_registry_requests_total` | counter | `method`, `endpoint`, `status` | Total number of Schema Registry requests |
| `schema_registry_requests_not_found_total` | counter | `method`, `endpoint` | Number of requests that returned HTTP 404 |
| `schema_registry_requests_error_total` | counter | `method`, `endpoint` | Number of requests that returned an HTTP 5xx status |
| `schema_registry_request_duration_seconds` | histogram | `method`, `endpoint` | Duration of Schema Registry requests, in seconds |

The histogram is exported as `schema_registry_request_duration_seconds_bucket` (with a `le` label), `schema_registry_request_duration_seconds_sum` and `schema_registry_request_duration_seconds_count`.

The `endpoint` label holds the matched route pattern, for example `/subjects/{subject}/versions`, not the concrete URL. This keeps the number of label values small.

## Authentication and license metrics

| Prometheus metric name | Metric type | Labels | Description |
| - | - | - | - |
| `basic_auth_credentials_reload_total` | counter | `result` (`success` or `failure`) | Number of attempts to load the HTTP Basic credentials file. Only recorded with `AUTH_PROVIDER=basic` |
| `license_expiry_timestamp_seconds` | gauge | | Expiry date of the Conduktor license, as a Unix timestamp. Not exported for licenses without an expiry date |

Alert on `basic_auth_credentials_reload_total{result="failure"}`. A failure means the credentials file on disk and the credentials in force have drifted apart.

Alert on `license_expiry_timestamp_seconds` before a restart would fail. For example, this expression is true when the license expires in less than 30 days:

```promql theme={null}
license_expiry_timestamp_seconds - time() < 30 * 86400
```

## JVM runtime metrics

Schema Registry Proxy also exports the standard JVM runtime metrics from OpenTelemetry (memory, garbage collection, threads, CPU and class loading). For the list of metrics and their names, see the [OpenTelemetry JVM metrics documentation](https://opentelemetry.io/docs/specs/semconv/runtime/jvm-metrics/).

## Related resources

* [Schema Registry Proxy environment variables](/guide/reference/schema-registry-proxy-environment-variables)
* [Schema Registry Proxy configuration examples](/guide/conduktor-in-production/deploy-artifacts/deploy-schema-registry-proxy/configuration)
* [Troubleshoot Schema Registry Proxy](/guide/conduktor-in-production/deploy-artifacts/deploy-schema-registry-proxy/troubleshooting)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.