Oodle Traces — Search and Analysis

This skill teaches the agent to search Oodle traces with the right service / time / duration filters and to fetch full trace detail by ID.

Prerequisites

brew install oodle-ai/oodle/oodle
oodle configure

Confirm the traces endpoint works (use a recent time window):

oodle traces list --from -15m --to now -o json | jq 'length'

Command Execution Order

Before running any oodle command:

1. Check whether a service name and approximate time window are already in context.
2. If not, run oodle traces list --from -1h --to now -o json | jq -r '.[].service' | sort -u to discover services that emitted traces recently.
3. Build the search with --service, --from, --to and at least one of --error / --min-duration / --operation.
4. To inspect a single trace, run oodle traces get <trace-id> -o json.
5. Do not run oodle traces list without a --service filter on production environments.

Quick Reference

Common Operations

Searching for errors in the last hour

# ✅ CORRECT — scoped to one service, narrow time window, error filter on
oodle traces list --service api --error --from -1h --to now -o json

# ❌ WRONG — no service, no error filter, huge result set
oodle traces list --from -1h --to now -o json

Searching for slow traces

# ✅ CORRECT — slow checkout traces in the last hour
oodle traces list --service checkout --min-duration 500 --from -1h --to now -o json

# ✅ CORRECT — narrow further by operation when you know the endpoint
oodle traces list --service checkout --operation POST_/cart --min-duration 500 --from -1h -o json

# ❌ WRONG — listing everything and sorting client-side wastes the API budget
oodle traces list --service checkout --from -1h -o json | jq 'sort_by(.durationMs) | reverse | .[0:10]'

Fetching a full trace

# ✅ CORRECT — list to discover trace ids, then get the one of interest
TRACE_ID=$(oodle traces list --service api --error --from -15m -o json | jq -r '.[0].traceId')
oodle traces get "$TRACE_ID" -o json

# ❌ WRONG — `oodle traces get` without an id (it expects the id as a positional arg)
oodle traces get

Time window flags

--from and --to accept the same formats as the rest of the CLI:

# ✅ CORRECT
oodle traces list --service api --from -30m --to now -o json

# ❌ WRONG — human strings are not parsed
oodle traces list --service api --from "30 minutes ago"

Best Practices

Always specify --service to scope the search

Trace volume can be massive; an unfiltered list is expensive and rate-limited.

# ✅ CORRECT
oodle traces list --service api --from -1h -o json

# ❌ WRONG — full-tenant scan
oodle traces list --from -1h -o json

Use --error to find failing traces, not client-side filtering

--error pushes the predicate to the server and returns matches faster.

# ✅ CORRECT
oodle traces list --service api --error --from -1h -o json

# ❌ WRONG — fetches every trace then filters client-side
oodle traces list --service api --from -1h -o json | jq '.[] | select(.status=="error")'

Use --min-duration to find slow traces, not client-side sort

# ✅ CORRECT — server-side filter, returns ~the right number of rows
oodle traces list --service api --min-duration 500 --from -1h -o json

# ❌ WRONG — pulls everything, sorts on the client
oodle traces list --service api --from -1h -o json | jq 'sort_by(.durationMs) | reverse'

Keep time windows ≤ 24h for list; widen by re-querying, not by raising --to

A 7-day list returns too many rows and risks timeouts. Page by hour.

# ✅ CORRECT — bounded window
oodle traces list --service api --error --from -1h --to now -o json

# ❌ WRONG — multi-day list
oodle traces list --service api --error --from -7d --to now -o json

Failure Handling

References

• Oodle CLI repo
• Oodle docs
• OpenTelemetry trace concepts