Learn how traditional APM (application performance monitoring) differs from traditional APM. More info at

1. ENTERPRISE APM
Enterprise businesses use new, legacy, and commercial
applications written in multiple programming languages. They
may touch middleware components and reach end-users on
browsers, rich clients, and mobile devices. Problems can
happen anywhere, be sporadic, or impact only a few critical
transactions. It is important to monitor horizontally across
technology stacks.
Traditional APM (or developer APM) products are designed
to monitor vertical technology stacks like Java, .NET or
PHP, on browsers and mobile devices. They provide strong
technology support inside each stack, good deep dive
capabilities, and are often used as part of new application
development.
NEW
LEGACY
AND
COMMERCIAL
APPLICATIONS
BROWSER
RICH CLIENT
CITRIX
MOBILE
TRACK
ALL
TRANSACTIONS
ALL HOPS
20
THE SHAPE OF DEVOPS
Whether it is in the cloud or in the
enterprise, diverse DevOps teams
need to lead the way. They need to
share a common toolkit across
technology stacks and speak the
same language.
When things go wrong, the team
needs to rely on an agreed upon set
of monitoring data they can all
understand. No war rooms, no
blame storming, just a search for
the truth.
Development, operations,
database, networking, and other IT
groups need to see everything,
everywhere, all the time.
TECHNOLOGY ADOPTION RATES
Cloud adoption is ramping up
rapidly, but legacy and
enterprise software aren’t going
anywhere. The enterprise
involves hybrid models and
heterogeneous networks. Being
able to capture performance
data across multiple technology
stacks is a key to success.
31
MEASURE – the real user experience of
employees, customers, partners and others
in real time on browsers, rich clients, and
mobile devices.
TRACK – every transaction across every
hop. Sampling or averaging obscures key
information. Tracking only when a problem is
identified misses key data about starting
conditions.
REPORT – provide information in easy to
use charts, dashboards, and reports that
everyone can understand and agree on.
If you have a distributed and
heterogeneous IT
environment, you need to
capture performance data
horizontally across
technologies. You need
Enterprise APM.
If you have applications built
around a single technology
stack, and you can accept
sampling and averaging of
performance data, then
Traditional APM might be right
for you.
TRADITIONAL APM
JAVA
.NET
PHP
APPLICATIONS
BROWSERS
AND
MOBILE
SAMPLE
OR
AVERAGE
TRANSACTIONS
VS.
<20%<15%
50%
70%
SaaS
CRM
SaaS
ERP
Enterprise
Cloud
Adoption
SMB Cloud
Adoption
ISOLATE – problems that may be unique to
a user, location, or time period. These
intermittent issues can only be resolved with
data about every transaction.
SERVE – provide information that is relevant
to multiple organizations from business
people, to IT management, and all other
technical disciplines. Serve both the Dev
and the Ops of DevOps.
ENTERPRISE APM TRADITIONAL APM
MEASURE – the real user experience of
employees, customers, partners and others
in real time on browsers and mobile devices.
Typically do not monitor rich clients.
TRACK – typically sample or average
transactions. Sometimes track all
transactions after a problem is found. Must
be published to remote server. Do not
capture all hops of the transaction.
REPORT – provide information in easy to
use charts, dashboards, and reports that
everyone can understand and agree on.
ISOLATE – problems that may be unique to
an application and its technology stack.
Intermittent issues are difficult to spot and
may be lost in averaging.
SERVE – primarily developers of Java,
.NET, and PHP applications. The resulting
insights can be shared with other groups.