Kensa adds one more place to send your traces. Keep the tracing you already have. Your app still creates the traces.
To check fixes, every trace needs two labels: service.version (for example, the commit you shipped)
and deployment.environment.name. When it creates the tracer provider, the SDK fills in both on Vercel and Railway, and the version
on Render. When you're done, check that a real request arrives.
Langfuse
On the Connect screen, choose Yes, I have observability, then Langfuse. Pick your region, enter your Langfuse project's public and secret keys, and choose Connect Langfuse. Use keys made just for Kensa, so you can turn off Kensa's access without affecting anything else.
Kensa first imports the last 24 hours of traces. After that, it checks for new ones every 15 minutes. To check setup, use the trace ID from Langfuse.
To monitor a fix, Kensa reads two fields from your Langfuse observations:
| Langfuse field | Required value |
|---|---|
release | The deployed version you pass to report_fix.deployedVersion |
environment | production |
Keep these values consistent across observations in the same trace. Conflicting versions or environments prevent Kensa from identifying its deployment.
Kensa SDK
Your agent framework's instrumentation captures model and tool calls. The Kensa SDK sends those traces to Kensa.
If your app already creates spans, keep that instrumentation. Otherwise, enable tracing in your agent framework before checking setup. See the Python or TypeScript SDK.
OpenTelemetry
Copy the address from the Connect screen or from get_setup_status.otlpEndpoint. Then set these
variables:
# Use the TRACES variable. The address already ends in /v1/traces.
export OTEL_EXPORTER_OTLP_TRACES_ENDPOINT="https://ingest.kensa.sh/v1/traces"
export OTEL_EXPORTER_OTLP_TRACES_PROTOCOL=http/protobuf
# %20 is the space after "Bearer".
export OTEL_EXPORTER_OTLP_TRACES_HEADERS="authorization=Bearer%20${KENSA_API_KEY}"
export OTEL_SERVICE_NAME=support-agent
export OTEL_RESOURCE_ATTRIBUTES="service.version=<commit sha>,deployment.environment.name=production"If these variables already point to another tool, add Kensa as a second exporter instead of changing them. Each request to Kensa can be up to 4 MiB. Make sure your app sends its last traces before it exits.