Sentry

Runs on its own 9

Looking things up, writing to Everdeck's own records and changes one step can undo. Once an agent's charter grants one of these, it runs without asking, unless you set it to Ask first in the charter or one of your approval rules covers it.

• List projects Tier 0 · Read Outside content

  List the organization's projects with id, slug, name and platform.

• Find issues Tier 0 · Read Outside content

  List the organization's issues with Sentry search syntax, for example "is:unresolved level:error", "is:unresolved assigned:me", "release:1.4.0 is:unresolved" or "is:unresolved firstSeen:-24h". Returns short id, title, culprit, level, status, priority, event and user counts, first and last seen, assignee and project. Sorted by last seen unless sort says otherwise.

• Look up an issue by short id Tier 0 · Read Outside content

  Turn a short id such as BACKEND-1A3 (as shown in Sentry, alerts and commit messages) into the issue id the other actions use.

• Read an issue Tier 0 · Read Outside content

  Read one issue: title, culprit, level, status and substatus, priority, event and user counts, first and last seen, first and last release, assignee, comment count and link.

• Read an issue's stack trace Tier 0 · Read Outside content

  Read one event of an issue, rendered as Markdown for reading: the exception and stack trace, breadcrumbs, request, tags and context. event_id may be latest, oldest, recommended (the most useful example) or a specific event id.

• See what an issue affects Tier 0 · Read Outside content

  Show how an issue's events spread over one tag: the top values with counts and when each was last seen. Useful keys include release, environment, browser, os, device, url, transaction, server_name and user.

• Resolve, archive, prioritise or assign an issue Tier 2 · Reversible Outside content

  Change an issue's state. Examples: resolve {"status": "resolved"}; resolve in the next release {"status": "resolvedInNextRelease"}; reopen {"status": "unresolved", "substatus": "ongoing"}; archive until it gets worse {"status": "ignored", "substatus": "archived_until_escalating"}; assign {"assignedTo": "[email protected]"} or {"assignedTo": "team:12"}; set priority {"priority": "high"}. Subscribers are notified.

• List releases Tier 0 · Read Outside content

  List releases, newest first, with version, when they were created and released, how many new issues each introduced, projects and last deploy.

• List members Tier 0 · Read Outside content

  List organization members with name, email, role and user id (use "user:<user id>" or the email to assign issues). Search with query, for example "email:[email protected]".