Issues and alerts
Alerts
Alerts are how Blipit tells people that something new broke or that a fixed bug came back. The Alerts page holds email rules; Slack, Microsoft Teams, Jira, Linear and webhooks live under Integrations and receive the same alerts. A workspace with no channels at all emails its owners.
1Add an email rule
On Alerts, enter an address, pick a project or All projects, and tick new issues, regressions, or both. Each rule shows when it last fired and whether delivery worked. Only owners and admins can change this; members can see it.
2New issues and regressions
A new-issue alert goes out the first time a fingerprint is seen. A regression alert goes out when a resolved issue gets a new event, with a note saying whether it came back in the same release or a later one. Snoozed issues skip both.
3Who else is emailed
Code owners whose rule matches the stack trace or URL get a copy. Odoo people in charge get new-issue and regression emails for their company. Nobody is emailed twice for one alert.
4Security thresholds
On the Scale plan the Alerts page also has Security thresholds: how many failed logins, blocked logins or password resets in how many minutes raise a security issue, per project or for the whole workspace. See Security monitoring.
5Bug reports
A new bug report, idea or question is emailed to the same people as error alerts, in each person's language, from alerts@blipit.io. Blipit waits until its screenshots and videos have uploaded, or two minutes at most and then says which upload is missing. The email shows the title, type, who sent it, the page, the browser, the Odoo model, record and field, the first screenshot and an Open the report button. Odoo people in charge only get reports from their own company. Each rule has a Bug reports switch, and the project's Bug report widget settings have Email new bug reports to turn the emails off for that project.
6People outside the workspace
When an alert or bug-report email goes to someone who is not a member of the workspace (an email rule address, an Odoo person in charge or a code owner), its button opens a secure guest view of that one issue or report instead of the sign-in page. Opening it emails a 6-digit code to the same address, so a forwarded email cannot be opened. After the code they see only that item, read-only, for 7 days on that browser, and can press Request access to ask the owners for a seat. Links work for 30 days. Members keep the normal link. Owners turn this off, see who viewed what and revoke access under Settings, Guest access, and every guest view is in the audit log.
7Other alerts
The Alerts page has more sections, each with its own guide: Workflow alerts for Odoo (see Odoo Workflows), Performance alerts for Odoo with Your own alerts on Team and Scale (see Odoo performance), and Dependency and server alerts (see Dependencies and Server health). App owners get their app's workflow and performance alerts.
8Alert history and the bell
Every alert Blipit sends is listed under Alert history at the top of the Alerts page, newest first: new issues and regressions, stuck apps, security, dependencies and server health, uptime, status pages, workflows, Odoo performance, SLAs, on-call incidents, bug reports and usage limits. Each row shows the sentence from the email, the project, the time in your time zone, the channels it went to and how many recipients, whether it is still active or has cleared, and an Open button. Filter by project, type or state, and load older alerts below the list. The bell at the top of the sidebar counts the alerts since you last looked and opens the latest 10. History is kept as long as your plan keeps issue history.
9Links in alert emails
Every link in an alert opens the workspace the alert belongs to. If you are a member of several workspaces and the alert came from another one, Blipit switches to it and opens the page. People who are not members of that workspace, or cannot see that project, get Not found.
Good to know
- Seats: members, pending invites, email rule addresses and Odoo people in charge share one seat count, deduplicated by email. When a rule would go past the plan's seats you see: '<Plan> includes N seats, and M people would be getting alerts. Remove one, or move up a plan on Usage.' Free has 1 seat, Solo 3, Team and Scale unlimited.
- Email action links (Resolve, Ignore) are signed, expire after 48 hours, work once, and only act when you press the button on the confirmation page, so mail scanners cannot resolve issues by prefetching.
- Security alerts go to your email rules, Slack, Teams and webhooks, or to the owners when there are none; never to Odoo people in charge or code owners.
- Bug report emails go out at most three times per project per hour. Reports that arrive after that wait and come as one summary, for example '12 new bug reports in Shop', with a link to each. Slack, Teams and webhooks get the same summary.
Stuck? Email support@blipit.io. Keys and the project id for each project are under API keys in app.blipit.io.