Sentry plugin

Two-way Sentry integration: Sentry errors flow into the Mushi Mushi queue, and fixes flow back. Merging a fix resolves the linked Sentry issue, and resolving in Sentry resolves the linked report. With the webhook below that happens at once; with only the automatic import set up (no webhook), Mushi Mushi checks open reports’ Sentry issues every 15 minutes and closes the ones you resolved (by hand, or with a commit, pull request or release). Sentry’s own resolves leave the report open: auto-resolve by age and a metric alert that cleared mean the bug went quiet, not that it was fixed. So does an issue you archive (ignore). Reopening a report in Mushi Mushi reopens its Sentry issue too. The outbound plugin below also copies triaged Mushi Mushi reports into Sentry.

Route Sentry errors into Mushi Mushi (inbound)

No plugin needed. This is built into the hosted API:

1. In Sentry: Settings → Developer Settings → Custom Integrations → Create New Integration → Internal Integration. Set its webhook URL to the Receive URL shown on the Mushi Mushi Sentry card (<api>/v1/webhooks/sentry?projectId=<your-project-id>), subscribe to the issue resource, enable Alert Rule Action, and give it Issue & Event: Read & Write.
2. In the Mushi Mushi console, open Integrations → Sentry and paste the integration’s Client Secret as the Webhook secret, plus your org slug, project slug and auth token. Sentry signs every delivery with that secret (Sentry-Hook-Signature, HMAC-SHA256 of the body); Mushi Mushi also requires a fresh Sentry-Hook-Timestamp and drops a Request-ID or body it already accepted.
3. To route alerts too: Alerts → Create Alert Rule (issue alert) → action Send a notification via your internal integration.
4. Fire a test alert. The error lands in Reports with a via Sentry badge, a plain-English diagnosis, and a dispatchable fix.

Issues that already exist never fire again. Pull them in with Import on the Sentry card, the import_sentry_issues MCP tool, or POST /v1/admin/projects/<id>/sentry/import with { "issueIds": ["WEB-12"] } (ids or short ids, at most 10) or { "query": "is:unresolved", "limit": 5 }.

For a whole backlog, add "sinceDays": 30 and "limit": 10, then send the nextCursor from each answer back as "cursor" until it comes back null. Running it again is safe: issues already imported answer linked. If one app reports to two Sentry projects (say a frontend and a backend), list the second in sentry_extra_project_slugs and pick it with "sentryProject".

In the console, all of this is on the Sentry card:

• More Sentry projects (edit the card) takes up to 10 extra project slugs, comma-separated. It saves sentry_extra_project_slugs; clearing the field removes them. Over the API, send a string array to PUT /v1/admin/integrations/platform/sentry ({ "sentry_extra_project_slugs": ["sbc-be"] }; [] or null clears it).
• Import existing Sentry issues has a Sentry project picker (shown when more than one project is configured) and a Seen in choice (any time, or the last 7, 14, 30 or 90 days). A windowed search imports 10 at a time; Load next page repeats the same search from where the last page ended until Sentry has no more.

Behavior:

• Deduped per Sentry issue: repeat alerts land on the same report; re-importing a linked issue returns the existing report.
• Regressions reopen: an alert for an already-fixed report flips it to reopened and bumps the regression counter instead of filing a duplicate.
• Resolves both ways: when a Mushi Mushi fix PR merges, Mushi Mushi resolves the linked Sentry issue through the Sentry API (resolvedInNextRelease, else resolved) and comments the PR link; the fix commit also carries Fixes <SHORT-ID> for Sentry’s GitHub integration. A failed resolve shows on the fix timeline. action: resolved from Sentry resolves the linked Mushi Mushi report.
• Fix context: the files named in an imported issue’s stack are indexed right away, and codebase sweeps index stack-frame files of open Sentry-linked reports first.
• Your Sentry alert rules are the noise filter: only alerts you route at the webhook are ingested. Sentry User Feedback submissions are also ingested on the same endpoint.

Copy Mushi Mushi reports into Sentry (outbound plugin)

Everything above is built in. The plugin is only for the other direction: copying the bugs your users report through Mushi Mushi into Sentry, so they sit next to your Sentry errors. You run it on your own server.

1. Start the plugin where Mushi Mushi can reach it over public HTTPS:

   npm i @mushi-mushi/plugin-sentry
   export MUSHI_PLUGIN_SECRET=...   # must match the signing secret in step 2
   export SENTRY_DSN=...
   export SEVERITY_THRESHOLD=high   # optional: low | medium | high | critical
   # Optional: resolve the matching Sentry issue on fix.applied
   export SENTRY_AUTH_TOKEN=...     # event:admin + project:read
   export SENTRY_ORG_SLUG=acme
   export SENTRY_PROJECT_SLUG=web
   npx -p @mushi-mushi/plugin-sentry mushi-plugin-sentry

2. In the console: Marketplace → Sentry Mirror → Install. Set the webhook URL to https://<your-host>/mushi/webhook, and use the form’s signing secret (Mushi Mushi generates one) as MUSHI_PLUGIN_SECRET.

Package

@mushi-mushi/plugin-sentry

Events