Build a Hosted Claude Client-Side Latency and Budget Observability Engine
Track client-side HTTP request latencies and per-call token costs for hosted Claude API workloads. Flag budget pacing anomalies and latency threshold breaches for platform engineering oversight.
What you are building
The core problem, expected build, and operating context for this challenge.
Track client-side HTTP request latencies and per-call token costs for hosted Claude API workloads. Flag budget pacing anomalies and latency threshold breaches for platform engineering oversight.
AI Platform Reliability Engineer
Ingest normalized client request telemetry logs containing round-trip time and token usage.
Calculate token consumption costs against published tier pricing and verify budget burndown velocity.
Detect client-side p95 latency degradations and error bursts across caller application IDs.
Generate Claude-assisted platform incident briefings with recommended client retry pacing limits.
Web dashboard displaying real-time token spend gauges, latency percentiles, and downloadable incident reviews.
Construct a synthetic log stream of 500 Anthropic API client responses with client timestamps and token counts. Starter examples below are synthetic. They are not downloaded records.
Anthropic Python SDK Utilize Anthropic Python SDK client invocation standards, message structures, and usage counter patterns.
langfuse, anthropic, pydantic. langfuse provides open tracing abstractions to capture client-side duration and token metrics cleanly. Hosted Claude API accessed over HTTPS for log explanation and diagnostic report generation.
Submit runnable source, pinned dependencies, setup commands, a working interface, example outputs, and a recorded end-to-end demo. Include tests and an action log.
Computes cumulative input and output token spend strictly from client usage metadata.
Flags client application endpoints exceeding configured latency SLAs without assuming server internals.
Synthesizes structured incident action items for client-side connection pool tuning.
```json [ { "input": { "app_id": "customer-support-bot", "requests": 150, "total_input_tokens": 120000, "total_output_tokens": 30000, "client_p95_ms": 4200, "daily_budget_usd": 50 }, "expected_output": { "calculated_spend_usd": 0.81, "budget_pacing": "healthy", "latency_sla_breach": true, "recommendation": "enable_streaming_or_reduce_max_tokens" } }, { "input": { "app_id": "batch-document-indexer", "requests": 500, "total_input_tokens": 25000000, "total_output_tokens": 4000000, "client_p95_ms": 11500, "daily_budget_usd": 100 }, "expected_output": { "calculated_spend_usd": 135, "budget_pacing": "exceeded", "latency_sla_breach": true, "recommendation": "throttle_client_concurrency_apply_batch_api" } } ] ```
Performs client-side telemetry observability only, making no assertions about proprietary model server hardware or internal routing. Use mock external writes. Require human review before any real deployment.
Participation guide
Performs client-side telemetry observability only, making no assertions about proprietary model server hardware or internal routing. Use mock external writes and human review.
How work is evaluated
Computes cumulative input and output token spend strictly from client usage metadata. Flags client application endpoints exceeding configured latency SLAs without assuming server internals. Synthesizes structured incident action items for client-side connection pool tuning.
Runnable source, pinned dependencies, setup commands, working interface, example outputs, recorded demo, tests, and action logs.
Challenge datasets
Public datasets, plus the private datasets you have access to.
How submissions are scored
These dimensions define what the evaluator checks and which criteria separate a passable run from a strong one.
Complete workflow
Ingest normalized client request telemetry logs containing round-trip time and token usage. Calculate token consumption costs against published tier pricing and verify budget burndown velocity. Detect client-side p95 latency degradations and error bursts across caller application IDs. Generate Claude-assisted platform incident briefings with recommended client retry pacing limits.
Missing or incorrect.
Partly complete, with documented gaps.
Complete, with reproducible evidence.
Correctness and evidence
Computes cumulative input and output token spend strictly from client usage metadata. Flags client application endpoints exceeding configured latency SLAs without assuming server internals. Synthesizes structured incident action items for client-side connection pool tuning.
Missing or incorrect.
Partly complete, with documented gaps.
Complete, with reproducible evidence.
Review interface
Web dashboard displaying real-time token spend gauges, latency percentiles, and downloadable incident reviews.
Missing or incorrect.
Partly complete, with documented gaps.
Complete, with reproducible evidence.
Safe execution
Performs client-side telemetry observability only, making no assertions about proprietary model server hardware or internal routing.
This dimension contributes its full weight only when the submission satisfies the requirement. Partial credit is not awarded.
What you should walk away with
Ingest normalized client request telemetry logs containing round-trip time and token usage.
Calculate token consumption costs against published tier pricing and verify budget burndown velocity.
Detect client-side p95 latency degradations and error bursts across caller application IDs.
Generate Claude-assisted platform incident briefings with recommended client retry pacing limits.
Reference links and supporting material
Construct a synthetic log stream of 500 Anthropic API client responses with client timestamps and token counts. Supplied starter examples are synthetic, not source extracts.
Challenge setup
Configuration summary for this challenge.
Challenge input
Input details are not configured.
Langfuse
Open-source LLM observability and evals.
Evaluated output
No output checks are configured.
- Ingest normalized client request telemetry logs containing round-trip time and token usage. Calculate token...
- Computes cumulative input and output token spend strictly from client usage metadata. Flags client applicat...
- Web dashboard displaying real-time token spend gauges, latency percentiles, and downloadable incident reviews.
- 2 public reference cases
- 2 configured tools
Summary shows the first task, up to three tools, and up to three evidence items. Open the technical recipe to view all configured items.
View technical recipe
Configured tools
- Langfuse · Optional
- Langfuse · Optional
Evaluation contract
- Complete workflow · Weight 40
- Correctness and evidence · Weight 30
- Review interface · Weight 20
- Safe execution · Weight 10
Reference cases
- 2 public reference cases
Workflow tasks
No workflow tasks are configured.
Recipe freeze marker
No recipe freeze time is recorded.