dd-debugger
Skill1k starsChanged 6 months agoApache-2.0View on GitHub
Live Debugger - inspect runtime argument/variable values in production by placing log probes on methods. Use when asked what values a function receives, what parameters look like at runtime, or to capture live data from running services without redeploying.
- Reads credentials
- Installs packages
1 other project uses a version of this.
Trending
More talk lately.about the whole repository
Most recently taken up by
- datadog-labs/pupword for word, first seen Oct 8, 2026
Who's talking about DataDog/pup
- A Hacker News story“Pup – Datadog CLI”Hacker News · Feb 10, 2026 · 4 points
- DataDog/terraform-provider-datadog“[datadog_provider] Add use_pup to authenticate with a pup login”GitHub · Nov 12, 2026 · 2 reactions
- DataDog/terraform-provider-datadog“[datadog_provider] Add bearer_token_command to refresh Bearer tokens from a command”GitHub · Oct 20, 2026 · 1 reactions
- datadog-labs/homebrew-pack“feat(policy): add trust policy for pup release workflow”GitHub · Feb 10, 2026 · 1 reactions
- Groupe-Hevea/tools-aquaproj“chore(deps): update dependency datadog-labs/pup to v2.4.5”GitHub · Nov 15, 2026
The biggest 5 of 50 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 50
Talked about on GitHub and Hacker News (50 times).
On GitHub · 49
- Nov 12, 2026[datadog_provider] Add use_pup to authenticate with a pup login — DataDog/terraform-provider-datadog2 reactions · 2 comments
- Oct 20, 2026[datadog_provider] Add bearer_token_command to refresh Bearer tokens from a command — DataDog/terraform-provider-datadog1 reaction · 3 comments
- Feb 10, 2026feat(policy): add trust policy for pup release workflow — datadog-labs/homebrew-pack1 reaction · 2 comments
- Nov 15, 2026chore(deps): update dependency datadog-labs/pup to v2.4.5 — Groupe-Hevea/tools-aquaproj0 reactions · 1 comment
- Nov 14, 2026chore(deps): update dependency datadog-labs/pup to v2.4.4 — Groupe-Hevea/tools-aquaproj0 reactions · 1 comment
44 more on GitHub
- Nov 14, 2026chore(deps): update dependency datadog-labs/pup to v2.4.7 — mikutas/dotfiles0 reactions
- Nov 13, 2026chore(deps): update dependency datadog-labs/pup to v2.4.6 — mikutas/dotfiles0 reactions
- Nov 13, 2026chore(deps): update dependency datadog-labs/pup to v2.4.5 — mikutas/dotfiles0 reactions
- Nov 12, 2026chore(deps): update dependency datadog/pup to v2.4.7 — MichielMak/docker-stacks0 reactions · 1 comment
- Nov 12, 2026chore(deps): update dependency github:datadog/pup to v2.4.7 — JP-Ellis/dotfiles0 reactions
- Nov 11, 2026chore(deps): update dependency datadog/pup to v2.4.5 — MichielMak/docker-stacks0 reactions · 1 comment
- Nov 11, 2026Update dependency github:DataDog/pup to v2.4.2 — BarryThePenguin/dotfiles0 reactions
- Nov 10, 2026chore(deps): update dependency datadog-labs/pup to v2.4.3 — Groupe-Hevea/tools-aquaproj0 reactions · 1 comment
- Nov 10, 2026chore(deps): update all non-major dependencies — tak848/dotfiles0 reactions · 2 comments
- Nov 10, 2026chore(deps): update dependency github:datadog/pup to v2.4.4 — JP-Ellis/dotfiles0 reactions
- Nov 10, 2026chore(deps): update dependency datadog/pup to v2.4.3 — MichielMak/docker-stacks0 reactions · 1 comment
- Nov 8, 2026chore(deps): update dependency datadog-labs/pup to v2.4.2 — mikutas/dotfiles0 reactions
- Nov 7, 2026chore(deps): update dependency github:datadog/pup to v2.4.2 — JP-Ellis/dotfiles0 reactions
- Nov 7, 2026chore(deps): update dependency datadog/pup to v2.4.2 — MichielMak/docker-stacks0 reactions · 1 comment
- Nov 6, 2026chore(deps): update dependency datadog-labs/pup to v2.4.1 — Groupe-Hevea/tools-aquaproj0 reactions · 1 comment
- Nov 6, 2026chore(deps): update dependency datadog-labs/pup to v2.4.1 — mikutas/dotfiles0 reactions
- Nov 6, 2026Update dependency github:DataDog/pup to v2.3.10 — BarryThePenguin/dotfiles0 reactions
- Nov 6, 2026Update dependency github:DataDog/pup to v2.3.8 — BarryThePenguin/dotfiles0 reactions
- Nov 6, 2026Update dependency github:DataDog/pup to v2.3.7 — BarryThePenguin/dotfiles0 reactions
- Nov 5, 2026Update dependency github:DataDog/pup to v2.3.6 — BarryThePenguin/dotfiles0 reactions
- Nov 4, 2026Update dependency github:DataDog/pup to v2.3.5 — BarryThePenguin/dotfiles0 reactions
- Nov 3, 2026chore(deps): update dependency datadog/pup to v2.4.1 — MichielMak/docker-stacks0 reactions · 1 comment
- Nov 3, 2026Update dependency github:DataDog/pup to v2.3.4 — BarryThePenguin/dotfiles0 reactions
- Nov 3, 2026chore(deps): update dependency github:datadog/pup to v2.4.1 — JP-Ellis/dotfiles0 reactions
- Nov 3, 2026chore(deps): update dependency datadog/pup to v2.4.0 — MichielMak/docker-stacks0 reactions · 1 comment
- Nov 3, 2026chore(deps): update dependency datadog-labs/pup to v2.3.10 — Groupe-Hevea/tools-aquaproj0 reactions · 1 comment
- Nov 3, 2026Update dependency github:DataDog/pup to v2.3.3 — BarryThePenguin/dotfiles0 reactions
- Nov 2, 2026Update dependency github:DataDog/pup to v2 — BarryThePenguin/dotfiles0 reactions
- Nov 2, 2026Update dependency github:DataDog/pup to v1.27.1 — BarryThePenguin/dotfiles0 reactions
- Nov 1, 2026chore(deps): update dependency datadog-labs/pup to v2.3.8 — Groupe-Hevea/tools-aquaproj0 reactions · 1 comment
- Oct 31, 2026chore(deps): update dependency datadog-labs/pup to v2.3.10 — mikutas/dotfiles0 reactions
- Oct 30, 2026chore(deps): update dependency datadog-labs/pup to v2.3.5 — Groupe-Hevea/tools-aquaproj0 reactions · 1 comment
- Oct 30, 2026chore(deps): update dependency github:datadog/pup to v2.3.10 — JP-Ellis/dotfiles0 reactions
- Oct 30, 2026chore(deps): update dependency datadog-labs/pup to v2.3.6 — mikutas/dotfiles0 reactions
- Oct 30, 2026chore(deps): update dependency datadog/pup to v2.3.10 — MichielMak/docker-stacks0 reactions · 1 comment
- Oct 30, 2026chore(deps): update dependency datadog-labs/pup to v2.3.3 — Groupe-Hevea/tools-aquaproj0 reactions · 1 comment
- Oct 29, 2026chore(deps): update dependency datadog/pup to v2.3.6 — MichielMak/docker-stacks0 reactions · 1 comment
- Oct 29, 2026chore(deps): update dependency github:datadog/pup to v2.3.8 — JP-Ellis/dotfiles0 reactions
- Oct 26, 2026chore(deps): update dependency datadog/pup to v2.3.3 — MichielMak/docker-stacks0 reactions · 1 comment
- Oct 26, 2026chore(deps): update dependency github:datadog/pup to v2.3.5 — JP-Ellis/dotfiles0 reactions
- Sep 21, 2026[Plugin]: pup — using-system/otelyssey0 reactions · 6 comments
- Aug 23, 2026Add dsf WASM apps, named-sandbox connect, and TensorLake tool_runner door — rita-aga/temper0 reactions
- Jul 15, 2026Is a CLI in the roadmap? — incident-io/sdk-go0 reactions · 4 comments
- Jun 23, 2026Datadog, 'Pup' 오픈소스 공개 — 33개 Datadog 제품 200여 개 명령어를 AI 에이전트가 직접 호출 가능한 CLI로 제공 — roomedia/ax-trend0 reactions
On Hacker News · 1
- Feb 10, 2026Pup – Datadog CLI4 points
Other versions1 project uses a version of this.
Word for word · 1
- datadog-labs/pup★ 1k100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository13 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- pupSkill
- dd-apmSkill
- dd-code-generationSkill
- dd-docsSkill
- dd-file-issueSkill
- dd-idpSkill
- dd-logsSkill
- dd-monitorsSkill
- dd-pupSkill
- dd-symdbSkill
- dd-triage-flaky-testSkill
- dd-unblock-prSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 2 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Place log probes on running services without redeploying.
- Distinctive: line 41
If you don't know the service, ask the user before proceeding.
- Very specific: line 180
Use bare --capture (no value) only when you don't know which fields to inspect:
- Very specific: line 252
Default --from is now — only shows new events going forward
- Very specific: line 253
Use --from 5m or --from 1h to include recent historical events
- Very specific: line 256
Use --wait <seconds> to retry probe existence check (handles create → watch pipeline).
- Very specific: line 275
When using the default output (no --fields), the debugger payload is at the top level.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Datadog Live Debugger
Place log probes on running services without redeploying. Create probes with custom templates and conditions, and stream captured events in real time.
Prerequisites
pup must be installed:
brew tap datadog-labs/pack && brew install pupAuthentication
Authenticate via OAuth2 (recommended) or API keys:
# OAuth2 (recommended)
pup auth login
# Or use API keys
export DD_API_KEY="key" DD_APP_KEY="key" DD_SITE="datadoghq.com"Typical Workflow
Prefer --capture expressions over full snapshots. Capture expressions are lighter-weight, faster, and return exactly the data you need.
- If you don't know the service, ask the user before proceeding.
- Verify the service using
pup debugger context <service>to list environments with active instances. If multiple environments exist, ask the user which one to target before proceeding. - Find a method using the
dd-symdbskill (pup symdb search --view probe-locations) - Place a probe with capture expressions for the values you need
- Watch events with
--fieldsfor compact output - Delete the probe when done
# 0. List environments (if multiple, ask user which to use)
pup debugger context my-service --fields service,language,envs
# 1. Create a probe with capture expressions (recommended)
# Use --fields id to get just the probe ID back
pup debugger probes create \
--service my-service \
--env production \
--probe-location "com.example.MyController:handleRequest" \
--capture "request.id" \
--capture "request.headers" \
--ttl 1h \
--fields id
# 2. Stream events with compact output
pup debugger probes watch <PROBE_ID> --timeout 60 --limit 10 \
--fields "message,captures,timestamp"
# 3. Clean up
pup debugger probes delete <PROBE_ID>Service Context
Always run this before creating probes. It returns JSON by default (like all other commands) showing environments with active instances, tracer versions, and supported probe features. If the service runs in multiple environments, ask the user which one to target — don't guess.
# Full JSON output (default)
pup debugger context my-service
# Compact: just the fields you need
pup debugger context my-service --fields service,language,envs
# Filter to a specific environment
pup debugger context my-service --env production --fields service,envs,repo| Flag | Description | Default |
--env | Filter to a specific environment | All environments |
--fields | Comma-separated fields: service, language, envs, repo | Full JSON response |
Probe Management
List Probes
# All probes
pup debugger probes list
# Filter by service
pup debugger probes list --service my-serviceGet Probe Details
pup debugger probes get <PROBE_ID>Create a Log Probe
pup debugger probes create \
--service my-service \
--env staging \
--probe-location "com.example.MyClass:myMethod" \
--capture "user.name" \
--capture "order.items[0].price"To disambiguate overloaded methods, pass a signature with argument types:
pup debugger probes create \
--service my-service \
--env staging \
--probe-location "com.example.MyClass:myMethod(int, java.lang.String)" \
--capture "user.name"Options:
| Flag | Description | Default |
--service | Service name (required) | — |
--env | Environment (required) | — |
--probe-location | TYPE:METHOD or TYPE:METHOD(args) (required). The signature form disambiguates overloaded methods. | — |
--language | java, python, dotnet, go | Auto-detected from symdb |
--capture EXPR | Capture expression (repeatable). Use dot notation for fields, brackets for indexing. | None |
--capture | Without value: enable full snapshot (capture everything). | No snapshot |
--template | Log message template with {variable} placeholders. Can combine with --capture. | Auto-generated |
--condition | DSL condition to filter captures | None |
--depth | How deep the tracer traverses the object graph when capturing (1–5). Start at 1 to see field names/types, increase to drill in. | 1 |
--rate | Snapshots per second | 1 |
--budget | Max probe hits. Only "total" window supported (hourly/daily not yet available). | 1000 |
--ttl | Probe time-to-live (e.g., 10m, 1h, 24h). Probe auto-expires. | 1h |
Capture Expressions (Recommended)
Always prefer capture expressions over full snapshots. They are lighter-weight and return exactly the data you need.
# Capture specific fields using dot notation
--capture "user.name"
--capture "request.headers"
# Access array elements
--capture "orders[0].total"
--capture "items[len(items)].name"
# Chain member access
--capture "response.body.data.id"Multiple --capture flags can be combined. Each expression is independently evaluated.
# Capture multiple specific values
pup debugger probes create \
--service my-service --env prod \
--probe-location "OrderService:processOrder" \
--capture "order.id" \
--capture "order.items[0].price" \
--capture "customer.email"Tip: Start with
--depth 1(the default) to see field names and types, then increase depth to drill into interesting subtrees. Use--depth 5for deeply nested objects.
Full Snapshot (use sparingly)
Use bare --capture (no value) only when you don't know which fields to inspect:
# Full snapshot — captures all arguments, locals, return value
pup debugger probes create \
--service my-service --env staging \
--probe-location "com.example.MyClass:myMethod" \
--captureYou can combine snapshot with capture expressions:
# Full snapshot + specific expressions
--capture --capture "user.name"Templates
Templates can be used alongside capture expressions for custom log messages:
# Template with capture expressions
pup debugger probes create \
--service my-service --env prod \
--probe-location "MyClass:myMethod" \
--capture "user.id" \
--template "Processing request for user={user.id}, took {@duration}ms"Template syntax uses {variable} placeholders:
--template "Processing order={orderId} for user={userId}"
--template "handleRequest took {@duration}ms"Conditions filter when the probe fires:
--condition "status == 'error'"
--condition "@duration > 100"Delete a Probe
pup debugger probes delete <PROBE_ID>Watch Probe Events
Stream log events and status errors from a probe in real time.
pup debugger probes watch <PROBE_ID>Options:
| Flag | Description | Default |
--timeout | Exit after N seconds | 120 |
--limit | Exit after N log events | unlimited |
--from | Start time for log query | now |
--wait | Wait up to N seconds for the probe to become available | 0 |
--fields | Comma-separated fields to include: message, captures, timestamp. Compact JSON output. | Full debugger payload |
Behavior:
- Without
--fields: outputs the trimmed debugger payload (snapshot, probe info, stack) — not the full log envelope - With
--fields: outputs only the requested fields as compact JSON per event - Polls for new log events and probe status errors every 1s
- Default
--fromisnow— only shows new events going forward - Use
--from 5mor--from 1hto include recent historical events - Probe status errors (e.g., instrumentation failures) go to stderr
- Exit code 0 if events received, 1 if timed out with no events
- Use
--wait <seconds>to retry probe existence check (handles create → watch pipeline); default is 0 (fail immediately if not found)
Using --fields for compact output
For most agent use cases, --fields gives you exactly what you need without jq:
# Message + captures + timestamp (most common)
pup debugger probes watch <ID> --fields "message,captures,timestamp" --limit 5
# Template message only (one line per event)
pup debugger probes watch <ID> --fields "message" --limit 10
# Just captures (expression values or snapshot data)
pup debugger probes watch <ID> --fields "captures" --limit 1Extracting fields with jq (reference)
When using the default output (no --fields), the debugger payload is at the top level. Common jq patterns:
# Extract a specific captured expression
pup debugger probes watch <ID> --limit 1 \
| jq '.snapshot.captures.return.captureExpressions'
# Get captured argument values
pup debugger probes watch <ID> --limit 1 \
| jq '.snapshot.captures.return.arguments'Default output structure (trimmed to debugger payload):
.snapshot.captures.return.arguments → method arguments
.snapshot.captures.return.locals → local variables
.snapshot.captures.return.captureExpressions → capture expression values
.snapshot.probe.id → probe ID
.snapshot.probe.location → source locationSupported Languages
| Language | --language value |
| Java | java |
| Python | python |
| .NET | dotnet |
Failure Handling
| Problem | Fix |
| Wrong env / no instances | Use pup debugger context <service> to list valid environments |
| "probe not found" | Use --wait <seconds> to retry, e.g. pup debugger probes watch <ID> --wait 10 |
| No events appearing | Check --from (default is now); probe may need time to instrument |
| Instrumentation errors | Check stderr output from watch for status errors |
| Auth error | Run pup auth login or set DD_API_KEY + DD_APP_KEY + DD_SITE |
| Wrong method signature | Use the dd-symdb skill to find exact TYPE:METHOD or TYPE:METHOD(args) values |
References
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

