3. Week Module Date Schedule Status
1. Visibility: From web application
interface to the database
Aug 21 6:00 AM GMT
11:00 AM EDT
Completed
In progress
2. Big Data and the Non Relational
database
Aug 28 6:00 AM GMT
11:00 AM EDT
Upcoming
Upcoming
3. Implementing the right website
monitoring strategy
Sept 4 6:00 AM GMT
11:00 AM EDT
Upcoming
Upcoming
4 Monitoring Cloud applications and
Containers
Sept 11 6:00 AM GMT
11:00 AM EDT
Upcoming
Upcoming
4. Agenda
Application response times and user
satisfaction
Identifying transactions that are slowing
down your app
Slow database calls preventing ideal
performance
Analysing error traces to eliminate all
performance barriers
5. • End users typically expect a quick response time (<3 secs)
while using any web application.
• The web server, application server, load balancer and
database are among the critical components that require
detailed visibility.
• The response time depends on several components
working together, all of which have to perform efficiently to
deliver the right user experience.
Application Model Overview
6. • Request overload
• Slice of death in Database
• Buggy application code
• Improper memory management
• Thread configuration
Reasons your application might be slow
17. • Individual business transaction apdex
score
• Transaction response time broken by
components like web request, handle
request, mvc, servlet, aspx
• Transaction response time and
throughput status
Transaction element wise response times
19. • Identify slow database calls
• Find the most hit database tables,
and determine if specific tables can
be indexed well
• Start tuning your database
performance and diagnose slow
queries.
Queries delaying response time
21. • Find the most
executed database
operations and its
response time
• Database
operation by caller
• Find the busiest
table and the most
performed SQL
operation on the
table.
Individual database calls
22. Common database problems and how to tackle them
I. Database response is slow towards requests
II. Not able to retrieve data when accessing a particular record in a web application
23. Discovery & mapping
Possible reasons:
• Not enough resources
• Queries taking more time to execute
I. Database response is slow towards requests
24. Buffer Manager stats
• Buffer & Cache hit ratio
• Page Life Expectancy
• Cache used per minute
25. • See log file and data file details for individual SQL DBs
• Generate reports for log and data files
MS SQL log file & data files
26. Oracle tablespace stats
• Identify used & free bytes of individual table space.
• Monitor Reads and Writes per min
• Track data files & monitor datafile auto extend
32. Details to analyze:
• Sessions
• Waits
• Locks
• Blocked queries
II. Unable to retrieve data while accessing a record in a web application
33. MS SQL - Session details
• Displays the SQL server session ID running in SQL server along with its status.
• Shows information on blocked request and allows user to kill user session.
34. Oracle - Session details
• Identify ONLINE, OFFLINE, or INVALID sessions as well as sessions initiated by specific users.
• Monitor number of memory sorts, table scans performed.
• Track physical & logical reads of the session as well as buffer cache hit ratio
35. Oracle - Session summary
• Know sessions wait time and its corresponding event.
• Track account status and user account expiry date.
47. • Custom instrumentation allows you to monitor specific blocks of your
application code.
• It allows you to track your own application methods captured and displayed
in the transaction traces.
• The instrumented methods will be displayed with execution time under the
trace details tab
APM Insight custom instrumentation
52. Contact : eval-apm@manageengine.com
Online Demo : demo.appmanager.com
1. Application response times and user satisfaction
2. Identifying transactions that are slowing down your app
3. Slow database calls preventing ideal performance
4. Analysing error traces to eliminate all performance barriers
Quick Recap: