On this page:

Related pages:

You can configure Server Visibility to alert you when certain conditions are met or exceeded based on monitored server hardware metrics.  The Getting Started Wizard can help you through the process if you're new to using AppDynamics Pro. Alternatively you can create alerting policies manually if you are already familiar with the process.  

You configure Health Rules, Actions, Policiesand Email Digests for monitoring servers almost exactly the same as you would configure these for monitored applications, with some minor changes.

Health Rules

Default health rules based on several usage metrics are enabled for Server Visibility. You can modify these and set up your own health rules. The default health rules are shown in the following screen shot:

On the Affects tab of the Health Rule wizard, you can choose to apply the Server Health Rule to:



The health rule is violated when specified critical or warning conditions are met.

Hierarchies, Groups, and Subgroups

Health rules can be applied to subgroups or machines within selected subgroups. Subgroups available on the Affects tab of the Health Rules wizard are Machines that are grouped into hierarchies depending on the Machine Hierarchy Property configuration for the Standalone Machine Agent. Also, see Machine Agent HierarchyThe subgroups are the leaf group a machine is in. So for example, if there are three machines where:
A and C are in the same subgroup, B is in a different one.


Server Policy Actions are triggered when any or select Health Rule Violation Events occur. Unlike Application Policies, Server Policies cannot be based on custom events.  


Actions are performed when a health rule is violated and a policy is triggered. Actions can be email or SMS message notifications, HTTP requests or custom actions that have been uploaded to the Controller. There are also email and HTTP request templates for you to use for alert and respond actions. 

Email Digests

Email Digests let you send notification of chosen health rule violation events to specific email addresses at a specified frequency, such as every 2 hours.