Network Management
SolarWinds Platform Node Reboot Alerts are delayed
Last boot alert is delayed. The email is received late. Alert emails are months delayed. ALERT: ${NodeName} rebooted at ${LastBoot}
First published date
11/17/2020 8:50 PM
Last published date
9/2/2025 5:17 PM
Overview
Sometimes, the last reboot alerts can appear delayed for servers. This is known behavior in SolarWinds Platform alerting.
Product section
Orion Platform
Cause
Misleading and incorrect email/event message is configured for the alert.
Resolution
The out-of-the-box alert for "Node Rebooted" has a misleading message. The default message reads
When the alert triggers, it will fill in with the previous timestamp of the Last Boot value for that node. This is dependent on when the server last rebooted - but can be days, weeks, months, or even years in the past.
This leads the user to believe that the node rebooted long ago but they are just now receiving an alert. The suggested email message should read something such as:
ALERT: ${NodeName} rebooted at ${LastBoot}
When the alert triggers, it will fill in with the previous timestamp of the Last Boot value for that node. This is dependent on when the server last rebooted - but can be days, weeks, months, or even years in the past.
This leads the user to believe that the node rebooted long ago but they are just now receiving an alert. The suggested email message should read something such as:
${NodeName} rebooted at ${N=Alerting;M=AlertTriggerTime;F=DateTime}.
The last reboot was at ${LastBoot}.