With configured notification rules, events could be sent out via SNMP, SMTP or ESRS. But by default, isi_celog_notification does not alert coalesced events, so the user may be confused when they did not receive events when the issue occurs if the event was coalesced to previous events.
This can be configured specifically to send an alert via SNMP, SMTP or ESRS.
1. First, list all notification rules on your cluster from running the command:
#isi events notifications list
2. Then find Event ID of the coalesced events that the user needs to be sent, you can select IDs from the following:
SYS_DISK_COALESCE 199990001
NODE_STATUS_COALESCE 299990001
NODE_INTERNAL_NETWORK_COALESCE 299990002
NODE_EXTERNAL_NETWORK_COALESCE 299990003
REBOOT_COALESCE 399990001
FILESYSTEM_COALESCE 899990001
HW_SYSTEM_COALESCE 999910001
HW_SENSOR_COALESCE 999910002
HW_FAN_COALESCE 999910003
HW_TEMP_COALESCE 999910004
HW_VOLTAGE_COALESCE 999910005
HW_I2C_COALESCE 999910006
HW_STORAGE_TRANSPORT_COALESCE 999910007
3. Selected the severity of events to be sent, or simply add it as all severities ()(info, warn, critical, emergency):
# isi events notifications modify --name=<notification rule> --add-<severity>=<coalesced event id>
For example: we'd like to alert coalesced fan events via ESRS (usually called ConnectEMC)
#isi events notifications modify --name=ConnectEMC --add-all=999910003
4. After modification, check the current status to see if it's configured as per the user's request (under column LEVELS, you will see (C==> critical , W==>warning , I==>info, E==>emergency)):
#isi events notifications list --name=<notification rule>