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
- 1Log completed and failed API requests from server handlers.
- 2Use route templates instead of raw URLs to keep cardinality clean.
- 3Capture status, latency, method, feature, team, and error type.
- 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
Claude Code Observability
Give Claude Code a prompt that makes telemetry part of the implementation pass instead of a separate cleanup project.
Open pageCursor Telemetry Setup
A copyable setup prompt for adding event tables, funnel tracking, and dashboards from inside Cursor.
Open pageCodex Instrumentation Prompt
A focused prompt that asks Codex to instrument the rest of the product, verify events, and summarize coverage gaps.
Open page