The dashboard provides an easy and straightforward way for you to create and integrate alerts into your workflow. OverOps enables you to be alerted whenever new errors are introduced, or specific errors exceed target volumes in any of the dashboard's built-in or custom views.
Alerts are controlled from the View Settings dialog accessible by clicking the when hovering over a dashboard view. Alerts are assigned to views, that means that once a view has been defined to visualize specific types of errors, or errors stemming from specific applications or servers you can immediately assign an alert to that view.
Within the View Settings dialog you can choose what you want to be alerted on - new errors introduced into the view and/or a numeric threshold for number of occurrences in the view in a rolling hour window.
In this dialog you also choose where you want to be alerted to - your email, or your team’s Slack, HipChat, PagerDuty or JIRA.
For example if you define a view called NullPointerExceptions, you can then set an alert to know exactly whenever a new NullPointerException is introduced anywhere into your environment using the "new error" toggle. You can also set alerts based on hourly volumes through the "threshold".
The alert settings in the View Settings dialog lets you configure what to be alerted on and through which channels
To get an overview of all defined alerts and alert integrations, go to the Settings | Alerts. This dialog is constructed of two parts:
- View Settings - this tab shows all the views, starting with alert defined views, indicating the configurations of each alert (on new errors/thresholds) and the designated channels for that alert. You can edit alerts from this tab as well, or go to the View Settings dialog by clicking on the “Advanced settings” within the “Send to” column.
- Default Settings - this tab shows the default alert integration configurations. Here you can set-up the default Slack channel, HipChat room, JIRA instance or PagerDuty service.
While Email can be configured per user, the default Slack, HipChat, JIRA and PagerDuty integrations can only be setup by the account admin, as they are shared by all users accessing the installation. That said, you don’t have to use the default settings - all users can set-up a different integration for a specific alert in the View Settings dialog.
The "View Settings" tab allows you to get an overview of all views and alerts
1. New error alerts will be fired whenever an error matching the View for which it was is defined. The information will include the Installation, Application and Server in which the error was detected. It will also include the error location and the entry point in your application leading into the error, as well as the full call stack. Clicking the alert will lead you directly into its Error analysis screen to enable you to drill in into its cause.
A new error alert in Slack
2. Threshold alerts are triggered whenever the number of occurrences in the view for which the alert was defined exceeds a numeric threshold in a rolling hour window. The contents of the alert will include the View for which it was defined (e.g. "Log errors in App1"), the time window and number of occurrences. The alert also includes the top 5 events contributing to the alert. Clicking the alert will take you directly to that view in the dashboard in the exact timeframe in which the threshold was exceeded.
A threshold alert in Slack
3. Email digests are sent to you aggregating new error alerts into a single email once the number of alerts exceeds a specific number over a target window frame. Both of these values can be set in the Email tab either in the View Settings dialog or the Alert Settings overview dialog. You can also ask to receive a daily digest covering all new errors over the past 24 hours.
Controlling email digests through Email tab
Receiving a daily digest over email lets you see errors that were introduced over the last day