This page applies to an earlier version of the AppDynamics App IQ Platform.
For the latest documentation, see the 4.5 Documentation.


Skip to end of metadata
Go to start of metadata

Beta Disclaimer

This documentation mentions features that are currently beta. AppDynamics reserves the right to change the features at any time before making them generally available as well as never making them generally available. Any buying decisions should be made based on features that are currently generally available.

You can configure AppDynamics Server Monitoring - Beta to alert you when certain conditions are met or exceeded based of metrics observed for monitored server hardware.  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

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

Subgroups

  •  all or selected subgroups 

Machines

  • all machines in the active account
  • machines within selected subgroups
  • selected machines
  • machines whose names match certain criteria

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 that are available on the Affects tab of the Health Rules wizard are Machines that are grouped into a hierarchies via the Machine Hierarchy Property configuration of the Standalone Machine Agent. These are the subgroups that are available on the Affects tab. In particular, the subgroups are the leaf group a machine is in. So for example, let's say there are three machines where:
  • A is in group Data Center 1|Rack 1
  • B is in group Data Center 1|Rack 2
  • C is in group Data Center 1|Rack 1
A and C are in the same subgroup, B is in a different one.

Policies

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 

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.