Heartbeat alerts are generated in an interval of every 5 minutes if no communication from the director or any of the components of the working stack is failed. Heartbeat alerts are of
CRITICAL severity and have
0x0000 condition ID.
Disabling the notification service does not display the heartbeat alert in the UI.
It generates in three conditions:
Kafka down
Nsfw down
Telegraf down
SupportAssist heartbeat
conditionId 0x0001-This alert generates if DC is not communicating with notifications for more than 5 minutes. This alert is with severity
CRITICAL.
conditionId 0x0002-This alert generates if DC is configured and the payload validation fails (in all condition except current_connection_state=enabled & last_five_min_success_rate >= threshold & last_hour_min_success_rate >= threshold) .
If the
current_connection_state is enabled and the heartbeat is 0, then there is no requirement to create any alert. This alert is with severity
ERROR.
Threshold value is configured, and the configuration file is present under
/etc/opt/dell/vplex/notification/ folder. This file
notification.conf gets installed along with notification RPM in all the nodes.
After changing the value from next alert, it considers the new value as the threshold. No service restart is required.
If the configured value is invalid or the file is not present, then the default value 0.5 is used as the threshold.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\