Skip to content
FreesbeFreesbe Docsfreesbe.net

Sentry

Freesbe takes issues and alerts from Sentry. Once an admin connects it:

  • Each issue posts into the channel you pick as one card, with its level, the error, the project, where it happened and the issue’s short id. Issue alerts post the issue they’re about, with the environment and release, and metric alerts (like a slow checkout) post cards of their own.
  • The same card stays current. When the issue is resolved, the card turns green and says how long it was open, and a reply under it lets everyone following the thread know. Archiving and assigning show on the card. An issue that comes back after it was resolved gets a new card.
  • Resolve and Archive for 1 hour on the card change the issue in Sentry, when you give Freesbe the integration’s token.
  • A live problems board pinned in the channel lists every issue that’s unresolved right now, worst first, and reports post on their own every morning or every Monday.

Issues post as their own member, Sentry, so their cards are easy to tell apart from people.

Connect Sentry

Section titled “Connect Sentry”

Only owners and admins can connect it. You need someone who’s a manager or owner of your Sentry organization.

  1. Open Workspace settings → Integrations & apps → Integrations → Monitoring and click Connect under Sentry.
  2. Give the connection a name, like Sentry: storefront, and pick the channel it posts to.
  3. Pick which issues to post under Issues to post (see Levels).
  4. For the Resolve and Archive for 1 hour buttons, fill in Sentry organization address and API token (see Resolve and archive from the card). You can add them later.
  5. Click Connect Sentry. Freesbe shows the Freesbe URL for Sentry. Copy it now: it’s only shown once.

Then, in Sentry:

  1. Open Settings → Custom Integrations (under Developer Settings) and click Create New Integration, then Internal Integration.
  2. Name it Freesbe and paste the Freesbe URL in Webhook URL. Turn on Alert Rule Action.
  3. Under Permissions, give Issue & Event Read & Write. Under Webhooks, tick issue. Save it.
  4. To post alerts too, open an issue or metric alert rule and add the action Send a notification via Freesbe.

With issue ticked, every new issue in the organization posts. To post only what your alert rules pick, leave issue unticked and use the alert action.

Levels

Section titled “Levels”

Freesbe goes by the issue’s level:

In Sentry On the card Icon
fatal Fatal 🚨
error, or a critical metric alert Error 🔴
warning, or a warning metric alert Warning 🟡
info and debug Info 🔵

Issues to post leaves out issues below the level you pick.

Resolve and archive from the card

Section titled “Resolve and archive from the card”

With the token, everyone in the channel can press Resolve or Archive for 1 hour on an issue’s card. Archiving hides the issue in Sentry for an hour, and it comes back on its own if it keeps happening after that. The card shows who did it. Metric alerts resolve themselves, so their cards only link to Sentry.

To set it up, open your Freesbe integration’s page in Sentry (Settings → Custom Integrations → Freesbe):

  1. Check Issue & Event has Read & Write under Permissions.
  2. Under Tokens, copy the token.
  3. In the connection’s settings in Freesbe, fill in Sentry organization address, where you open Sentry (like https://northwind.sentry.io), and paste the token in API token. If you host Sentry yourself, include your organization: https://sentry.example.com/organizations/northwind.

Freesbe checks the token before saving it, and keeps it encrypted.

The board and reports

Section titled “The board and reports”

Like Zabbix, each connection pins a live problems board in its channel, listing the issues unresolved right now, worst first, with how long and who archived them. Reports count the issues Freesbe got over the last day or week: by level, still unresolved, total time, the typical time to resolve, the noisiest issues and the busiest projects. See The live problems board and Reports for more.

Questions

Section titled “Questions”

Can different projects go to different channels? Yes. Connect Sentry once per channel, make an internal integration for each, and add each one’s alert action to the rules of the projects it’s for (leave issue unticked, since it covers the whole organization).

Who can see the cards? Everyone in the channel. Use a private channel for issues only some people should see.

Is the URL a secret? Yes: anyone with it can post issues into the channel. If it leaks, delete the connection and connect again for a new URL.