This document discusses the need for application performance management (APM) tools. It notes that occasional errors occur in applications that are difficult to track down due to out-of-date documentation and large volumes of log files. Finding issues can take a long time and cost a company customers and money. Traditional methods like logs and documentation are inadequate to resolve problems quickly. APM tools can automatically map applications, monitor transactions in real-time, and pinpoint performance bottlenecks down to specific lines of code or database calls without additional logging. This allows companies to quickly resolve issues before greater costs are incurred.

1. Why You Need APM
Sunil Vanmullem

2. 2
When IT goes wrong
Somewhere in your data center, in a server somewhere, something went wrong. There
were no lights, no log information. It just went silently wrong for one transaction in 100,000
to your e-application. It happens intermittently at non uniform intervals. 99.9999% of your
customers don’t experience this failure.

3. 3
Time is Money – lots of it
You have to resolve the problem. Every customer is important and your e-application builds
long lasting loyalty – you have 12M customers delivering profits of 1Bn. It is critical that
each and every customer has a great customer experience as its not just their experience
that matters, they also bring their friends. It just takes one social media message from a
disgruntled customer.

4. 4
There is no manual
Design docs are great, except when your store is on fire. Documents stop being relevant
from the moment the application enters operations. You don’t have time to pour through a
hundred UML diagrams, you want the fire extinguisher… it doesn’t exist in a document.

5. 5
Which Log?
Each application has its own logs, each rotates over time. In one day your server farm
generates thousands of log files. The best part is that logs don’t contain everything you
need to solve the problem, or in any kind of sequence - even if you can find them.

6. 6
Time is still money
That’s another thousand customers taking their business elsewhere, and you still haven’t
had breakfast.

7. 7
The Detective Trail
You’ve already spent 6 long weeks looking at this problem. You discover that the
documentation is hopelessly out of date and incomplete. You have consulted a wide range
of people who are or were involved with the project. consensus: there is a problem, but its
definitely not in their area.
Infrastructure
Analyst
Database
Analyst
Product
Owner
T1 Support Design
Authority
Lead
Architect
Project
Manager
Solution
Designer
Business
Analyst
Coder
Stream Lead
Test Lead

8. 8
So you know what the problem is
There are 400 revenue-critical servers In your cluster under tight change control. You don’t
know which server is experiencing the problem or which function it is. If you added logging
you would generate 1.8TB of log data each and every day. There is no hope of analysing
that much data….
Your IT is holding back your business.

9. 9
Still think theres a magic bullet?
There is no silver bullet. There isn’t enough documentation that will put the fire out. Logs
files are not the answer, you cant monitor everything all the time.
… actually, the last point, you can.

10. 10
How it works
APM tags transactions at entry points to your applications. It uses this to follow transactions
through your applications and through to external systems.

11. 11
Discovery
APM creates a map of your applications and data flows through it – automatically,
effortlessly

12. 12
Application Performance Management
It takes under an hour* to implement completely transparently to your application. APM
discovers automatically, in real-time, where each transaction goes, the response rate of
every transaction and narrow performance issues to a line of code, a web-service call, or
even a SQL call. Works for Java, SQL, PHP and .NET.
The entire
application
Line of Code and
SQL View

13. Demo ( if the technology permits)

14. Auto discovery

15. Quickly narrow root cause

16. Focus on what really is slow

17. Get really specific

18. Specific to the individual transaction

19. To the line of code

20. Really

21. And database calls

22. 22
Still looking
there for an
answer?
…yeah, good
luck with
that

23. 23
What your competitors are
doing to your market share.

24. 24
Questions ?