Rollbar plugin

Copies each bug Mushi Mushi triages into Rollbar as an item, and tries to resolve the item when the fix merges.

Not in the Mushi Mushi Cloud Marketplace yet. The console has no Rollbar listing, so you can’t install it from there. On a Mushi Mushi server you run yourself, add a plugin_registry row for it and install it like any listed plugin. To bring Rollbar errors into Mushi Mushi, use @mushi-mushi/adapters instead.

Setup (self-hosted Mushi Mushi)


npm i @mushi-mushi/plugin-rollbar
export MUSHI_PLUGIN_SECRET=...      # the signing secret set when the plugin is installed
export ROLLBAR_ACCESS_TOKEN=...     # project access token with post_server_item (or write) scope
export ROLLBAR_PROJECT_ID=...       # required by the server
export ADMIN_BASE_URL=https://...   # optional: console URL for report links
npx -p @mushi-mushi/plugin-rollbar mushi-plugin-rollbar

Point the plugin’s webhook URL at https://<your-host>/mushi/webhook.

Package

@mushi-mushi/plugin-rollbar

Events

Event	Action
`report.classified`	Create a Rollbar item (environment `production`, level from severity, fingerprint `mushi-<projectId>-<reportId>`)
`fix.applied`	Resolve the item (`PATCH /api/1/item/<id>`, `status: resolved`)

To resolve, the plugin needs the item id from Rollbar’s answer to the create call and keeps it in memory (pass your own cache to createRollbarPlugin(cfg, cache) to survive restarts). Rollbar documents that answer as returning an occurrence uuid; if it carries no id, nothing is stored and fix.applied does nothing. We have not confirmed this against a live Rollbar account.