...
There are many potential uses for the custom alert target. If you wish to apply some complex filtering and/or routing logic, you can use the IsHandled property to mark alerts for inclusion/exclusion. You may also wish to generate a log file of a specific format for your external log ingestion software, or perhaps would like to send alerts to an edge-logging service. As this is a standard custom-code device, you can include standard and web references, resources etc., making it easy to connect to and distribute alerts to other platforms. For example, to connect to Nagios, you could implement the following:
The Scheduling tab let's you specify when your alert group will receive events. It has three options:
- No Scheduling: Your alert group will receive all events regardless of day or time.
- Days & Hours: Choose when your alert group will receive events based on the day and hour (minimum resolution 1 hour)
- CRON: Specify a CRON string (which must contain an internal marker, ie ' - ')
The most common usage would be 'Days & Hours'. You can toggle a day/hour by clicking with the mouse. Dragging the mouse let's you select multiple adjacent blocks. 'Office hours' and 'After hours' would appear as follows:
The final tab, 'Tabs & Channels' lets you specify which group(s)/tab(s)/channel(s) will be included. By default, the "All" option in each header is checked, including all items. To start filtering, uncheck the "All" checkbox and check the items you wish to include:
