OpenParable
Skip to content
← Back to skills

Detect N Plus One

Testing & Quality
detect-n-plus-one

Detect N Plus One is an Agent Skill for testing & quality published in the jaegertracing/jaeger repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Detect N+1 query patterns in a trace, where one parent operation triggers many near-identical child spans (often database calls). Use when a trace is slow and shows repeated downstream calls, or when the user asks about N+1, repeated queries, or chatty DB access.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/jaegertracing/jaeger/blob/HEAD/cmd/jaeger/internal/extension/jaegerquery/internal/mcptools/skills/detect-n-plus-one/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/detect-n-plus-one, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Detect N+1 Query Patterns

When this applies

A parent span has many child spans with the same operation name and similar duration, typically database queries or RPC calls.

Procedure

  1. Find candidate traces with search_traces.
  2. Pull the span tree with get_trace_topology; group child spans by operation name under each parent.
  3. Flag any group with more than 10 near-identical siblings as a potential N+1 pattern. Check that children have similar durations (within 2x of the median).
  4. Inspect repeated siblings with get_span_details to confirm they target the same downstream service and carry similar attributes.
  5. Report: the parent span (service, operation), the repeated child operation, the count, total wall-clock time consumed, and whether children run sequentially or in parallel.

Gotchas

  • Parallel fan-out can look like N+1 but is intentional — check whether children overlap in time before flagging.
  • Batch operations may share an operation name but carry different payloads — check span attributes to distinguish.