Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > 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