Sentry

Overview

What this integration does

Sentry detects errors, performance regressions, and release issues. NotiLens receives those events as structured notifications — with the project name, issue title, culprit, and a direct link back to Sentry. You choose the priority per alert rule, so a spike in 500 errors pages you immediately while a new low-impact issue just logs quietly.

Installation

Install NotiLens on Sentry

1. Open the NotiLens Sentry App

Click the link below to open the NotiLens app install page in your Sentry organisation:

Install NotiLens on Sentry

2. Log in to NotiLens

1. Clicking Install redirects you to the NotiLens login page.
2. Log in with your NotiLens credentials.

3. Authorise Sentry access

1. Sentry will request permission to send notifications to NotiLens.
2. Click Allow to grant access.

4. Select or create a topic

1. Choose an existing NotiLens topic to receive Sentry alerts, or create a new one specifically for Sentry.
2. Click Continue.

Topics let you organise alerts by project, team, or environment — e.g. a separate topic for production vs staging.

5. Installation complete

NotiLens shows a Sentry connected confirmation. You can close this page and return to Sentry.

6. Verify in Sentry

1. In Sentry, go to Settings → Integrations.
2. Search for NotiLens — it should show as Installed.

Alert Rules

Configure alert rules to use NotiLens

NotiLens is available as a notification action in any Sentry alert rule. You add it the same way you'd add Slack or PagerDuty — and you choose the priority per rule.

Error alerts

1. In Sentry, go to Alerts → Create Alert Rule.
2. Select Issues as the alert type.
3. Set your conditions — e.g. "A new issue is created" or "Issue occurs more than 10 times in 1 hour".
4. Under Actions, click Add action.
5. Select NotiLens from the list.
6. Choose the notification priority (see table below).
7. Save the rule.

Performance alerts

1. Go to Alerts → Create Alert Rule → Metrics.
2. Choose your metric — transaction duration, error rate, Apdex, etc.
3. Set threshold conditions for warning and critical levels.
4. Under Actions, add NotiLens for each threshold — use Warning for the warning threshold and Urgent for critical.
5. Save the rule.

Tip: set two NotiLens actions on the same performance alert — one at the warning threshold (warning) and one at the critical threshold (urgent). NotiLens handles them independently.

Priority Levels

Choosing the right priority

When you add NotiLens as an action in a Sentry alert rule, you select the notification type. This maps to NotiLens's priority system and determines whether the notification bypasses ML filtering or routes through it.

Events

Common Sentry alert rules for NotiLens