Submit a ticketCall us

Training ClassSign up for Network Performance Monitor (NPM) and Scalability instructor-led classes

Attend our instructor-led classes, provided by SolarWinds® Academy, to discuss the more advanced monitoring mechanisms available in NPM as well as how to tune your equipment to optimize its polling capabilities. NPM classes offered:
NPM Custom Monitoring and Polling
Orion Platform Scalability

Reserve your seat.

Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > Limitations of excluding databases from Exchange Monitoring

Limitations of excluding databases from Exchange Monitoring

Updated January 26, 2017


This article provides brief information on the limitations of excluding databases from Exchange Monitoring.


  • SAM version 6.0 or later
  • Orion Platform version 2014 or later


It is not possible to exclude database from monitoring within AppInsight for Exchange, but you can write your alerting trigger conditions to exclude specific mailbox databases and/or remove any and all thresholds from a specific mailbox database so they do not appear in a warning or critical state. 


You can remove the thresholds from the database file and transaction log directory monitors. This will prevent them from going into a warning or critical state without affecting your other mailbox databases.

Database Copies may be reporting a critical state because this server is participating in a DAG yet there is no copy of this database anywhere. This is the status reported to us by Exchange itself and is echoed in the Windows Event Log of the Mailbox server since this is an unsupported configuration as stated by Microsoft's best practices.


Possible Workaround: 

1. From the AppInsight, go to the database you want to stop monitoring.

2.  Go to Management box at the top of the page, and then click Edit Database.

3. The last entry should be for Database backup for that database name, and if you clear the thresholds it should stop turning red.




Last modified