AppDynamics Power User Training Notes – Day Three

Dashboards. Useful for displaying and sharing information across teams or departments. Allows integrating other tools via iFrame widget. Dashboards can also be embedded into other services or even web pages.

A dashboard can also be converted into a report. One can also schedule periodic emailing of reports to a recipient list. This might be useful to create a “weekly/monthly digest” of data relating to an environment.

Policy triggers define events that trigger actions. When the criteria in a policy is met, a corresponding trigger is activated. This can be used to control behaviour such as increaing thread pool size as load increases etc. The trigger must be associated with a health rule violation. For example, if a health rule specifies “calls higher than normal” then a policy can be created based on this heath rule. The trigger gets executed when violation of the specified health rule occurs. Triggers can span different stages of health rule violations, for example, start and/or end. More than one health rule violation event can be specified.

When defining actions for policy triggers, one can configure the action to require human approval before executing a particular action. In this case, one must specify email address of the approver within the action.

Runbook automation is a remediation action that is executed on a node on a policy trigger. For instance, if for some reason there’s a java out of memory error, the runbook automation can backup the logs and restart the JVM. Everything that the runbook automation does is logged with the action that was executed, time and the local script that the automation ran to carry out the specified action. There’s three types:

Remediation action: Run arbitrary script on a node

HTTP request: Make a HTTP request to some server notifying it of the issue.

Cloud auto-scaling: Scale out or scale in on cloud services like AWS.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.