sentry-automation

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Sentry Automation via Rube MCP

通过Rube MCP实现Sentry自动化

Automate Sentry error tracking and monitoring operations through Composio's Sentry toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/sentry

通过Composio的Sentry工具包，借助Rube MCP自动化Sentry错误追踪与监控操作。

工具包文档：composio.dev/toolkits/sentry

Prerequisites

前置条件

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Sentry connection via
```
RUBE_MANAGE_CONNECTIONS
```
with toolkit
```
sentry
```
Always call
```
RUBE_SEARCH_TOOLS
```
first to get current tool schemas

必须已连接Rube MCP（需具备RUBE_SEARCH_TOOLS权限）
通过
```
RUBE_MANAGE_CONNECTIONS
```
激活Sentry连接，工具包为
```
sentry
```
请始终先调用
```
RUBE_SEARCH_TOOLS
```
获取最新的工具架构

Setup

设置步骤

Get Rube MCP: Add

https://rube.app/mcp

as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

Verify Rube MCP is available by confirming
```
RUBE_SEARCH_TOOLS
```
responds
Call
```
RUBE_MANAGE_CONNECTIONS
```
with toolkit
```
sentry
```
If connection is not ACTIVE, follow the returned auth link to complete Sentry OAuth
Confirm connection status shows ACTIVE before running any workflows

获取Rube MCP：在客户端配置中添加

https://rube.app/mcp

作为MCP服务器。无需API密钥——只需添加端点即可使用。

确认
```
RUBE_SEARCH_TOOLS
```
可响应，以此验证Rube MCP是否可用
调用
```
RUBE_MANAGE_CONNECTIONS
```
并指定工具包
```
sentry
```
如果连接未处于ACTIVE状态，请按照返回的授权链接完成Sentry OAuth认证
在运行任何工作流之前，确认连接状态显示为ACTIVE

Core Workflows

核心工作流

1. Investigate Issues

1. 问题排查

When to use: User wants to find, inspect, or triage error issues

Tool sequence:

```
SENTRY_LIST_AN_ORGANIZATIONS_ISSUES
```
- List issues across the organization [Required]
```
SENTRY_GET_ORGANIZATION_ISSUE_DETAILS
```
- Get detailed info on a specific issue [Optional]
```
SENTRY_LIST_AN_ISSUES_EVENTS
```
- View individual error events for an issue [Optional]
```
SENTRY_RETRIEVE_AN_ISSUE_EVENT
```
- Get full event details with stack trace [Optional]
```
SENTRY_RETRIEVE_ISSUE_TAG_DETAILS
```
- Inspect tag distribution for an issue [Optional]

Key parameters:

```
organization_id_or_slug
```
: Organization identifier
```
issue_id
```
: Numeric issue ID

query

: Search query (e.g.,

is:unresolved

assigned:me

browser:Chrome

)

```
sort
```
: Sort order (
```
date
```
,
```
new
```
,
```
freq
```
,
```
priority
```
)
```
statsPeriod
```
: Time window for stats (
```
24h
```
,
```
14d
```
, etc.)

Pitfalls:

```
organization_id_or_slug
```
is the org slug (e.g., 'my-org'), not the display name
Issue IDs are numeric; do not confuse with event IDs which are UUIDs
Query syntax uses Sentry's search format:
```
is:unresolved
```
,
```
assigned:me
```
,
```
!has:release
```
Events within an issue can have different stack traces; inspect individual events for details

适用场景：用户想要查找、检查或分类错误问题

工具调用序列:

```
SENTRY_LIST_AN_ORGANIZATIONS_ISSUES
```
- 列出组织内的所有问题 [必填]
```
SENTRY_GET_ORGANIZATION_ISSUE_DETAILS
```
- 获取特定问题的详细信息 [可选]
```
SENTRY_LIST_AN_ISSUES_EVENTS
```
- 查看某一问题的单个错误事件 [可选]
```
SENTRY_RETRIEVE_AN_ISSUE_EVENT
```
- 获取包含堆栈跟踪的完整事件详情 [可选]
```
SENTRY_RETRIEVE_ISSUE_TAG_DETAILS
```
- 检查问题的标签分布情况 [可选]

关键参数:

```
organization_id_or_slug
```
: 组织标识符
```
issue_id
```
: 数字格式的问题ID

query

: 搜索查询语句（例如：

is:unresolved

assigned:me

browser:Chrome

）

```
sort
```
: 排序方式 (
```
date
```
,
```
new
```
,
```
freq
```
,
```
priority
```
)
```
statsPeriod
```
: 统计时间窗口（
```
24h
```
,
```
14d
```
等）

注意事项:

```
organization_id_or_slug
```
是组织的slug（例如'my-org'），而非显示名称
问题ID为数字格式；请勿与UUID格式的事件ID混淆
查询语法需使用Sentry的搜索格式：
```
is:unresolved
```
,
```
assigned:me
```
,
```
!has:release
```
同一问题下的事件可能具有不同的堆栈跟踪；需查看单个事件以获取详细信息

2. Manage Project Issues

2. 项目问题管理

When to use: User wants to view issues scoped to a specific project

Tool sequence:

```
SENTRY_RETRIEVE_ORGANIZATION_PROJECTS
```
- List projects to find project slug [Prerequisite]
```
SENTRY_RETRIEVE_PROJECT_ISSUES_LIST
```
- List issues for a specific project [Required]
```
SENTRY_RETRIEVE_ISSUE_EVENTS_BY_ID
```
- Get events for a specific issue [Optional]

Key parameters:

```
organization_id_or_slug
```
: Organization identifier
```
project_id_or_slug
```
: Project identifier
```
query
```
: Search filter string
```
statsPeriod
```
: Stats time window

Pitfalls:

Project slugs are different from project display names
Always resolve project names to slugs via RETRIEVE_ORGANIZATION_PROJECTS first
Project-scoped issue lists may have different pagination than org-scoped lists

适用场景：用户想要查看特定项目范围内的问题

工具调用序列:

```
SENTRY_RETRIEVE_ORGANIZATION_PROJECTS
```
- 列出项目以获取项目slug [前置步骤]
```
SENTRY_RETRIEVE_PROJECT_ISSUES_LIST
```
- 列出特定项目的问题 [必填]
```
SENTRY_RETRIEVE_ISSUE_EVENTS_BY_ID
```
- 获取特定问题的事件 [可选]

关键参数:

```
organization_id_or_slug
```
: 组织标识符
```
project_id_or_slug
```
: 项目标识符
```
query
```
: 搜索过滤字符串
```
statsPeriod
```
: 统计时间窗口

注意事项:

项目slug与项目显示名称不同
请始终先通过RETRIEVE_ORGANIZATION_PROJECTS将项目名称转换为slug
项目范围的问题列表分页规则可能与组织范围的不同

3. Configure Alert Rules

3. 告警规则配置

When to use: User wants to create or manage alert rules for a project

Tool sequence:

```
SENTRY_RETRIEVE_ORGANIZATION_PROJECTS
```
- Find project for the alert [Prerequisite]

SENTRY_RETRIEVE_PROJECT_RULES_BY_ORG_AND_PROJECT_ID

- List existing rules [Optional]

```
SENTRY_CREATE_PROJECT_RULE_FOR_ALERTS
```
- Create a new alert rule [Required]
```
SENTRY_CREATE_ORGANIZATION_ALERT_RULE
```
- Create org-level metric alert [Alternative]
```
SENTRY_UPDATE_ORGANIZATION_ALERT_RULES
```
- Update existing alert rules [Optional]
```
SENTRY_RETRIEVE_ALERT_RULE_DETAILS
```
- Inspect specific alert rule [Optional]
```
SENTRY_GET_PROJECT_RULE_DETAILS
```
- Get project-level rule details [Optional]

Key parameters:

```
name
```
: Alert rule name
```
conditions
```
: Array of trigger conditions
```
actions
```
: Array of actions to perform when triggered
```
filters
```
: Array of event filters
```
frequency
```
: How often to trigger (in minutes)
```
actionMatch
```
: 'all', 'any', or 'none' for condition matching

Pitfalls:

Project-level rules (CREATE_PROJECT_RULE) and org-level metric alerts (CREATE_ORGANIZATION_ALERT_RULE) are different
Conditions, actions, and filters use specific JSON schemas; check Sentry docs for valid types
```
frequency
```
is in minutes; setting too low causes alert fatigue
```
actionMatch
```
defaults may vary; explicitly set to avoid unexpected behavior

适用场景：用户想要为项目创建或管理告警规则

工具调用序列:

```
SENTRY_RETRIEVE_ORGANIZATION_PROJECTS
```
- 找到告警所属的项目 [前置步骤]

SENTRY_RETRIEVE_PROJECT_RULES_BY_ORG_AND_PROJECT_ID

- 列出现有规则 [可选]

```
SENTRY_CREATE_PROJECT_RULE_FOR_ALERTS
```
- 创建新的告警规则 [必填]
```
SENTRY_CREATE_ORGANIZATION_ALERT_RULE
```
- 创建组织级别的指标告警 [替代方案]
```
SENTRY_UPDATE_ORGANIZATION_ALERT_RULES
```
- 更新现有告警规则 [可选]
```
SENTRY_RETRIEVE_ALERT_RULE_DETAILS
```
- 检查特定告警规则 [可选]
```
SENTRY_GET_PROJECT_RULE_DETAILS
```
- 获取项目级规则详情 [可选]

关键参数:

```
name
```
: 告警规则名称
```
conditions
```
: 触发条件数组
```
actions
```
: 触发时执行的操作数组
```
filters
```
: 事件过滤条件数组
```
frequency
```
: 触发频率（以分钟为单位）
```
actionMatch
```
: 条件匹配方式（'all'、'any'或'none'）

注意事项:

项目级规则（CREATE_PROJECT_RULE）与组织级指标告警（CREATE_ORGANIZATION_ALERT_RULE）是不同的
条件、操作和过滤条件使用特定的JSON架构；请查看Sentry文档获取有效类型
```
frequency
```
以分钟为单位；设置过低会导致告警疲劳
```
actionMatch
```
的默认值可能不同；请显式设置以避免意外行为

4. Manage Releases

4. 版本发布管理

When to use: User wants to create, track, or manage release versions

Tool sequence:

```
SENTRY_LIST_ORGANIZATION_RELEASES
```
- List existing releases [Optional]
```
SENTRY_CREATE_RELEASE_FOR_ORGANIZATION
```
- Create a new release [Required]

SENTRY_UPDATE_RELEASE_DETAILS_FOR_ORGANIZATION

- Update release metadata [Optional]

```
SENTRY_CREATE_RELEASE_DEPLOY_FOR_ORG
```
- Record a deployment for a release [Optional]

SENTRY_UPLOAD_RELEASE_FILE_TO_ORGANIZATION

- Upload source maps or files [Optional]

Key parameters:

```
version
```
: Release version string (e.g., '1.0.0', commit SHA)
```
projects
```
: Array of project slugs this release belongs to
```
dateReleased
```
: Release timestamp (ISO 8601)
```
environment
```
: Deployment environment name (e.g., 'production', 'staging')

Pitfalls:

Release versions must be unique within an organization
Releases can span multiple projects; use the
```
projects
```
array
Deploying a release is separate from creating it; use CREATE_RELEASE_DEPLOY
Source map uploads require the release to exist first

适用场景：用户想要创建、跟踪或管理版本发布

工具调用序列:

```
SENTRY_LIST_ORGANIZATION_RELEASES
```
- 列出现有版本 [可选]
```
SENTRY_CREATE_RELEASE_FOR_ORGANIZATION
```
- 创建新版本 [必填]

SENTRY_UPDATE_RELEASE_DETAILS_FOR_ORGANIZATION

- 更新版本元数据 [可选]

```
SENTRY_CREATE_RELEASE_DEPLOY_FOR_ORG
```
- 记录版本的部署信息 [可选]

SENTRY_UPLOAD_RELEASE_FILE_TO_ORGANIZATION

- 上传源映射或文件 [可选]

关键参数:

```
version
```
: 版本字符串（例如'1.0.0'、提交SHA值）
```
projects
```
: 此版本所属的项目slug数组
```
dateReleased
```
: 版本发布时间戳（ISO 8601格式）
```
environment
```
: 部署环境名称（例如'production'、'staging'）

注意事项:

版本号在组织内必须唯一
一个版本可覆盖多个项目；请使用
```
projects
```
数组指定
部署版本与创建版本是分开的操作；请使用CREATE_RELEASE_DEPLOY完成部署
上传源映射文件前需确保版本已存在

5. Monitor Organization and Teams

5. 组织与团队监控

When to use: User wants to view org structure, teams, or member lists

Tool sequence:

SENTRY_GET_ORGANIZATION_DETAILS

SENTRY_GET_ORGANIZATION_BY_ID_OR_SLUG

- Get org info [Required]

```
SENTRY_LIST_TEAMS_IN_ORGANIZATION
```
- List all teams [Optional]
```
SENTRY_LIST_ORGANIZATION_MEMBERS
```
- List org members [Optional]
```
SENTRY_GET_PROJECT_LIST
```
- List all accessible projects [Optional]

Key parameters:

```
organization_id_or_slug
```
: Organization identifier
```
cursor
```
: Pagination cursor for large result sets

Pitfalls:

Organization slugs are URL-safe identifiers, not display names
Member lists may be paginated; follow cursor pagination
Team and member visibility depends on the authenticated user's permissions

适用场景：用户想要查看组织架构、团队或成员列表

工具调用序列:

SENTRY_GET_ORGANIZATION_DETAILS

或

SENTRY_GET_ORGANIZATION_BY_ID_OR_SLUG

- 获取组织信息 [必填]

```
SENTRY_LIST_TEAMS_IN_ORGANIZATION
```
- 列出所有团队 [可选]
```
SENTRY_LIST_ORGANIZATION_MEMBERS
```
- 列出组织成员 [可选]
```
SENTRY_GET_PROJECT_LIST
```
- 列出所有可访问的项目 [可选]

关键参数:

```
organization_id_or_slug
```
: 组织标识符
```
cursor
```
: 用于大数据集的分页游标

注意事项:

组织slug是URL安全的标识符，而非显示名称
成员列表可能会分页；请按照游标分页规则获取全部内容
团队和成员的可见性取决于当前认证用户的权限

6. Manage Monitors (Cron Monitoring)

6. 监控管理（定时任务监控）

When to use: User wants to update cron job monitoring configuration

Tool sequence:

```
SENTRY_UPDATE_A_MONITOR
```
- Update monitor configuration [Required]

Key parameters:

```
organization_id_or_slug
```
: Organization identifier
```
monitor_id_or_slug
```
: Monitor identifier
```
name
```
: Monitor display name
```
schedule
```
: Cron schedule expression or interval
```
checkin_margin
```
: Grace period in minutes for late check-ins
```
max_runtime
```
: Maximum expected runtime in minutes

Pitfalls:

Monitor slugs are auto-generated from the name; use slug for API calls
Schedule changes take effect immediately
Missing check-ins trigger alerts after the margin period

适用场景：用户想要更新定时任务监控配置

工具调用序列:

```
SENTRY_UPDATE_A_MONITOR
```
- 更新监控配置 [必填]

关键参数:

```
organization_id_or_slug
```
: 组织标识符
```
monitor_id_or_slug
```
: 监控标识符
```
name
```
: 监控显示名称
```
schedule
```
: Cron调度表达式或时间间隔
```
checkin_margin
```
: 延迟签到的宽限期（以分钟为单位）
```
max_runtime
```
: 预期的最大运行时长（以分钟为单位）

注意事项:

监控slug由名称自动生成；API调用时请使用slug
调度更改会立即生效
超过宽限期未签到会触发告警

Common Patterns

常见模式

ID Resolution

ID转换

Organization name -> Slug:

1. Call SENTRY_GET_ORGANIZATION_DETAILS
2. Extract slug field from response

Project name -> Slug:

1. Call SENTRY_RETRIEVE_ORGANIZATION_PROJECTS
2. Find project by name, extract slug

组织名称 -> Slug:

1. 调用SENTRY_GET_ORGANIZATION_DETAILS
2. 从响应中提取slug字段

项目名称 -> Slug:

1. 调用SENTRY_RETRIEVE_ORGANIZATION_PROJECTS
2. 根据名称找到项目，提取slug

Pagination

分页

Sentry uses cursor-based pagination with
```
Link
```
headers
Check response for cursor values
Pass cursor in next request until no more pages

Sentry使用基于游标的分页方式，通过
```
Link
```
头传递游标
检查响应中的游标值
在后续请求中传递游标，直到没有更多页面

Search Query Syntax

搜索查询语法

```
is:unresolved
```
- Unresolved issues
```
is:resolved
```
- Resolved issues
```
assigned:me
```
- Assigned to current user
```
assigned:team-slug
```
- Assigned to a team
```
!has:release
```
- Issues without a release
```
first-release:1.0.0
```
- Issues first seen in release
```
times-seen:>100
```
- Seen more than 100 times
```
browser:Chrome
```
- Filter by browser tag

```
is:unresolved
```
- 未解决的问题
```
is:resolved
```
- 已解决的问题
```
assigned:me
```
- 分配给当前用户的问题
```
assigned:team-slug
```
- 分配给指定团队的问题
```
!has:release
```
- 未关联版本的问题
```
first-release:1.0.0
```
- 首次出现在1.0.0版本中的问题
```
times-seen:>100
```
- 出现次数超过100次的问题
```
browser:Chrome
```
- 按浏览器标签过滤

Known Pitfalls

已知注意事项

ID Formats:

Organization: use slug (e.g., 'my-org'), not display name
Project: use slug (e.g., 'my-project'), not display name
Issue IDs: numeric integers
Event IDs: UUIDs (32-char hex strings)

Permissions:

API token scopes must match the operations being performed
Organization-level operations require org-level permissions
Project-level operations require project access

Rate Limits:

Sentry enforces per-organization rate limits
Implement backoff on 429 responses
Bulk operations should be staggered

ID格式:

组织：使用slug（例如'my-org'），而非显示名称
项目：使用slug（例如'my-project'），而非显示名称
问题ID：数字整数
事件ID：UUID（32位十六进制字符串）

权限:

API令牌的权限范围必须与执行的操作匹配
组织级操作需要组织级权限
项目级操作需要项目访问权限

速率限制:

Sentry对每个组织实施速率限制
收到429响应时请实现退避机制
批量操作应错开执行

Quick Reference

快速参考

Task	Tool Slug	Key Params
List org issues	SENTRY_LIST_AN_ORGANIZATIONS_ISSUES	organization_id_or_slug, query
Get issue details	SENTRY_GET_ORGANIZATION_ISSUE_DETAILS	organization_id_or_slug, issue_id
List issue events	SENTRY_LIST_AN_ISSUES_EVENTS	issue_id
Get event details	SENTRY_RETRIEVE_AN_ISSUE_EVENT	organization_id_or_slug, event_id
List project issues	SENTRY_RETRIEVE_PROJECT_ISSUES_LIST	organization_id_or_slug, project_id_or_slug
List projects	SENTRY_RETRIEVE_ORGANIZATION_PROJECTS	organization_id_or_slug
Get org details	SENTRY_GET_ORGANIZATION_DETAILS	organization_id_or_slug
List teams	SENTRY_LIST_TEAMS_IN_ORGANIZATION	organization_id_or_slug
List members	SENTRY_LIST_ORGANIZATION_MEMBERS	organization_id_or_slug
Create alert rule	SENTRY_CREATE_PROJECT_RULE_FOR_ALERTS	organization_id_or_slug, project_id_or_slug
Create metric alert	SENTRY_CREATE_ORGANIZATION_ALERT_RULE	organization_id_or_slug
Create release	SENTRY_CREATE_RELEASE_FOR_ORGANIZATION	organization_id_or_slug, version
Deploy release	SENTRY_CREATE_RELEASE_DEPLOY_FOR_ORG	organization_id_or_slug, version
List releases	SENTRY_LIST_ORGANIZATION_RELEASES	organization_id_or_slug
Update monitor	SENTRY_UPDATE_A_MONITOR	organization_id_or_slug, monitor_id_or_slug

Powered by Composio

任务	工具Slug	关键参数
列出组织问题	SENTRY_LIST_AN_ORGANIZATIONS_ISSUES	organization_id_or_slug, query
获取问题详情	SENTRY_GET_ORGANIZATION_ISSUE_DETAILS	organization_id_or_slug, issue_id
列出问题事件	SENTRY_LIST_AN_ISSUES_EVENTS	issue_id
获取事件详情	SENTRY_RETRIEVE_AN_ISSUE_EVENT	organization_id_or_slug, event_id
列出项目问题	SENTRY_RETRIEVE_PROJECT_ISSUES_LIST	organization_id_or_slug, project_id_or_slug
列出项目	SENTRY_RETRIEVE_ORGANIZATION_PROJECTS	organization_id_or_slug
获取组织详情	SENTRY_GET_ORGANIZATION_DETAILS	organization_id_or_slug
列出团队	SENTRY_LIST_TEAMS_IN_ORGANIZATION	organization_id_or_slug
列出成员	SENTRY_LIST_ORGANIZATION_MEMBERS	organization_id_or_slug
创建告警规则	SENTRY_CREATE_PROJECT_RULE_FOR_ALERTS	organization_id_or_slug, project_id_or_slug
创建指标告警	SENTRY_CREATE_ORGANIZATION_ALERT_RULE	organization_id_or_slug
创建版本	SENTRY_CREATE_RELEASE_FOR_ORGANIZATION	organization_id_or_slug, version
部署版本	SENTRY_CREATE_RELEASE_DEPLOY_FOR_ORG	organization_id_or_slug, version
列出版本	SENTRY_LIST_ORGANIZATION_RELEASES	organization_id_or_slug
更新监控	SENTRY_UPDATE_A_MONITOR	organization_id_or_slug, monitor_id_or_slug

由Composio提供支持