Applications Manager
An all round on-premise application performance monitoring solution for IT Ops and DevOps
Visibility: From web application
interface to the database
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
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
• 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
• Request overload
• Slice of death in Database
• Buggy application code
• Improper memory management
• Thread configuration
Reasons your application might be slow
Apdex score
Response
time
Application Performance Monitoring: Key performance indicators
Error traces
Transactio
n traces
Slow SQL
statements
APM Insight for end to end visibility of your web applications
Coming soon: Support for PHP and Node.js applications.
APM Insight data collection
1. Application response times and user satisfaction
APM Insight Dashboard
• Global open standard to measure end user
satisfaction
• Scale of 0 to 1
• Helps identify satisfied, tolerated and
frustrated users
Apdex score
• Response time and response time by tiers
• Throughput
• Slowest transactions by response time
Response time and throughput
2. Identifying transactions that are slowing down your app
• Response time
• Slow business transactions
• Error traces
Transaction elements for performance issues
Transaction component split up
• 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
3. Slow database calls preventing ideal performance
• 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
Overall performance of the database
• 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
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
Discovery & mapping
Possible reasons:
• Not enough resources
• Queries taking more time to execute
I. Database response is slow towards requests
Buffer Manager stats
• Buffer & Cache hit ratio
• Page Life Expectancy
• Cache used per minute
• See log file and data file details for individual SQL DBs
• Generate reports for log and data files
MS SQL log file & data files
Oracle tablespace stats
• Identify used & free bytes of individual table space.
• Monitor Reads and Writes per min
• Track data files & monitor datafile auto extend
MS SQL top queries by CPU
MS SQL Top queries by CPU
MS SQL Slow running queries
Oracle buffer gets - Top 10 queries
• Buffer Gets
• Execution
• Buffer Gets per Execution
Oracle disk reads - Top 10 queries
Details to analyze:
• Sessions
• Waits
• Locks
• Blocked queries
II. Unable to retrieve data while accessing a record in a web application
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.
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
Oracle - Session summary
• Know sessions wait time and its corresponding event.
• Track account status and user account expiry date.
MS SQL - Top waits by waiting tasks
MS SQL - Most blocked queries
Oracle - Lock
• Know which type of session lock type is being used.
• Track blocked session time.
4. Analysing error traces to eliminate all performance barriers
• Identify slow internal invocations (methods) in the code and trace the execution details for URLs
Pinpoint
Traces to investigate time consuming transactions
Drill down to SQL statements
Details of background transactions
Pinpoint application errors
Stack trace of erroneous transactions
• 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
Additional insights for Java web applications
• JVM Cpu usage
• Heap & Non heap memory
• Just in time compiler
• JVM Classes count
• Garbage collection details
• Thread details
• Configuration details
JVM performance insights
JVM: Garbage collector
JVM: threads
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:
Contact : eval-apm@manageengine.com
Online Demo : demo.appmanager.com

Visibility-from web application interface to the database

  • 1.
    Applications Manager An allround on-premise application performance monitoring solution for IT Ops and DevOps
  • 2.
    Visibility: From webapplication interface to the database
  • 3.
    Week Module DateSchedule 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 timesand 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 userstypically 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
  • 7.
    Apdex score Response time Application PerformanceMonitoring: Key performance indicators Error traces Transactio n traces Slow SQL statements
  • 8.
    APM Insight forend to end visibility of your web applications Coming soon: Support for PHP and Node.js applications.
  • 9.
    APM Insight datacollection
  • 10.
    1. Application responsetimes and user satisfaction
  • 11.
  • 12.
    • Global openstandard to measure end user satisfaction • Scale of 0 to 1 • Helps identify satisfied, tolerated and frustrated users Apdex score
  • 13.
    • Response timeand response time by tiers • Throughput • Slowest transactions by response time Response time and throughput
  • 14.
    2. Identifying transactionsthat are slowing down your app
  • 15.
    • Response time •Slow business transactions • Error traces Transaction elements for performance issues
  • 16.
  • 17.
    • Individual businesstransaction 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
  • 18.
    3. Slow databasecalls preventing ideal performance
  • 19.
    • Identify slowdatabase 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
  • 20.
  • 21.
    • Find themost 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 problemsand 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 Possiblereasons: • 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 logfile 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
  • 27.
    MS SQL topqueries by CPU
  • 28.
    MS SQL Topqueries by CPU
  • 29.
    MS SQL Slowrunning queries
  • 30.
    Oracle buffer gets- Top 10 queries • Buffer Gets • Execution • Buffer Gets per Execution
  • 31.
    Oracle disk reads- Top 10 queries
  • 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 - Sessiondetails • 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 - Sessionsummary • Know sessions wait time and its corresponding event. • Track account status and user account expiry date.
  • 36.
    MS SQL -Top waits by waiting tasks
  • 37.
    MS SQL -Most blocked queries
  • 38.
    Oracle - Lock •Know which type of session lock type is being used. • Track blocked session time.
  • 39.
    4. Analysing errortraces to eliminate all performance barriers
  • 40.
    • Identify slowinternal invocations (methods) in the code and trace the execution details for URLs Pinpoint
  • 41.
    Traces to investigatetime consuming transactions
  • 43.
    Drill down toSQL statements
  • 44.
  • 45.
  • 46.
    Stack trace oferroneous transactions
  • 47.
    • Custom instrumentationallows 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
  • 48.
    Additional insights forJava web applications
  • 49.
    • JVM Cpuusage • Heap & Non heap memory • Just in time compiler • JVM Classes count • Garbage collection details • Thread details • Configuration details JVM performance insights
  • 50.
  • 51.
  • 52.
    Contact : eval-apm@manageengine.com OnlineDemo : 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:
  • 53.