Chapter 32. Alerts and Notification

The Never mark trigger as failing option disables the failure notification in the Server UI. If you set this option and the trigger fails, it will not be marked as failing. However, the number of failures for Data Services and Event Listeners will be incremented.

Figure 32.1. Never mark trigger as failing option chosen

The Any failure will mark trigger as failing option considers the trigger failing even if a single failure occurs.

This choice is suitable for infrequently running triggers.

Figure 32.2. Data Service - Alerts and Notification

You can set threshold to

The Mark trigger as failing when option sets the trigger as failing when a threshold is reached. The threshold can be specified as a percentage of failing executions or as a number of failing executions in a row.

This choice is suitable for frequently running triggers.

Figure 32.3. Data Service - Alerts and Notification

For Data Services, you can also select HTTP status codes which should be considered by CloverDX Server as an endpoint invocation failure.

Select the HTTP status codes by entering individual codes or ranges of codes separated by commas. By default, codes 404, 500, 501, 502 and 504-599 are considered as an endpoint invocation failure. Leaving the field blank means that CloverDX Server considers all HTTP status codes from the range 400-599 as invocation failure.

Ignored Error Codes

By default, CloverDX Server does not consider the following HTTP status codes as failures: 503: The code is returned when invoking a manually disabled endpoint. 401: The code means the user has not been authorized. Many HTTP clients don't use preemptive authentication, send the first request without credentials and handle 401 status by sending another authenticated request. You may add these status codes to the Failure Filtering field to treat them as failures.

If a trigger fails, it is shown in the table of Schedules, Data Services or Event Listeners, respectively. Additionally, the number of failing triggers is shown in the main menu.

Figure 32.4. Some Data Service is failing

You can also set an email notification. This email notification works additionally to the notification in the Server UI. It sends an email when the health state of a trigger changes. An email is also sent if the trigger was failing and you manually reset its health state.

Figure 32.5. E-mail Notification

With the Test button, you can send a testing email to the addresses of the recipients.

Email notifications require a working connection to an SMTP server.

You can add the trigger to Monitors (Operations Dashboard) directly from the Alerts and Notification tab.

Figure 32.6. Adding trigger to monitors

Alert levels are used on the Operations Dashboard. They show you the severity of problems and help you decide which ones to address first.

You can set the alert level for each trigger. When multiple triggers start failing, highest level triggers and monitors are shown first and they are also “more red”.

You can use the following alert levels, Medium is the default:

Figure 32.7. Alert level selection