Custom alerts
Lenovo XClarity One raises alerts based on known hardware and firmware issues. You can create alert rules for raising custom alerts that you are interested in based the occurrence or frequency of certain events or based on metric thresholds.
Event-based alerts
Event occurrence. An alert is raised when one or more events occur based on one of the following criteria.
When all the target events occur at least once during a certain period of time
When any of the target events occur collectively the specified number of times (count) during a certain period of time
Every time one of the target events occur
When each of the target events occur in sequence during a certain period of time
Event frequency. An alert is raised when one or more target events occur a specific number of times (count) during a certain period of time based on the following criteria.
Every time one of the target events occur
When any of the target events occur a specific number of times (count) during a certain period of time
You can create alert rules for an event that already occurred by clicking Monitor in the context menu from the Device management view, and then click the title of the Events card. Select the event, and then select the Create alert rule icon (
).
You can generate an alert rule for any event by clicking the Alert rules tab on context menu from the Settings view, and then clicking the Create alert rule icon (
).
Tip: For a list of event codes, see Event messages.
Metric-based alerts
An alert is raised when the value of a usage-metric exceeds the defined threshold based one of on the following criteria.
When the average value of the metric exceeds the threshold (based on the comparator) during a specific interval. For example, you can create a rule to raise an alert when the average CPU Temperature (metric) during a 24-hour period (interval) is greater than (operator) 40 degrees C (threshold).
When the metric exceeds the threshold (based on the comparator) a certain number of times during a specific interval. For example, you can create a rule to raise an alert when the CPU Temperature (metric) is greater than (operator) 40 degrees C (threshold) for 5 times (count) in a 24-hour period (interval).
When the metric exceeds the threshold (based on the comparator) for a certain cumulative sub-interval out of specific given maximum interval. For example, you can create a rule to raise an alert when the CPU Temperature (metric) is greater than (operator) 40 degrees C (threshold) for cumulative 30 minutes out of 120 minutes period (maxInterval).
When the metric exceeds the threshold (based on the comparator). For example, you can create a rule to raise an alert when the CPU Temperature (metric) is greater than (operator) 40 degrees C (threshold).
You can edit alert rules for usage-metric thresholds, but you cannot create new alert rules for them.
Currently, XClarity One supports threshold alerts for processors and memory.
Thresholds for these usage metrics are enabled by default. When enabled, an alert is raised when a component meets or exceeds its warning or critical threshold for the alert duration. The alert duration is the number of minutes during a specific period that the threshold value must be met or exceeded. For example, if processor temperature has a warning threshold of 80% and alert duration of 4 of 10 minutes, then an alert is raised when the processor temperature exceeds 80% for 4 or more minutes within a 10-minute period.
The minimum interval is 2 minutes within a 5-minute period.
You can set warning and critical usage thresholds and the alert duration for the certain components by clicking the Alert rules tab on context menu from the Settings view and then clicking the row for the component that you want to change.