Skip to main content
Version: v1.31.2

Monitoring / Tracing


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


To configure the tracing, you need to set in the configuration the endpoint to your OTLP collector.

# ...
openTelemetryOtlpEndpoint: http://localhost:4318
# ...

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


If you want to try the OpenTelemetry integration locally, follow this README to setup Jaeger and see your traces.


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


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.


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


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

Use specific port for the monitoring

You can configure a different port for the monitoring endpoints.
This is useful if you want to expose the monitoring endpoints on a different port than the main service.

# ...
monitoringPort: 1032
# ...

By default the monitoring endpoints are exposed on the same port as the main service.

Get the latest GO Feature Flag updates