Use Sentry with NimbleBrain.
Connect Sentry and just ask — no workflow to build. Errors, performance, and release tracking. The agent gets 14 actions, running under your own credentials.
Everything the agent can do in Sentry
Errors, performance and releases, so the question after a deploy is one the agent can answer rather than one somebody goes looking for. An error-tracking surface that lags the product it tracks is worse than no surface at all, which is why this one is Sentry’s own.
14 actions
- Get organization issue details
- Delete organization issue
- Get project events
- Fetch issue event by id
- Access project information
- Create release for organization
- Get organization release version
- Create release deploy for org
- Create organization alert rule
- Fetch organization alert rules
- Create organization monitor
- Get organization environments
- Get organization stats summary
- Get organization sessions
Nobody types an action name
You ask. The agent works out which of its actions that takes, and in what order.
What broke after the deploy this morning?
Calling 1 action in Sentry
- Create release deploy for org
- Working
Which error is hitting the most users right now?
Calling 3 actions in Sentry
- Get organization issue details
- Delete organization issue
- Get project events
- Working
Summarise this issue and tell me where it comes from.
Calling 3 actions in Sentry
- Get organization issue details
- Delete organization issue
- Fetch issue event by id
- Working
Three steps, and Sentry is reachable.
-
Install it
Find Sentry in the directory inside your workspace and install it. No adapter for us to build first, no queue to join.
-
Connect the account
Sign in at the vendor, or hand an admin credential over once. Tokens stay with the workspace or the person who owns them — never pooled, never copied to us.
-
Ask for the work
The tools show up in front of the agent, under the same access wall as everything else. Describe the job in plain language, or put it on a schedule.
