Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > Server & Application Monitor (SAM) > Alert Email does not contain top 10 processes

Alert Email does not contain top 10 processes


Alert emails do not contain top 10 processes or the alert has an empty body field.


All SAM versions


The top 10 processes are pulled at the time that the alert fires off.  Due to the delay that is involved with a servers response to the query that Orion makes to it, sometimes we have not gathered the information before the alert gets fired off.  Allowing an adequate amount of time for Orion to gather the information from the server before sending off the alert email should resolve the issue.


Increase the time of the delay between the alert firing and the email being sent out.  In order to do that, please follow these steps:

  1. Edit the alert that you are seeing the issue with.
  2. Go to the Trigger Actions tab.
  3. Click on the Add Escalation Level button at the bottom of the page.
  4. Set a time of 10 minutes there (you can lower this later after verifying that the alert now works).
  5. Move the email that you have configured from the top section to the newly created section (or create a new email in the new section).
  6. Save the changes and then test the alert.  Once verification has been done on it working, feel free to change the 10 minutes to a lower number (checking after each one to make sure it still works).
    1. Please be aware that different servers will have different response times due to latency, burden on the server, etc.


For more information, see:

Last modified