1. Connect Kensa
Open your app's repository and give your coding agent this prompt:
Fetch https://kensa.sh/install and follow it.Follow the sign-in flow. Your coding agent will help configure the right connection.
If you already have traces
You can connect the tracing you already use to Kensa. Choose the path that matches your setup:
- Langfuse: Connect your Langfuse project. Kensa imports existing traces automatically.
- OpenTelemetry: Add Kensa as another destination for your traces. Apply the configuration through your normal deployment process.
If you're setting up tracing
Your coding agent will add the Kensa SDK and enable tracing in your agent framework. Open a pull request, review the changes, and merge it. Configure your Kensa API key in your deployment environment, then deploy your app.
2. Check the connection
For Langfuse, Kensa starts by importing recent traces. For SDK or OpenTelemetry setups, use your deployed app, such as sending your chatbot a message or running an agent task.
Then ask your coding agent:
Check that Kensa is receiving production traces.3. Explore your issues
Open Issues to review what Kensa finds. Each issue includes evidence and the expected behavior.
Choose Copy agent prompt to give an issue to your coding agent.
Troubleshooting setup
API keys
If you use the SDK or OpenTelemetry, you need the project's API key. The Connect screen creates one
if the project doesn't have one yet. You can also make one on the page where you chose
Connect agent: open Configure tracing credentials and choose Generate new key. Save it
as KENSA_API_KEY in your secret store when it's shown.
For manual setup, follow Tracing.
Check a specific request
Capture the request's trace ID from your instrumentation, or copy it from Langfuse. The Python and TypeScript examples show how to read an OpenTelemetry trace ID. Ask your coding agent:
Call get_setup_status with traceId "<the request's trace ID>".
Report traceReceived and productionMonitoringReady separately.traceReceived: truemeans Kensa received that request. Local traffic is enough to verify setup.productionMonitoringReady: truemeans Kensa has received a production trace with a version in the last 24 hours. To monitor a specific fix, ship it and report its deployed version.
Trace delivery
Check that your app creates spans, the API key belongs to the connected project, and buffered spans
have been flushed. In a short-lived process, call kensa.flush() after the request finishes; await
it in TypeScript. For Langfuse, imports run every 15 minutes after the initial import.
If the trace arrives but production monitoring isn't ready, check its deployed version and
environment. Use the environment where the request actually ran, such as development or production.
Next steps: Describe your agent's job · Fix and monitor an issue