---
sidebar_position: 80
title: Monitoring / Tracing
description: Monitoring and Tracing of the relay proxy.
---

## Tracing

The **relay proxy** is able to trace the requests it is handling. This is done by using OpenTelemetry.

### Configuration
To configure the tracing, you need to set in the configuration the endpoint to your OTLP collector.
```yaml
# ...
openTelemetryOtlpEndpoint: http://localhost:4318
# ...
```

All your requests will be traced and sent to the collector with the service name **`go-feature-flag`**.

:::note
If you want to try the OpenTelemetry integration locally, follow this [README](https://github.com/thomaspoignant/go-feature-flag/tree/main/cmd/relayproxy/testdata/opentelemetry)
to setup Jaeger and see your traces. 
:::

## Monitoring

The **relay proxy** offers some endpoints for you to be able to see how it behaves.

### `/health`
Making a **GET** request to the URL path `/health` will tell you if the relay proxy is ready to
serve traffic.

This is useful especially for loadbalancer to know that they can send traffic to the service.

### `/info`
Making a **GET** request to the URL path `/info` will give you information about the actual state
of the relay proxy.

### `/metrics`
This endpoint is providing metrics about the relay proxy in the prometheus format.



