Developer Docs•stable•Updated 2026-07-06
Logs & Traces
Search Gateway requests, direct ingestion attempts, webhook deliveries and developer signals from one operational view.
Logs & Traces is the developer investigation surface for Kadryn traffic.
Use it to answer:
- did Kadryn receive the request?
- did Gateway forward it?
- did direct ingest accept or reject it?
- did a webhook deliver successfully?
- what provider, model, project and environment were involved?
- what trace ID or request group ID connects this event to my app logs?
What appears here
Depending on your workspace, Logs & Traces can show:
- Gateway requests;
- direct ingestion attempts;
- webhook deliveries;
- policy decisions;
- fallback usage;
- errors;
- synthetic tests;
- expensive requests;
- request groups;
- trace IDs.
What to search by
Useful search fields include:
- Kadryn request ID;
- trace ID;
- request group ID;
- provider request ID;
- project;
- feature;
- environment;
- provider;
- model;
- status;
- error code;
- webhook endpoint.
Common filters
Use filters to narrow the investigation:
| Filter | Use it when |
|---|---|
| Gateway | You are debugging runtime provider traffic. |
| Direct ingest | You are debugging usage import. |
| Webhooks | You are debugging deliveries or redeliveries. |
| Errors only | You need failures first. |
| Expensive only | You are investigating high-cost calls. |
| Fallback used | You suspect provider fallback or routing changes. |
| Synthetic only | You are validating tests rather than production traffic. |
Gateway investigation
When a Gateway request fails:
- search by trace ID or request group ID;
- inspect status and error code;
- check provider route status;
- check model and provider;
- review policy decision if blocked;
- preserve Kadryn request ID in support notes.
Direct ingest investigation
When an ingestion event is missing:
- search by idempotency key, provider request ID or trace ID;
- check accepted vs rejected attempts;
- inspect validation errors;
- verify timestamp and environment;
- check whether the event appears in Costs after rollup.
Webhook investigation
When a webhook delivery fails:
- search by endpoint or delivery ID;
- inspect response status;
- check retry state;
- verify signature handling;
- redeliver only after fixing the receiver.
Synthetic traffic
Synthetic traffic is useful for validation.
Use it to verify:
- API key setup;
- Gateway readiness;
- provider route readiness;
- webhooks endpoint readiness;
- log visibility;
- trace search.
Do not treat synthetic traffic as proof of real production traffic.
Logging guidance
Keep these IDs in your application logs:
- trace ID;
- request group ID;
- Kadryn request ID;
- provider request ID;
- idempotency key hash or prefix;
- project;
- environment.
Do not log secrets or full Authorization headers.