Agent skill · data analytics · aiskillstore
latency-tracker
Per-call and aggregated latency tracking for MEV infrastructure. Use when implementing performance monitoring or debugging slow operations. Triggers on: latency, timing, performance, slow, speed, instrumentation.
Why this skill is useful
Provides specific instrumentation patterns and alerting thresholds for tracking latency in MEV infrastructure that the AI wouldn't reliably generate on its own.
What it needs
About 1k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Latency Tracker Per-call and aggregated latency tracking for MEV infrastructure. When to Use Implementing performance monitoring Debugging slow operations Adding instrumentation to code paths Tracking end-to-end latency Setting up alerting thresholds Workflow Step 1: Define Span Hierarchy Structure spans from e2eflow down to individual calls. Step 2: Instrument Code Wrap operations in tracker.span() calls. Step 3: Set Alert Thresholds Configure alerts for latency exceeding expected ranges. --- Span Hierarchy e2eflow (root) ├── rusthotpathcall (5-15ms) │ └── rpcethcall (5-20ms) ├── txsubmit └── txconfirm (1-15s) Usage Alert Thresholds Span Expected Alert ------ ---------- ------- rusthotpath 5-15ms >30ms rpcethcall 5-20ms >50ms e2etosubmit 10-50ms >100ms
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/latency-tracker