Configure LLM Observability data collection
Site24x7's LLM Observability uses OpenTelemetry to collect telemetry generated by your LLM applications. Instrument your application using an OpenTelemetry-compatible instrumentation library or framework and export the generated telemetry to the Site24x7 OpenTelemetry Protocol (OTLP) endpoint.
Once Site24x7 receives the telemetry, you can analyze LLM performance, token consumption, costs, errors, prompts, traces, and other request-level information under APM > LLM Observability.
Prerequisites
Before configuring LLM Observability, ensure that:
- Your LLM application is instrumented using an OpenTelemetry-compatible instrumentation library or framework.
- You have access to your Site24x7 account.
- Your application can communicate with the Site24x7 OpenTelemetry endpoint.
- The required LLM telemetry is exported using OTLP.
Obtain the Site24x7 OTLP endpoint and API key
To send LLM telemetry to Site24x7:
- Log in to the Site24x7 web client.
- Navigate to APM > OpenTelemetry.
- Copy the OTLP Endpoint and API Key displayed on the Add OpenTelemetry Agent page.
The OTLP endpoint specifies where the telemetry data must be sent, while the API key authenticates the data sent to Site24x7.
Instrument your LLM application
Instrument your LLM application using an OpenTelemetry-compatible library or framework that can generate the telemetry required for LLM Observability. You can configure your instrumentation to export telemetry either directly to the Site24x7 OTLP endpoint or through an OpenTelemetry Collector, which then forwards the telemetry to Site24x7.
Using Traceloop and OpenLLMetry
If you use Traceloop and OpenLLMetry to instrument your LLM application, first configure the appropriate Traceloop SDK for your application language or framework.
Refer to the corresponding Traceloop documentation:
After completing the instrumentation steps for your application, configure Traceloop to export the generated OpenTelemetry data to Site24x7.
Configure Traceloop to export data to Site24x7
Set the following environment variables in the environment where your LLM application runs:
export TRACELOOP_BASE_URL="<SITE24X7_OTLP_ENDPOINT>"
export TRACELOOP_HEADERS="api-key=<SITE24X7_API_KEY>"
Replace:
<SITE24X7_OTLP_ENDPOINT>with the OTLP endpoint copied from Site24x7.<SITE24X7_API_KEY>with the API key copied from Site24x7.
Note: Do not expose the Site24x7 API key in your application source code. Store it securely as an environment variable or through your application’s secret management mechanism.
TRACELOOP_BASE_URLspecifies the OpenTelemetry endpoint to which Traceloop exports the telemetry.TRACELOOP_HEADERSprovides the authentication header required by Site24x7.
Use the base Site24x7 OTLP endpoint without a signal-specific path. The Traceloop SDK automatically appends /v1/traces, /v1/metrics, or /v1/logs based on the telemetry being exported.
Initialize Traceloop
Initialize the Traceloop SDK according to the language or framework used by your application. Refer to the respective Traceloop agent documentation listed above for the appropriate initialization procedure.
| Environment variable | Description | Value for Site24x7 |
|---|---|---|
TRACELOOP_TRACE_CONTENT |
Specifies whether prompts and completions are recorded in spans | Set to false if prompts contain sensitive data |
TRACELOOP_TELEMETRY |
Specifies whether anonymous SDK usage telemetry is sent to Traceloop | false recommended |
Start sending LLM telemetry
Start or restart your application after completing the instrumentation and export configuration.
When the instrumented application makes LLM calls, the OpenTelemetry telemetry generated for those interactions is exported to the configured Site24x7 OTLP endpoint.
Depending on the instrumentation and the information available for each request, the collected data can include details such as the model, provider, request duration, input and output token usage, cost, request time, prompts, and traces.
Verify the data in Site24x7
After your application generates LLM requests:
- Log in to the Site24x7 web client.
- Navigate to APM > LLM Observability.
- Select the required time period.
- Check the Dashboard tab to verify that LLM requests and metrics are being received.
- Open the Prompt Analysis tab to verify individual LLM interactions.
The Dashboard tab provides aggregated information about LLM performance, utilization, token consumption, costs, and errors, while the Prompt Analysis tab provides request-level visibility into individual LLM interactions. This verification flow already exists in your current document and can largely remain unchanged.
Troubleshooting
If LLM data is not displayed in Site24x7, verify that:
- Your LLM application is properly instrumented.
- The application is exporting telemetry using OTLP.
- The configured OTLP endpoint matches the Site24x7 endpoint.
- The Site24x7 API key is correctly provided in the
api-keyheader. - Your application or OpenTelemetry Collector can reach the Site24x7 endpoint.
- The application has generated LLM requests after the configuration was applied.
Also verify that the appropriate Traceloop SDK has been initialized according to the respective setup instructions.
