At a glance
Connect Sentry to stop production errors from living only in an alerts channel. Cogno watches the Sentry projects a project is bounded to, and when something new or escalating appears it checks whether the board already covers it before raising anything.
Before you start
- Decide which Cogno project should receive the issues. Sentry projects are named per Cogno project, under Filter.
- Know which Sentry organizations you want read. An authorization covers the ones your Sentry account can see; an organization it cannot see needs a connection from somebody who can.
Connect Sentry in Cogno
1
Open the Sentry integration
Go to Settings → Integrations and select Sentry.
2
Authorize Cogno
Select Connect Sentry and approve in Sentry. The browser returns to Cogno and the connection is completed there. Sentry does not ask which organization — that choice is made in Cogno, next.
Choose what the connection reads
A Sentry authorization follows the person who granted it, not one organization — so a connection usually arrives able to see more than you meant to connect. Two choices narrow it, both on the connection:1
Pick the organizations
Under Organizations, tick the ones Cogno should read. Everything else the authorization can see stays out of reach. A connection that sees exactly one organization has it ticked already — there was nothing to choose.
2
Pick the projects
Under Projects Cogno offers, tick the projects a Cogno project may then pick from. Untick the rest and they stop appearing anywhere.
When you need a second connection
Only when the organization is one your Sentry account cannot see. Then the person who can see it adds their own:1
Add their account
Select Add a Sentry account and approve in Sentry, signed in as that person.
Choose which projects a project reads
Connecting an organization does not by itself bring in any issues. What a Cogno project takes from Sentry is set on that project, the same way Slack channels and GitHub repositories are:1
Open the project
Select the project in the sidebar and open its Configuration panel.
2
Add Sentry projects to Filter
In Filter, select + next to Sentry and pick the projects this project should read. Cogno only takes events from what is listed here.
organization/project, because a project slug is only unique inside its organization. A Sentry project can be named by more than one Cogno project. A project with nothing listed receives nothing.
What Cogno does with an error
Cogno checks the projects you named every few minutes and reacts in two cases:
An issue that simply keeps happening produces nothing further — it is reacted to once, not on every check.
Cogno does not file a task for every error it detects. It reads the issue — how many people it has reached, whether it started with a release, whether it has been raised before and left — searches the project for issues that arrived alongside it, and checks the board. A dozen errors appearing together is a deploy rather than a bug, and an error the board already covers needs nothing. When it does warrant attention, Cogno raises it or hands it to a local agent to triage against the code.
An agent working on the error can read Sentry directly: the exception and the file and function it was raised in, and — for one occurrence — the application stack frames, the source around the failing line, the request that triggered it, and the release it shipped in. It reads only the Sentry projects the Cogno project it is working on has in its Filter, and nothing it does changes anything in Sentry.
A project is read for the first time when you add it to a Filter, and that first read records what is already open without reacting to it. A workspace connecting Sentry is not woken for every error it has been living with.