ALERTS Configuration Syntax
The ALERTS Configuration is used to set up the features that allow Dashboard URL's and/or related entities to be included in Threshold alert messages.
SUBSYS ALERTS DEFINE WEB_ADDRESS (https://<machine-name>/) SET DESTINATION (<destination-name>, {Y|N}>) RICH-ALERTS ({ON|OFF}) RICH-ALERTS DESTINATION ({snmptrap|dispatchmanager}, {Y|N}) RICH-ALERTS DISPATCH-MANAGER-FORMAT (HTML, {Y|N}>) FIPS-SNMP-VER ({v3|All}) REOPEN-CLOSEACK-ALERT() PRESERVE-ALERTS ({Y|N}) CACHE-INTERVAL (<n>) CACHE-TIMEOUT (<n>) SUPPRESS-THRESHOLD () ALERTS-SOURCE-OVERRIDE ()
Syntax Elements
DEFINE WEB_ADDRESS
The DEFINE WEB-ADDRESS statement refers to adding Dashboard URL's to alert messages.
(https://<machine-name>/) | Define the base address of the Prognosis web server |
SET DESTINATION
The SET DESTINATION statement refers to adding Dashboard URL's to alert messages.
<destination-name> | Alert messages can include a URL for a Prognosis dashboard that can provide meaning and context. Example: SET DESTINATION (DispatchManager, Y) |
{Y|N} | Sets if the URLs will be included in the alert messages. |
RICH-ALERTS
The RICH-ALERTS statement refers to adding related entities to alert messages. For details see the Alert Blueprints.
{ON|OFF} | Setting this statement to 'ON' will cause any triggered Thresholds to contain the additional contextual details. |
RICH-ALERTS DESTINATION
The RICH-ALERTS DESTINATION statement refers to adding related entities to alert messages. For details see the Alert Blueprints.
{<snmptrap>|dispatchmanager} | Destination of where the alert text will be sent, either a specified SNMP Trap name or Prognosis Dispatch Manager. |
{Y|N} | Sets if the additional contextual information will be included in the alert text. |
RICH-ALERTS DISPATCH-MANAGER-FORMAT
The RICH-ALERTS DISPATCH-MANAGER-FORMAT statement refers to adding related entities to alert messages. For details see the Alert Blueprints.
HTML | Format of the Dispatch Manager email message. Currently, only HTML is supported. |
{Y|N} | Sets if the HTML format is to be used. Without HTML, a simple plain text email message will be generated while the HTML format provides a clearer easier to read format. |
FIPS-SNMP-VER
The FIPS-SNMP-VER token can be used to configure what versions of the SNMP Trap protocol are permitted to be used for sending alerts when FORCE-FIPS-ENCRYPTION is configured. If FORCE-FIPS-ENCRYPTION is not configured, this token has no effect.
{v3|All} | Select either v3 or All v3 - will allow only SNMPv3 Traps when in FIPS mode. All- will allow all SNMP Trap versions when in FIPS mode. Default: v3 |
REOPEN-CLOSEACK-ALERT()
When this statement is added to the ALERTS Configuration, it will allow a problem alert that is in a CLOSEACK state to return to an OPENACK state when a further ON event is triggered for the exact same condition. Without applying this optional statement, alerts in the CLOSEACK state will remain in that state even when another ON event is triggered for the same condition. This option is available in Prognosis 11.5 and later versions. For further details see the Operator Acknowledgement for Thresholds
The following PRESERVE-ALERTS, CACHE-INTERVAL and CACHE-TIMEOUT statements refer to the Prognosis feature that will store current alert information in cache so that if Prognosis is stopped these alerts will not be duplicated. upon restart. For details see the Preserving Alert State on Restart.
PRESERVE_ALERTS
{Y|N} | Option to enable or disable the Prognosis 'Preserve Alerts' feature. |
CACHE-INTERVAL
<n> | The interval, in seconds, at which the current alert state will be saved to disk. |
CACHE-TIMEOUT
<n> | The time period, in seconds, at which the alert state will be discarded if it is older than the configured value. |
SUPPRESS-THRESHOLD()
When this statement is added to the ALERTS Configuration, it will permanently disable all Thresholds on the current Prognosis server and will not dispatch any messages to any configured destinations.
ALERTS-SOURCE-OVERRIDE() -New-
When this statement is added to the ALERTS Configuration, it will allow the substitution of the Source Node for the alerts with fields that are marked with the DEVICE option. See Defining a Field for a User Record for more information.
This option is enabled by default in new Prognosis 11.7 and later installations. Upgrades from Prognosis version 11.6 and earlier will have this option disabled by default.