sentry

| Task | Command |

|------|---------|

| Find errors on a date | search-events.js --org X --start 2025-12-23T15:00:00 --level error |

| List open issues | list-issues.js --org X --status unresolved |

| Get issue details | fetch-issue.js --latest |

| Get event details | fetch-event.js --org X --project Y |

| Search logs | search-logs.js --org X --project Y "level:error" |

"What went wrong at this time?"

Find events around a specific timestamp:

```bash

# Find all events in a 2-hour window

./scripts/search-events.js --org myorg --project backend \

--start 2025-12-23T15:00:00 --end 2025-12-23T17:00:00

# Filter to just errors

./scripts/search-events.js --org myorg --start 2025-12-23T15:00:00 \

--level error

# Find a specific transaction type

./scripts/search-events.js --org myorg --start 2025-12-23T15:00:00 \

--transaction process-incoming-email

```

"What errors have occurred recently?"

```bash

# List unresolved errors from last 24 hours

./scripts/list-issues.js --org myorg --status unresolved --level error --period 24h

# Find high-frequency issues

./scripts/list-issues.js --org myorg --query "times_seen:>50" --sort freq

# Issues affecting users

./scripts/list-issues.js --org myorg --query "is:unresolved has:user" --sort user

```

"Get details about a specific issue/event"

```bash

# Get issue with latest stack trace

./scripts/fetch-issue.js 5765604106 --latest

./scripts/fetch-issue.js https://sentry.io/organizations/myorg/issues/123/ --latest

./scripts/fetch-issue.js MYPROJ-123 --org myorg --latest

# Get specific event with all breadcrumbs

./scripts/fetch-event.js abc123def456 --org myorg --project backend --breadcrumbs

```

"Find events with a specific tag"

```bash

# Find by custom tag (e.g., thread_id, user_id)

./scripts/search-events.js --org myorg --tag thread_id:th_abc123

# Find by user email

./scripts/search-events.js --org myorg --query "user.email:*@example.com"

```

---

```bash

./scripts/fetch-issue.js [options]

```

Get details about a specific issue (grouped error).

Accepts:

• Issue ID: 5765604106
• Issue URL: https://sentry.io/organizations/sentry/issues/5765604106/
• New URL format: https://myorg.sentry.io/issues/5765604106/
• Short ID: JAVASCRIPT-ABC (requires --org flag)

Options:

• --latest - Include the latest event with full stack trace
• --org - Organization slug (for short IDs)
• --json - Output raw JSON

Output includes:

• Title, culprit, status, level
• First/last seen timestamps
• Event count and user impact
• Tags and environment info
• With --latest: stack trace, request details, breadcrumbs, runtime context

---

```bash

./scripts/fetch-event.js --org --project [options]

```

Get full details of a specific event by its ID.

Options:

• --org, -o - Organization slug (required)
• --project, -p - Project slug (required)
• --breadcrumbs, -b - Show all breadcrumbs (default: last 30)
• --spans - Show span tree for transactions
• --json - Output raw JSON

Output includes:

• Timestamp, project, title, message
• All tags
• Context (runtime, browser, OS, trace info)
• Request details
• Exception with stack trace
• Breadcrumbs
• Spans (with --spans)

---

```bash

./scripts/search-events.js [options]

```

Search for events (transactions, errors) using Sentry Discover.

Time Range Options:

• --period, -t - Relative time (24h, 7d, 14d)
• --start - Start time (ISO 8601: 2025-12-23T15:00:00)
• --end - End time (ISO 8601)

Filter Options:

• --org, -o - Organization slug (required)
• --project, -p - Project slug or ID
• --query, -q - Discover search query
• --transaction - Transaction name filter
• --tag - Tag filter (repeatable)
• --level - Level filter (error, warning, info)
• --limit, -n - Max results (default: 25, max: 100)
• --fields - Comma-separated fields to include

Query Syntax:

```

transaction:process-* Wildcard transaction match

level:error Filter by level

user.email:foo@bar.com Filter by user

environment:production Filter by environment

has:stack.filename Has stack trace

```

---

```bash

./scripts/list-issues.js [options]

```

List and search issues (grouped errors) in a project.

Options:

• --org, -o - Organization slug (required)
• --project, -p - Project slug (repeatable)
• --query, -q - Issue search query
• --status - unresolved, resolved, ignored
• --level - error, warning, info, fatal
• --period, -t - Time period (default: 14d)
• --limit, -n - Max results (default: 25)
• --sort - date, new, priority, freq, user
• --json - Output raw JSON

Query Syntax:

```

is:unresolved Status filter

is:assigned Has assignee

assigned:me Assigned to current user

level:error Level filter

firstSeen:+7d First seen > 7 days ago

lastSeen:-24h Last seen within 24h

times_seen:>100 Event count filter

has:user Has user context

error.handled:0 Unhandled errors only

```

---

```bash

./scripts/search-logs.js [query|url] [options]

```

Search for logs in Sentry's Logs Explorer.

Options:

• --org, -o - Organization slug (required unless URL provided)
• --project, -p - Filter by project slug or ID
• --period, -t - Time period (default: 24h)
• --limit, -n - Max results (default: 100, max: 1000)
• --json - Output raw JSON

Query Syntax:

```

level:error Filter by level (trace, debug, info, warn, error, fatal)

message:timeout Search message text with wildcards

trace:abc123 Filter by trace ID

project:my-project Filter by project slug

```

Accepts Sentry URLs:

```bash

./scripts/search-logs.js "https://myorg.sentry.io/explore/logs/?project=123&statsPeriod=7d"

```

---

1. Start broad, then narrow down: Use search-events.js with a time range first, then drill into specific events

1. Use breadcrumbs: The --breadcrumbs flag on fetch-event.js shows the full history of what happened before an error

1. Look for patterns: Use list-issues.js --sort freq to find frequently occurring problems

1. Check related events: If you find one event, look for others with the same transaction name or trace ID

1. Tags are your friend: Custom tags like thread_id, user_id, request_id help correlate events