From wicked-garden
Distributed tracing analysis for performance investigation and service dependency mapping. Analyze latency breakdowns, identify bottlenecks, map service calls, and correlate slow requests with code changes. Use when: "trace analysis", "distributed tracing", "latency investigation", "slow requests", "service dependencies", "performance tracing"
npx claudepluginhub mikeparcewski/wicked-garden --plugin wicked-gardenThis skill uses the workspace's default tool permissions.
Analyze distributed traces for performance investigation and service dependency mapping.
Provides Ktor server patterns for routing DSL, plugins (auth, CORS, serialization), Koin DI, WebSockets, services, and testApplication testing.
Conducts multi-source web research with firecrawl and exa MCPs: searches, scrapes pages, synthesizes cited reports. For deep dives, competitive analysis, tech evaluations, or due diligence.
Provides demand forecasting, safety stock optimization, replenishment planning, and promotional lift estimation for multi-location retailers managing 300-800 SKUs.
Analyze distributed traces for performance investigation and service dependency mapping.
Use capability-based discovery:
# Discover available integrations via capability detection
# Scan for tracing capabilities by analyzing server descriptions:
# - tracing capability: Dedicated distributed tracing systems
# - apm capability: APM tools that include distributed tracing
# - telemetry capability: Unified observability with tracing support
For each discovered source:
For slow traces:
Build dependency graph:
See refs/bottlenecks-detection.md and refs/bottlenecks-resolution.md for detailed patterns.
Common bottleneck types:
Use wicked-garden:search to find:
| Capability | What to Look For | Provides |
|---|---|---|
| tracing | Distributed tracing, span collection, trace analysis | Distributed traces, span details |
| apm | Performance monitoring with distributed tracing | Traces with performance context |
| telemetry | Unified observability with traces and metrics | Unified traces and metrics |
Fallback: Analyze code for call patterns via wicked-garden:search (database calls, HTTP clients, async operations).
Provide trace analysis with:
See refs/bottlenecks-detection.md and refs/bottlenecks-resolution.md for detailed output templates.
See refs/bottlenecks-detection.md and refs/bottlenecks-resolution.md for detailed analysis of:
Sequential database queries in a loop. Fix with batch queries or JOIN.
Waiting for external APIs sequentially. Fix with Promise.all or async processing.
Repeated identical queries. Fix with caching layer (Redis, in-memory).
Slow database operations. Fix with indexes, query optimization, pagination.
Lock waits or queue delays. Fix with reduced lock scope, optimistic locking.
Identify services on critical path (required for request completion). Focus optimization here.
Single request triggers many downstream calls. Risk of amplified load and cascading failures.
Service A calls B calls A (cycle). Risk of infinite loops and complex debugging.
See refs/dependencies.md for detailed dependency analysis patterns.
When bottlenecks identified, engage wicked-garden:engineering:backend with trace context, code locations, and optimization recommendations.
During build phase:
Emit events:
observe:trace:slow:warningobserve:correlation:found:success