SAP Monitoring Tools Comparison v3.

0 9/13/2019
by IT-Conductor Inc.

https://www.itconductor.com/blog/how-to-select-your-sap-monitoring-tools

DISCLAIMER: The information represented in this

comparison is based on personal knowledge and experience
of its author(s).
All opinions are the author's own and does not necessarily
represent any vendors' view points.
You are hereby granted non-exclusive use of the content in
your own comparisons or publications, given proper credit
to its source.
If you notice any tool features that changed. Let us know by
email to [email protected].

Linh Nguyen - Initial version v1.0 7/7/2015

IT-Conductor team: Linh N., Vladimir M., Terry K. v2.0 3/29/2017

Update HANA Cockpit
Added Tivoli
Added BMC ProactiveNet
Reviewed SAP Solman 7.2, no meaningful changes in
Technical Monitoring

For detailed TCO analysis and c

IT-Conductor team: Linh N., Vladimir M., Too C., Femi C. v3.0 9/13/2019 contact [email protected]
Added Dynatrace
Added AppDynamics
Change SAP LVM to SAP LaMa (functionality same)
For detailed TCO analysis and comparison between Solman and IT-Conductor please
contact [email protected]
# Functionality Description

* How much effort, skills and resources are needed to Install,

Configure, Deploy and Maintain.
* Include central tools and managed systems, whether it's
1
Ease of Implementation & on-premise or cloud, agent or agentless.
Maintenance * Infrastructure requirements.
* Are there Jumpstarts available either as a service or
templates/wizards, etc.
* Do users access via GUI or Web or from anywhere?
 * How various instrumentations and their performance
counters are collected.
Performance Metrics & * Methods may include agents, webservices, API, native
2 calls, etc.
Collection Methods * Are the collection methods reliable?
* Is there self-monitoring of collection status as well as data
collection footprint?
 This is the most basic need in monitoring:
* How is availability determined and is its definition flexible,
3 Availability such as ping, logon, synthetic, how often, how long, what
percentage?
 * Are they static or dynamic (such as standard deviation,
4 Monitoring (Thresholds) averages, min, max, etc)?
* Is it easy to set and tune, by instance or class or centrally?

* How is notification of an event or exception handled?

* Are there flexible definitions of what items or groups,
5 Notification schedule (different for days and time), severity, and are
notification targets based on individuals, groups, roles?
* Is notification built in or external integration required
 For known reaction to anticipated events, how are they
6 Recovery Actions supported? Is it easy to integrate commands, scripts and
can they run cross-platform?

* What reports are available and how flexible are they to

customize or define?
* Are reports static, or dynamic like dashboards which can
7 Reporting be further analyzed?
* Are data available for download using external reporting? *
Can reports be scheduled and how are they delivered?
 * Can a definition of service be monitored including
applications, groups of systems, users, locations,
transactions, business processes, synthetic transactions? *
8 Service Monitoring Can the service level be managed at different level in the
hierarchy with respect to events, weight and impacts?
* Are monitored service easy to drill-down to find root-cause
correlation and further analysis?

* Can IT operations checklist be automated, as workflows,

runbooks, recovery actions with integrated monitor and
9 Process Automation logging?
* Are design tools easy to use, deploy and support cross-
platform?
SAP CCMS SAP Solution Manager (7.1 & 7.2) SAP Landscape Manager (LaMa) 3.0

* Highly Complex, Involves Solution

Manager (SM) landscape, BW, System
Landscaped Directory (SLD), LMDB
(Landscape Mgt DB), CCMSPING,
* Single systems pre- GRMG, CCMS Agent installation and
delivered monitoring configuration.
* Central monitoring (CEN) * Requires SAP Plug-In ST-A/PI.
* Primarily a virtualization & automation
requires technical * Requires SMD (Solution Mgr
platform but has some monitoring
monitoring setup via RZ21 Diagnostics) Agent on each managed
* Requires NW Java Base install using
* Java monitoring host
SWPM, LVM Add-on using SUM
additional work to hook up * DB monitoring requires DB client
* SAPHOSTAGENT required on all
to ABAP system installs
managed hosts
* SAPGUI access required * Many patches and SAP reports
* Additional licensing required if PCA
* CCMS Agents, activation (using RTCCTOOL)
(Post-Copy Automation) is used
CCMSPING, * Configuration using templates and
* Web access, mostly still in Netweaver
SAPHOSTAGENT wizards, but still requires many manual
webdynpro UI, some transitioning to
required setup steps
SAPUI5
* SAP MC (Management * Additional HW and optional SW
Console) can be used as licenses (such as Wiley Introscope
Java Gui enterprise)
* Needs active connection to SAP
Service under contract
* SAPGUI, Web, Fiori
* Slow if not properly sized
* Collectors include auto-
abap, RFC, SAPCCM4X,
SAPCCMSR, * Agent-based monitoring
* Limited collection from
SAPOSCOL, CCMSPING * Based on SAP MAI (Monitoring &
SAPHOSTAGENT and Diagnostics
Service Alerting Infrastructure)
Agent
* Each CCMS metric * Templates provides monitoring
* Monitors primarily using Webservices
provide the base scenarios and what gets collected from
and JDBC connections
instrumentation and can each managed system, how often, if
* Collects mainly data for ACM
be customized they are stored in BW
(automatic capacity management),
* Self-monitoring is critical * Limits the types of alert and
such as availability, users, response
as collection sometimes performance metric collected. Not
times, host resource utilizations
become stale granular as CCMS based monitoring
* No alerts monitoring of managed
* SAP Basis support * E2E requires Diagnostics Agents and
system
packs, kernel updates and Trace activation
agent updates on regular
basis
 * ABAP System Availability composed of
* ABAP availability
status propagated from technical app
monitored by RFC logon
server (instance status, HTTP, RFC)
* GMRG (Generic Request
collected by Diagnostic Agent
Message Generator) run
* SAPHOSTAGENT Availability reported * Checks for RUNNING states and
as application/agent to
by sapcontrol webservices reports percentage of instances with
report application
* JAVA System Availability composed of that status
availability back to CCMS
Java instance, Central Services (SCS), * Other states reported include
* RFCPING and
Application add-on, and Connection timeout, or UNKNOWN
CCMSPING services can
SAPHOSTAGENT
check remote destinations
* Database availability from sapcontrol
via ping and/or logon and
or sapdbctrl status, including service
report back into CEN
status
* Defaults and thresholds
are maintained in RZ20's
MTE (Monitoring Tree
Element) Properties and
* Configurable thresholds in the * Basic monitoring of instance status,
Methods
Managed object, OR the Template capacity utilization, and checks against
* Length of periodic
specific configurations
execution can be modified
* Thresholds are static
YELLOW, RED for
Performance MTE

* SMTP and/or SMS notification targets

via Alert Consumer Variant Maintenance
following logic of 'Create, Notify,
Confirm'
* 3rd-party integration to Incident * Notification for Automation activities
* SAPOffice and SMTP
Management set in Incident Variant status, Task Planner, Validation results,
can be configured to send
* Notification settings are made at the and ACM
alerts, but is often far too
global, template, alert, or work mode * Notification templates available for
noisy without filtering
level of hierarchy. Settings made at the each type of Notification
lower level of the hierarchy override the
higher level.
* Custom schedule and Recipient List
available
* Auto-reaction can be
assigned as a method, but
* Automated failover of virtualized SAP
few are implemented
* Auto-reaction needs to be created and resources in managed LVM pool
* Drill-down on specific
assigned to each Notification Variant * HANA takeover and auto-registration
alerts and metrics
capable
normally launch another
Basis monitoring TCODE

* On-screen reports are

* Service Reports collected via
normally by individual
EarlyWatch templates * Report for Capacity, System Load,
monitoring transactions
* Custom BW reporting possible with SLA for Automated Capacity Mgt (ACM)
* Periodic reports can be
development
generated via Earlywatch
 * BPM (Business Process Monitoring),
and some scenarios like PI (Process
* Some advanced
Integration)
configuration is needed to
* Templates need to be created and
monitor individual ABAP
maintained N/A
transactions
* Service Availability Management
* Advanced Service
(SAM)
monitoring is N/A
* SM 7.2 "Focus" solutions are
additional charge per user

* Single or Mass operations can be

scheduled (Restart, Stop, PCA, etc.) or
auto-reaction such as failover
* Validations are pre-built checklists
* Limited to methods * Guided Procedures as Wizard-based
against thresholds or configuration
assigned to an auto- tasks with checklists
settings. Can set severity, notification
reaction of an MTE * Require attended execution
and validation intervals
* Blueprints are best practice
templates, hard to maintain or
customize
 SAP HANA COCKPIT
SAP DBACOCKPIT SAP HANA STUDIO
(1.0 & 2.0)

* Java and Studio client

* SAP Fiori app served
install required
* SAPGUI-based by HANA XS Application
* Eclipse-based
Database monitoring Server
Administration Console
* Requires remote HANA1 COCKPIT
perspective available
database setup for non- * Built-in within HANA,
through HANA Studio
local systems, DBCO as part of Delivery Unit
* JDBC monitor through
(Database Connection) package
sapcontrol / sapdbcontrol
setup
* Simple monitoring with
* Requires HANA2 COCKPIT
some database and
SAPHOSTAGENT * Separate
configuration control
* Easy access for Basis installation,
* Python-based DBAdmin
and DBA recommended to be on
available on HANA host
its own server
but is memory-hungry
 * JDBC Connection to
* Fiori apps retrieve from
each HANA tenant DB's
Statistics tables, which
Statistics schema
also collects from
* Alerts, performance,
* SQL-based monitoring SAPHOSTAGENT
resource utilization, load
using DB client connection based on snapshots
including sessions come
* Collection based on * Data and configuration
from native statistics table
Auto-abap schedule is based on HANA
* Various traces including
* DBA Planning Calendar Studio
Expensive statements
for backup and * Trace analysis is
trace requires activation
consistency checks available for log files, XS
* Data displayed adhoc or
applications and
on refresh interval,
performance trace
independent of data
requires activation
collected on HANA system
 * Database services
status are monitored for
services other than XS,
and Indexserver
HANA1
COCKPIT *
* Database: connection to
Its built-in, so if the
* Operational state database server lost but
HANA is down,
determined by DB no external alerts can be
COCKPIT is not
connection monitoring generated
available
* For HANA the same * HANA service exceptions
* Can monitor up to
service states are indicate inactive, or
HANA1 SPS12 only
monitored as in HANA restarted services, as long
HANA2
Studio as nameserver and
COCKPIT *
indexserver are running
Can monitor several
HANA systems
* Only
support HANA1 SPS12
and higher
*Administration tasks
capability
 * Thresholds are
configured with HANA
* Individual client's studio
Studio
must be open to view
* Individual system-
* Standard DB check monitored system
based thresholds with
thresholds can be set to * Individual system-based
Low, Medium, and High thresholds
HANA2
* Once set, thresholds are * Configured checks can
Cockpit *
Static have periodic settings with
Additional monitoring
repeat intervals and/or
tiles not available in
specific time
HANA Studio

* SMTP-based email
* SMTP-based email
N/A * Can configure
* Can configure recipients
recipients for specific
for specific checks
checks
N/A N/A N/A

* Reporting via
Performance Warehouse * Static System
(BW datastores) Information reports can be N/A
* Can't schedule report for manually generated
delivery, download or print
N/A N/A N/A

* Preconfigured checks, * Preconfigured checks,

N/A
but no recovery actions but no recovery actions
OZSOFT SAP Mgt Pack, HANA MP,
ASE MP, BOBJ MP for Microsoft
IT-Conductor IBM Tivoli Monitoring
System Center Operations Mgr
(SCOM)

* IBM Tivoli Monitoring solutions

provide a means to manage
distributed resources
* Modules are delivered through
a set of offerings that include:
-IBM Tivoli Monitoring for
Applications
* Management Pack add-on to * SaaS offering via cloud
-IBM Tivoli Monitoring for
Microsoft System Center Operations platform
Business Integration
Mgr (SCOM), deployed in 1 hour * Agent-less monitoring: No
-IBM Tivoli Monitoring for
* Central SCOM/SAP Connector and central or managed agent
Databases
Configuration GUI for easy installation
-IBM Tivoli Monitoring for
configuration. * Requires a single proxy agent
Messaging and Collaboration
* Database management packs are to connect all SAP systems from
* The client offers two modes of
native to SCOM, no additional a site to the monitoring service
operation: a Java desktop client
hardware needed, use agentless * Minimal configuration needed
and an HTTP browser.
monitoring to monitor using default SAP and
* For Tivoli Data Warehouse
* Users access SCOM console GUI or database best-practices
need RDBMS
Web console templates
* Need Planing Architectire and
sizing
* Administrator teams and
application teams have skills
required for programming
(general skills).
 * Agent-based monitoring
* Agent run the collection in one
* CCMS BAPI + agent-less
of the following two modes:
external protocols (many).
- On-demand collection: The
* Seamless cross platform
agent collects data when it
* Agentless monitoring based on SAP monitoring (many adapters are
receives a request and returns
CCMS Monitor Sets, included)
that data.
SAPHOSTAGENT, and native * Each monitoring metric and
- Scheduled collection: The
ODBC/JDBC performance queries alert has associated class
agent runs data collection in the
* Retrievers define how and how
background on scheduled
often to collect monitoring data
intervals and returns the most
remotely
recently collected data when it
receives a request.
 * Agent Watchdog: The agent
* Can leverage both SAP CEN watchdog performs specific
* Integrated – agent-less, flexible
availability monitoring, as well as direct availability monitoring actions
definition of what availability is to
logon check for system response against the ITM agent based on
the customer, including check
* Synthetics monitoring availability and the policy in the agent’s
window and threshold
performance common agent package (CAP)
* Ping, Logon, Synthetics, Status
* SAPHOSTAGENT redundant check file. This component runs inside
reports from SAP agents
for service status the OS agent process as a
logical component.
 * Static / Dynamic / Std.Dev.
thresholds; flexible, rule based
* Thresholds can be centrally set in targeting
SCOM monitors that mirror SAP * Aggregates, averages, min,
metrics max, and intervals can define
* Static / Dynamic / Std.Dev.
* SAP Alert severity can be mapped how thresholds can trigger state
thresholds; flexible
and trigger different levels in SCOM change, with custom severity
* Powerful Alert and Metric filtering to * User, or role-based overrides
eliminate noise from SAP that can trigger state changes in
monitored instances
* Time-synchronized data

* Subscription-based notification engine * Advanced, Policy Based,

within SCOM based on severity. Dynamic Group Targeting,
* Individual and group-based Schedule and Severity based
* Advanced, Event based, rule
notifications notification target selection
Based via System Command
* SCOM integration to other service * SMTP-based email and/or
management platform for notification is adapter-based push to other
common enterprise solutions
 * One or more recovery actions
with a specific event. These
actions are automatically
triggered when the event occurs
and, typically, are used for
Automation includes: restoring satisfactory system
* Advanced, Policy-Based, service level.
Recovery Process triggering. * Each time an event occurs,
Recovery Processes can span the system provides a
N/A
system and application. notification of the event, triggers
* Interactive process design and a recovery action to restore
monitoring. satisfactory conditions and, if
the action is successful,
provides a notification that the
action was performed.
* Actions are associated with
the execution of a CIM method
or the execution of a program.

* Multi-row data plot

* Integrated, Single place for * HTML & PDF based
Definition Configuration and * Combined historical and real-
Scheduling. time data
* SCOM reporting based on SCOM
* Many preconfigured templates; * A set of out-of-the-box reports
data warehousing
* Flexible delivery. Report design that represent known best
* SAP alerts and metric from operations
is a part of the service. practices for the products or
database are sent to data warehouse
* HTML & PDF based solutions they are delivered
based on rules
* Cross-systems, applications, with, as well as a mechanism
landscapes, sites KPI-based (OPAL) to share reports as
reports experience of community grows
 * Advanced Flexible transaction
grouping,
* Drill-Down for Performance
* Distributed apps can be configured
analysis,
with dependencies between multiple
* Composite Service Definitions * Drill-down capabilities,
monitored apps
* Policy Based Monitoring / including leveraging other in-
* Dashboards based on SLA and target
Recovery / Notification, depth Tivoli monitoring tools to
objectives
* Role-based Dashboards identify the root-cause of a
* Service drill-down to bottom
* Synthetic transaction & service performance problem.
infrastructure component, all rolled up
monitoring
to automated Health service monitoring
* Service Grid and hierarchy
allow impact awareness & root-
cause

*IBM Tivoli Open Process

Automation Library (OPAL).
OPAL contains downloadable
* Synthetics monitoring availability and * Advanced Policy Based,
product extensions such as:
performance Interactive Recovery
* Automation packages
* Scheduled synthetic reports, including * Process Design using
* Integration adapters
eCATT scripts, and SAPGUI Graphical Flow charts.
* Documentation
transaction launch to measure * Automate common SAP Basis
* Plug-in tool kits
availability and latency operations.
* Technical services
 BMC (ProactiveNet) Dynatrace

Dynatrace SaaS:
Step1:Create your Dynatrca account
Step2:Install OneAgent and Environment ActiveGate
Step3: Fine tune you environment
Dynatrace offers also an on-premises deployment model of
Dynatrace called Dynatrace Managed:
Step1: Obtain a Dynatrace Managed License
Step2: Set up Your Managed cluster
Step3:Install OneAgent and ActiveGate
Step4:Fine tune your environment
* Solution monitors on-premise
and public cloud resources
(e.g., storage, UCS) and Browser UI is used to access performance data interactively
services, including SaaS, IaaS, and applications on Android and iOS devices
and PaaS.
* Deployments are classified
into the following two
categories:
- Single-server deployment
- Multiple-server deployment
* Desktop client, HTTP browser,
CLI console
* Server requirement: RDBMS
(Oracle or Sybase ASA) for
central repository for all the
monitoring configuration and
statistical data
 *Agent-based monitoring: OneAgent platform

https://www.dynatrace.com/support/help/technology-
support/supported-technologies-and-versions/

A single instance of OneAgent can handle monitoring for all

types of entities, including servers, applications, services,
databases, and more. OneAgent gives you all the operational
and business performance metrics you need, from the front-end
to the back-end and everything in between—cloud instances,
hosts, network health, processes, and services. OneAgent
discovers all the processes you have running on your hosts.
Based on what it finds, OneAgent automatically activates
instrumentation specifically for your unique application stack.:
* Agent-less and agent-based
monitoring
https://www.dynatrace.com/support/help/setup-and-
configuration/dynatrace-oneagent/

SAP ABAP Monitored as Technology not real user application,

with ActiveGate extension (still in Preview as of Sep-2019).
SAP process awareness and dependency monitoring are
enabled by OneAgent, not by the ActiveGate ABAP platform
monitoring extension. They are optional and require OneAgent
installation on AS ABAP servers and other servers from the
SAP landscape.
https://www.dynatrace.com/news/blog/introducing-the-
dynatrace-sap-abap-platform-monitoring-extension-eap/

HANA Monitoring is not supported

 Host-level Availability only not SAP components.
To assess health, the following performance metrics are
captured for each host and presented on each Host overview
page:
CPU
Memory
Disk (storage health)
NIC (network health)

* Ping, SNMP Agent

Availablity,SNMP Trap
Receiver,TCP monitor,
 Dynatrace provides full insight across SAP cloud ecosystems:
SAP Cloud Platform monitoring
SAP C/4HANA Monitoring

https://www.dynatrace.com/technologies/sap-monitoring/

Dynatrace utilizes two types of thresholds:

Automated baselines: Multidimensional baselining
automatically detects individual reference values that adapt
Types of thresholds:
over time. Automated baseline reference values are used to
* Absolute
cope with dynamic changes within your application or service
* Signature
response times, error rates, and load.
* Abnormality Event
Built-in static thresholds: Dynatrace uses built-in static
* Intelligent
thresholds for all infrastructure events (for example, detecting
high CPU, low disk space, or low memory).

Dynatrace therefore applied AI to develop an intelligent,

automated, multi-dimensional baselining method.

https://www.dynatrace.com/support/help/how-to-use-
dynatrace/problem-detection-and-analysis/basic-concepts/how-
problems-are-detected-and-analyzed/?
_ga=2.250804431.857733974.1562591024-
1032254637.1561881534

Availability events,Error events,Slowdown events,Resource

events,Custom alerts,Info events. Dynatrace allows set up fine-
grained alert-filtering rules that are based on the severity,
customer impact, associated tags, and/or duration of detected
problems.
Problem notification systems:
Email
*Advanced, Event based, rule Webhook
Based via SMTP-based email ServiceNow
or System Command JIRA
OpsGenie
PagerDuty
VictorOps
Microsoft Teams
Slack
xMatters
* Not true recovery-actions, but
using patented self-learning
analytics, automatically
discovers and learns the
behavioral and performance
trends for each of the monitored
application and service
components; identifying normal
and abnormal behavior.

No Recovery Actions - Alerts and dashboards only – leaves

troubleshooting to you.

Service quality reports:

Each service quality report summarizes the monitoring insights

that Dynatrace has compiled over the past week. Each report
offers an overview of your applications, services, infrastructure
utilization, performance problems, and the impact of
performance problems on your customers.

Types and formats

AppMon includes the following customizable report formats:
• PDF
• HTML and Tabbed HTML
* Impact report templates
• XML
* Event report templates
• Microsoft Excel and Excel 2007
* Performance reports
• CSV

Reports can either be created by the client or by the server.

Scheduled reports are one kind of server side reports.

In addition to regular REST Reporting the AppMon Server also

supports another REST interface for XML reports. It offers more
parameters than the regular reporting interface.

https://www.dynatrace.com/support/doc/appmon/application-
monitoring/reporting/?
_ga=2.49601775.857733974.1562591024-
1032254637.1561881534
 As service landscapes can become quite complex, Dynatrace
automatically categorizes services based on their dependencies
to other entities like services or applications.
• Entry points
• Used by applications
• External dependencies
• Background activity
* Performance indicators (KPIs), • Background activity
application and end-user https://www.dynatrace.com/support/help/how-to-use-
response times, and dynatrace/services-and-transactions/
service level objectives (SLOs).
• Define custom services
• Custom API definitions
• Configure service error detection
• visualized through Service flow
• Service-level backtrace can show you such call sequences
• PurePath visualization
• Context-specific drill down

Dynatrace OneAgent discovers all processes running on the

host and automatically activates instrumentation specifically for
* Need Integrating with BMC your stack. New components get auto-instrumented on the fly.
Server Automation https://www.dynatrace.com/platform/automated/?
_ga=2.216922207.857733974.1562591024-
1032254637.1561881534
SaaS and on-premise options are available
SaaS :
• AppDynamics AppDynamics
itself stores the data and
hosts the server components of the system
in the cloud
• Need to install only the agent
components
On-premise :
• Hosting the components and storing data
should be done by the user
• Need to install the agent components and
the controller and event service
components
• Involves additional setup and
administration
Should be instrumented with separate
agents for each application.
• To monitor applications — Application
agent
• To monitor servers — machine agent
Need to configure the agent during
instrumentation. Application agents for the
following languages are already available in
the AppDynamics Wizard
• Java
• .NET
• PHP
• Node.js
• Python

Browser UI is used to access performance

data interactively and applications on
Android and iOS devices

Upgrading application and machine agents

on a large scale is a nightmare; we cannot
push upgrades through the platform,
meaning, manual upgrades each time a
new major release is out. Each time we
have a new major release, we need to do a
Rollout.
Can create or customize metrics based on
the requirements.

https://docs.appdynamics.com/display/PRO
42/Metrics+Reference

AppDynamics uses self-learned baselines.

It calculates the dynamic baselines
automatically using the periodic load
patterns of given metrics.

Application Server Agent

• Monitors an application server in runtime
and send data to the controller
• For each application, a separate agent
should be installed
Machine Agent
• Installed on a machine to report data
about hardware, memory and network to
the controller
• Installed on virtual or physical machine
operating systems

SAP ABAP Agent

https://docs.appdynamics.com/display/SAP/
SAP+Monitoring+Using+AppDynamics

HANA Monitoring is only supported via 3rd

party extension
• The agent evaluates each response,
based on your specified violation rules, and
flags each response as failed (rule
violation) or successful (no violation).
• The service monitor maintains a rolling
buffer of evaluated responses. This buffer
has a configurable window size (number of
evaluated responses), success threshold
(number of successful responses), and
failure ratio (number of failed responses).
• The monitor collects evaluated responses
until the response buffer is full. Then it
evaluates the service as:
○ NORMAL - Successful responses is
greater than or equal to the success
threshold.
○ CRITICAL - Failed responses is greater
than or equal to the failure threshold.
• When the buffer is full, the monitor re-
evaluates the service every time it
evaluates a new response.

https://docs.appdynamics.com/display/PRO
45/Service+Availability+Monitoring
The AppDynamics Platform uses both self-
learned baselines and configurable
thresholds to help identify application
issues.

• Static and Dynamic Thresholds

• Percentage Deviation Threshold
• Standard Deviation Threshold

https://docs.appdynamics.com/display/PRO
45/Transaction+Thresholds

Email Notifications:
• Without a Template
• With a Template
SMS Notifications

https://docs.appdynamics.com/display/PRO
45/Notification+Actions
No Recovery Actions - Alerts and
dashboards only – leaves troubleshooting
to you.

Support Remediation and Custom Actions

A remediation action runs a local script in a

node. The script executes on the machine
from which it was invoked or on the node
specified by the remediation action
configuration.

A custom action is typically used to

integrate third-party alerting and ticketing
systems.

https://docs.appdynamics.com/display/PRO
45/Actions

Scheduled Reports:
• Application Health Report
• Dashboard Report
• Controller Audit Report
• Home Screen Report
• All Applications Summary
• User Experience: Browser Apps
Custom Reports

file formats:
• PDF
• JSON
• CSV

https://docs.appdynamics.com/display/PRO
45/Reports
SAP Supported Environments:
https://docs.appdynamics.com/display/SAP/
SAP+Supported+Environments

Extensions and Custom Metrics

Tier Metric Correlator
Dynamic Monitoring Mode
Service Availability Monitoring
Server metrics in transaction snapshots
Server KPIs in application flow map
Health rules for extended hardware metrics

Application Run Book Automation solution.

Can run reactions such as diagnostics,
remediation, HTTP requests, cloud auto-
scaling, and even custom actions. Provides
a level of automation that isn’t provided in
the same way by Dynatrace.