Exam Observability-Self-Hosted-Fundamentals Topic 2 Question 13 Discussion

To prevent "alert noise" caused by temporary performance spikes, the SolarWinds Platform allows for threshold persistence. According to theSolarWinds Platform Administrator Guide, simply setting a threshold at 90% would trigger an alert the moment a single poll returns a high value.
The correct configuration to ensure onlysustainedhigh utilization triggers an action is toset the node to change CPU status if the threshold is met for multiple polling cycles. This is found in the "Edit Node" properties under the Thresholds section. For example, if the polling interval is 2 minutes and you set the condition to "10 minutes" (or 5 consecutive polls), the CPU status will only transition to Warning or Critical after the utilization has stayed above 90% for that entire duration. This filtering happens at the node/status level, ensuring that the alert engine only fires when there is a legitimate, sustained performance bottleneck rather than a transient spike caused by a routine background process.