Skip to main content
Connect Sentry to give your agents visibility into application errors and exceptions.

​
Capabilities

CapabilitySupported
Knowledge Source✓ Search errors for context
Deployment Trigger✗
Tool Actions✗

​
Setup

​
Connect via OAuth

  1. Go to Settings → Connections in Duckie
  2. Find Sentry and click Connect
  3. You’ll be redirected to Sentry
  4. Select the organization to connect
  5. Grant Duckie read access
  6. You’ll be redirected back to Duckie
Duckie requests read-only access to projects and events.

​
Using as Knowledge Source

Once connected, Duckie can search Sentry for relevant errors:
  1. Go to Train → Knowledge
  2. Click Add Source
  3. Select Sentry
  4. Choose which projects to index
  5. Click Start Sync

​
What Gets Indexed

  • Error messages and stack traces
  • Error frequency and trends
  • Affected users count
  • First/last seen timestamps
  • Tags and metadata

​
How Agents Use Sentry Data

When customers report issues, agents can:
  1. Search for related errors — Find if there’s a known bug
  2. Check error status — See if it’s resolved or ongoing
  3. Get context — Understand the technical details
  4. Estimate impact — See how many users are affected

​
Example Workflow

In a runbook: 
When a customer reports a technical issue:
1. Search Sentry for errors matching their description
2. If found:
   - Acknowledge the known issue
   - Share expected resolution timeline
   - Offer workaround if available
3. If not found:
   - Collect reproduction steps
   - Escalate to engineering

​
Best Practices

​
Index Production Projects

Focus on production environments:
  • Customer-facing errors
  • Backend services
  • API errors

​
Use Sentry Tags

Well-tagged errors are easier to search:
  • User ID
  • Feature area
  • Error category

​
Combine with Issue Tracking

Link Sentry errors to Jira/Linear issues:
  • Agents can reference the tracking ticket
  • Provide status updates to customers

​
Use Cases

​
Technical Support

Help support agents understand customer-reported bugs:
  • Verify if error is known
  • Get technical context
  • Estimate resolution

​
Proactive Communication

Identify affected users for proactive outreach:
  • Major outages
  • Widespread bugs

​
Troubleshooting

​
”Cannot access Sentry”

  • Re-authenticate the connection
  • Verify your Sentry account has project access
  • Check organization permissions

​
”Errors not syncing”

  • Verify the project is selected
  • Check that there are recent events
  • Force a sync refresh