When you run the setup wizard, several global settings are configured for your installation. If you enter your SMTP settings and add a user, a few default conditions and actions are added to help you get started. As a reminder, the wizard can be accessed through the Tools menu at any time.
Before proceeding, introduce yourself to the following basic SentryOne alerting and response system concepts:
|Conditions||Describes the various states of any monitored objects.|
|Actions||Determines what happens when a condition is met.|
|Settings||Defines criteria for when a condition is met. Certain settings known as source settings are used to define what events are collected by SentryOne.|
There are a couple of ways to see how settings and conditions/actions are configured for your SentryOne installation. Select Reports to run the active settings list and configured actions list reports. Select Reports > General, or view configured actions and settings directly in the Conditions and Settings pane. By default, the Conditions and Settings pane displays on the right side of the SentryOne client. If you do not see the Conditions and Settings pane, select View > Conditions to restore it.
To configure global actions or settings, confirm that the Shared Groups node is selected in the Navigator pane. The shared groups node is the global or root node of your SentryOne installation. The SentryOne alerting and response system uses the principle of inheritance, so any action or setting you configure at the Shared Groups node is passed down to all applicable objects beneath it.
For example, if you configure a Send Email Action for the SQL Server Agent Job: Failure condition (shared groups), you'll receive an email anytime a SQL Server Agent Job fails across your entire monitored enterprise.
Refine actions or settings at each level, as needed. For example, if you have a development server in your environment that you don't wish to be alerted about, disable the Send Email Action at the instance level. This configuration only applies to that instance, and it doesn't affect any other server in your environment. This level of control gives you the ability to determine what happens in response to events occurring on your monitored targets.
Several levels within the SentryOne hierarchy where you can configure applicable actions and settings are outlined as follows:
For a more in-depth look at the SentryOne hierarchy and other alerting related features, see the Alerting and Response System topic.