Skip to main content

​
sentry issue view

View detailed information about a Sentry issue by its ID or short ID. The latest event is automatically included for full context.

​
Usage

sentry issue view <issue-id>

​
Issue ID Formats

The view command accepts multiple issue identifier formats: 
# Explicit org + ID
sentry issue view sentry/EXTENSION-7
sentry issue view sentry/cli-G

# Project + suffix
sentry issue view cli-G
sentry issue view spotlight-electron-4Y

# Short ID (searches across orgs)
sentry issue view CLI-G

# Suffix only (requires DSN context)
sentry issue view G

# Numeric ID
sentry issue view 123456789

​
Multi-Project Mode

After running sentry issue list in a monorepo, you can use the alias-suffix format shown in the ALIAS column: 
# If list shows "e-7" in ALIAS column
sentry issue view e-7

​
Parameters

​
issue-id
string
required
Issue identifier in any supported format (see formats above).

​
Flags

​
--web
boolean
default:"false"
Open the issue in your default web browser instead of displaying in terminal.Alias: -wExample:
sentry issue view EXTENSION-7 -w
​
--spans
number
default:"3"
Maximum depth of span tree to display. Set to 0 or use --spans no to disable span tree display.Example:
# Show full span tree
sentry issue view CLI-G --spans 10

# Disable span tree
sentry issue view CLI-G --spans 0
sentry issue view CLI-G --spans no
​
--json
boolean
default:"false"
Output results as JSON including issue details, latest event, and span tree data.Example:
sentry issue view EXTENSION-7 --json

​
Examples

​
Basic Usage

# View issue by numeric ID
sentry issue view 123456789

# View issue by short ID
sentry issue view EXTENSION-7

# View with explicit org
sentry issue view sentry/CLI-G

​
Browser Integration

# Open issue in browser
sentry issue view EXTENSION-7 --web
sentry issue view CLI-G -w

​
Span Tree Control

# Show deeper span tree
sentry issue view CLI-G --spans 5

# Disable span tree for faster output
sentry issue view CLI-G --spans 0

​
JSON Output

# Export to JSON
sentry issue view EXTENSION-7 --json > issue-details.json

# Extract specific fields with jq
sentry issue view CLI-G --json | jq '.issue.title'
sentry issue view CLI-G --json | jq '.event.tags'

​
Sample Output

​
Human-Readable Format

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Issue: EXTENSION-7
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Title:       TypeError: Cannot read property 'map' of undefined
Project:     sentry/cli
Status:      unresolved
Level:       error
Culprit:     processData in app.js

Activity:
  First seen:  2024-03-01 10:30:00 UTC (4 days ago)
  Last seen:   2024-03-05 20:15:00 UTC (2 hours ago)
  Events:      142
  Users:       23

Link: https://sentry.io/organizations/sentry/issues/123456789/

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Latest Event
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Event ID:    a1b2c3d4e5f6g7h8i9j0
Timestamp:   2024-03-05 20:15:00 UTC
Environment: production
Release:     [email protected]

Tags:
  browser.name:     Chrome
  browser.version:  120.0.0
  os.name:          Mac OS X
  user.id:          user-456

Context:
  url:              https://app.example.com/dashboard
  transaction:      /dashboard
  
Replay: https://sentry.io/replays/xyz123/

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Span Tree (trace: abc123def456)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

▼ http.server GET /api/users                     1.2s
  ├─ db.query SELECT * FROM users                120ms
  ├─ http.client GET /external/api               850ms
  └─ render.template users.html                   45ms

Tip: Use 'sentry issue explain EXTENSION-7' for AI root cause analysis

​
JSON Format

{
  "issue": {
    "id": "123456789",
    "shortId": "EXTENSION-7",
    "title": "TypeError: Cannot read property 'map' of undefined",
    "culprit": "processData in app.js",
    "level": "error",
    "status": "unresolved",
    "count": "142",
    "userCount": 23,
    "firstSeen": "2024-03-01T10:30:00Z",
    "lastSeen": "2024-03-05T20:15:00Z",
    "permalink": "https://sentry.io/organizations/sentry/issues/123456789/",
    "project": {
      "slug": "cli",
      "name": "Sentry CLI"
    }
  },
  "event": {
    "id": "a1b2c3d4e5f6g7h8i9j0",
    "dateCreated": "2024-03-05T20:15:00Z",
    "platform": "javascript",
    "tags": [
      {"key": "browser.name", "value": "Chrome"},
      {"key": "browser.version", "value": "120.0.0"},
      {"key": "os.name", "value": "Mac OS X"},
      {"key": "user.id", "value": "user-456"}
    ],
    "context": {
      "url": "https://app.example.com/dashboard",
      "transaction": "/dashboard"
    }
  },
  "trace": {
    "traceId": "abc123def456",
    "spans": [
      {
        "span_id": "span1",
        "description": "GET /api/users",
        "op": "http.server",
        "start_timestamp": 1709667300.0,
        "timestamp": 1709667301.2
      }
    ]
  }
}

​
Notes

  • Organization context is required to fetch the latest event and span tree. If not provided explicitly, it’s resolved from DSN detection or project aliases.
  • The span tree shows the performance trace for the latest event, helping identify slow operations.
  • Use --spans 0 to disable span tree fetching for faster output when you only need issue metadata.
  • The -w flag is useful for quickly jumping to the Sentry web UI for more advanced investigation.

​
See Also

Build docs developers (and LLMs) love

Get started for freeTalk to us