backend-telemetry-hardening
Implements backpressure, validation, and queue management to stabilize ingestion under high load.
Install
mkdir -p .claude/skills/backend-telemetry-hardening && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/15150" && unzip -o skill.zip -d .claude/skills/backend-telemetry-hardening && rm skill.zipInstalls to .claude/skills/backend-telemetry-hardening
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Harden backend telemetry ingestion under load (MQTT spikes, DB pool pressure, validation failures).Key capabilities
- →Quantify input/error rates, queue depth, and p95 latency to identify bottlenecks
- →Implement bounded queues and explicit backpressure for ingress
- →Throttle and batch MQTT messages per topic
- →Tune TimescaleDB pool limits and batch writes
- →Validate data at the boundary and route failures to a dead-letter queue
- →Apply idempotency guards, circuit-breaking, and bounded retries
How it works
The skill profiles current system performance to identify bottlenecks, then applies strategies like bounded queues, topic-based throttling, database pool tuning, and validation at the boundary.
Inputs & outputs
When to use backend-telemetry-hardening
- →Debug telemetry ingestion lag
- →Optimize database pool usage
- →Harden MQTT ingestion
About this skill
TRIGGERS
- MQTT bursts causing lag
- TimescaleDB pool saturation/wait times
- Ingestion queue growth/timeouts
- Zod validation error spikes
- Persistence inconsistency
STEPS
- Profile: Quantify input/error rates, queue depth, p95 latency. ID bottleneck (ingress/validation/persistence).
- Ingress: Bounded queues|Explicit backpressure|Separate parse/persistence|NO blocking CPU/sync I/O in hot paths.
- MQTT: Per-topic throttle/batch|Coalesce safe telemetry|Idempotent reconnects.
- TimescaleDB: Measure pool util/wait|Tune limits|Batch writes|Parameterized SQL|Selective columns/deterministic order.
- Validation (Zod): Validate at boundary|Route failures to dead-letter + reason|Preserve observability|NEVER bypass validation.
- Resilience: Idempotency guards|Circuit-breaking/load-shedding|Bounded/jittered retries.
- Verify: Burst & steady-state tests|Check pool stability, latency, data integrity.
- CI Checks:
pnpm --filter @ice-truck/backend lintpnpm --filter @ice-truck/backend type-checkpnpm --filter @ice-truck/backend test
EXIT CRITERIA
- Stable ingestion under load
- NO uncontrolled queue/pool exhaustion
- Validation failures quarantined, ZERO corruption
REFS
docs/DEFINITION_OF_DONE.md | docs/API.md | docs/THREAT_MODEL.md | backend/src/services/ | backend/tests/ | tests/k6/
How it compares
This approach systematically hardens telemetry ingestion paths against various load-induced failures, unlike ad-hoc fixes for individual issues.
Compared to similar skills
backend-telemetry-hardening side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| backend-telemetry-hardening (this skill) | 0 | 2mo | No flags | Advanced |
| langsmith-fetch | 6 | 7mo | Review | Intermediate |
| langfuse-common-errors | 1 | 1mo | Caution | Beginner |
| autotel | 0 | 2mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
langsmith-fetch
ComposioHQ
Debug LangChain and LangGraph agents by fetching execution traces from LangSmith Studio. Use when debugging agent behavior, investigating errors, analyzing tool calls, checking memory operations, or examining agent performance. Automatically fetches recent traces and analyzes execution patterns. Requires langsmith-fetch CLI installed.
langfuse-common-errors
jeremylongshore
Diagnose and fix common Langfuse errors and exceptions. Use when encountering Langfuse errors, debugging missing traces, or troubleshooting integration issues. Trigger with phrases like "langfuse error", "fix langfuse", "langfuse not working", "debug langfuse", "traces not appearing".
autotel
jagreehal
Use when instrumenting with trace/span/track, reviewing code for logging and observability patterns, converting console.log to wide events, adding structured errors, setting up canonical log lines, configuring init(), adding subscribers, or working in the autotel monorepo.
typescript-node-esm-compiler-runtime
GonkaGate
Own TypeScript plus Node.js ESM compiler/runtime correctness. Use whenever the real question is why TypeScript compiles but Node fails, how `tsconfig`/`package.json`/entrypoint/runtime mode must align, whether relative imports should use `.js` or `.ts`, how `nodenext`/`node20`/`verbatimModuleSyntax`
ai-debug-harness
DeandreFu
Self-driving Electron + Node debug harness with NDJSON logs, Playwright E2E, doctor preflight, and a YAML-frontmatter cookbook of known causes. Use when a voice-chat E2E flow misbehaves locally, audio publish silently fails, the agent worker emits warnings, or any LiveKit/Electron/Fastify error appe
debug-cross-service-auth
J-Akiru5
Use when: diagnosing Supabase JWT handoff failures from Next.js frontend to Laravel backend including headers, CORS, issuer, audience, and secret mismatches.