Telemetry
For teams that need route-level latency, errors, and traffic visibility

API Reliability Monitoring

Track API request volume, status codes, latency, timeouts, customer impact, and failed endpoints with SQL.

Why this works
  • Route-level p50 and p95 latency without building a custom metrics system.
  • Failure analysis by endpoint, method, status code, feature, and account.
  • Alerts around 5xx spikes, slow routes, and sudden traffic drops.

Agent prompt

Paste this into your coding agent

Replace YOUR_API_KEY after signup, then ask the agent to run the product flow and verify the first events.

agent prompt

API Reliability Monitoring setup prompt

text
Add Telemetry instrumentation for API reliability.

Use /skill.md and this Telemetry API key: YOUR_API_KEY

Please log each important API endpoint with route_template, method, status_code, status, latency_ms, user_id or team_id when available, request_size_bytes, response_size_bytes, and error_type.

Create:
1. A table for API request events.
2. Charts for request volume, error rate, p50 and p95 latency, and top failing endpoints.
3. Alerts for elevated 5xx rate, slow p95 latency, and sudden traffic drops.

Do not log request bodies, auth headers, cookies, secrets, or raw user content.

Setup steps

  1. 1Log completed and failed API requests from server handlers.
  2. 2Use route templates instead of raw URLs to keep cardinality clean.
  3. 3Capture status, latency, method, feature, team, and error type.
  4. 4Create dashboards and alerts for error rate, p95 latency, and top failing routes.

Events to capture

api_request_startedapi_request_completedapi_request_failedapi_timeoutapi_rate_limitedcustomer_impact_detected

Questions unlocked

  • Which routes are slowest by p95 latency?
  • Which customer accounts are affected by errors?
  • Where did traffic suddenly drop or spike?

Next step

Create the API key your agent will use

The free plan is enough to run the prompt, send test events, and review the first dashboard.

Related pages