Monitoring Agent for Tomcat 6.4 Fix Pack 4. Reference IBM

Transcription

1 Monitoring Agent for Tomcat 6.4 Fix Pack 4 Reference IBM

2

3 Monitoring Agent for Tomcat 6.4 Fix Pack 4 Reference IBM

4 Note Before using this information and the product it supports, read the information in Notices on page 95. This edition applies to version of the Monitoring Agent for Tomcat and to all subsequent releases and modifications until otherwise indicated in new editions. Copyright IBM Corporation 2014, US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Contents Chapter 1. Monitoring Agent for Tomcat 1 Chapter 2. Dashboards Default dashboards deepdive dashboards Group widgets for the Default dashboards Group widgets for the deepdive dashboards Custom views Chapter 3. Thresholds Predefined thresholds Customized thresholds Chapter 4. Attributes Data sets for the monitoring agent Attribute descriptions Cache data set Connector data set Counter Notifications data set CTX Counter Notifications data set CTX Gauge Notifications data set CTX Performance Object Status data set CTX Registered Monitors data set CTX String Notifications data set GarbageCollector data set GarbageCollector Runtime data set Gauge Notifications data set J2EEApplication data set J2EEApplication Runtime data set JspMonitor data set KOTCTX nodes data set Manager data set Memory data set MemoryPool data set OperatingSystem data set OperatingSystem Runtime data set Performance Object Status data set Registered Monitors data set Request Breakdown data set Request Context data set Request Distribution data set Request Instance data set Request Stack Trace data set Request Summary data set Request Trace data set RequestProcessor data set Runtime data set Server data set Servlet data set Servlet Runtime data set SessionMgr data set String Notifications data set StringCache data set Take Action Status data set Thread Pool Status data set Threading data set ThreadPool data set Tomcat Agent Configuration DD data set Tomcat Agent Configuration TT data set Accessibility features Notices Trademarks Terms and conditions for product documentation.. 97 IBM Online Privacy Statement Index Copyright IBM Corp. 2014, 2017 iii

6 iv Tomcat agent Reference

7 Chapter 1. Monitoring Agent for Tomcat The Monitoring Agent for Tomcat offers a central point of management for your Tomcat environment or application. The software provides a comprehensive means for gathering the information that is required to detect problems early and to prevent them. Information is standardized across the system. You can monitor multiple servers from a single console. By using the Tomcat agent you can easily collect and analyze Tomcat specific information. Installing and configuring the agent Install the monitoring agent on the system where the application that you want to monitor is located. For more information, see the following documentation in IBM Knowledge Center: v IBM Cloud Application Performance Management v IBM Cloud Application Performance Management, Private Copyright IBM Corp. 2014,

8 2 Tomcat agent Reference

9 Chapter 2. Dashboards Open the Application Performance Dashboard in the Cloud APM console to see a status summary of all your applications. As you drill down to dashboards for specific applications and their supporting elements, more details are available about the selected item. Use the Tomcat agent dashboards to proactively monitor your Tomcat deployment. Each dashboard page contains views with key performance indicators. When an application that includes Tomcat managed resources (also referred to as managed systems) is selected, the navigator and the Status Overview tab show Tomcat in the Components group: v Click Components to see a single Tomcat group widget that is displayed along with a group widget for every other data source type in the application. v Click the Tomcat subgroup to see a group widget for each managed resource in the application. v Click inside a Tomcat group widget or click a Tomcat managed resource from the navigator Instances section to open a dashboard with KPIs from the selected managed resource. For more information about the KPIs, click in the view or click in the dashboard banner. Default dashboards TOMCAT Use this TOMCAT Status group widget to check if the Tomcat application is running. At a glance, you can see if any of the following conditions apply to the server: v v v v v v The server is not running. The response time of requests is too slow. The JVM requires more memory. The JVM is consuming too much CPU. The amount of heap memory that is used is excessive. The rate at which requests are failing (error rate) is too high. TOMCAT Application Detail Dashboard Use this dashboard to identify trends in the performance of a selected application. You can view the average response time and throughput of all requests in the application over recent periods, as well as a table of requests. Select any request in the table to view the average response time and throughput or this particular request. TOMCAT Server GC Dashboard Use this dashboard to determine if memory leaks are occurring on the server and if the heap is poorly structured. You can view the JVM CPU usage, total heap usage, throughput, and average response over time the last 24 hours, so you can investigate the relation between application server load and heap usage. You can also view the garbage collection count and duration over a recent time period. TOMCAT Server Thread Pool Dashboard Use this dashboard to investigate the performance of thread pools and identify if any of your thread pools are not large enough to handle the load that is placed on them. You can view a graph of average thread pool size over a recent period, as well as average usage for every thread pool and a table of thread pools with further details. Select a thread pool in the table to view an average usage graph for this thread pool. Copyright IBM Corp. 2014,

10 TOMCAT Summary Dashboard Use the group widgets in this dashboard to identify how applications on the Tomcat server are performing. You can also use this dashboard to see server information, such as the server version and state. Additional group widgets These pop-up group widgets are displayed after you click a group widget for more details. Some group widgets have links to more granular information in a popup widget, described here. deepdive dashboards Request Instances This is a diagnostics dashboard. Use the Request Instances dashboard to determine if all of the request instances of a request have a problem. Remember: A time selector bar might be displayed. The time period applies to all group widgets and dashboards that are derived from historical data. The time selector does not apply to the deep-dive dashboards. Using the dashboard Determine if only some instances of a request have a problem. v v v If all of the request instances are experiencing a problem, some of the underlying code might be poorly constructed. If only some instances are experiencing the problem, locate the hot spot where the problem occurred. To drill down to the Request Traces dashboard, click View request sequence on an instance row. Request Summary This is a diagnostics dashboard. Use the Request Summary dashboard to identify in which Tomcat application segments the request spent the most time. From this dashboard, you can drill down to the request instances that took the most time. Remember: A time selector bar might be displayed. The time period applies to all group widgets and dashboards that are derived from historical data. The time selector does not apply to the deep-dive dashboards. Using the dashboard To identify which request instances resulted in a slow average response time for a specific request, complete these steps: 1. Locate a request with a slow average response time in the Request Summary table. 2. Select a request in the table to view the response time breakdown for the request. The Response Time Breakdown chart shows where the request spent the most time. 3. In the Response Time Breakdown chart, identify the request type that is taking up the most time, and click the request type. The Request Instances dashboard opens. From this dashboard, you see the request instances of this request type with the slowest response times. Request Traces This is a diagnostics dashboard. Use the Request Traces dashboard to identify the sequence of calls to nested requests and methods for a request instance. Use the dashboard to identify the root cause of a problem, if the problem relates to the code. Remember: A time selector bar might be displayed. The time period applies to all group widgets and dashboards that are derived from historical data. The time selector does not apply to the deep-dive dashboards. Using the dashboard 4 Tomcat agent Reference

11 v v v Compare the path taken by request instances that ran without a problem and request instances that performed poorly. Use the request sequence dashboard to gather information about the paths of each request instance. Depending on the input parameters, a request instance might take a different path to other instances. The difference in path taken might indicate the source of the resource issue or bottleneck. Use the stack tree to identify the nested requests or method call where the bottleneck or slow response time occurred. Use the request context to identify the specific resource that the nested request or method call was using. Additional group widgets These pop-up group widgets are displayed after you click a group widget for more details. Some group widgets have links to more granular information in a popup widget, described here. Group widgets for the Default dashboards TOMCAT Use this TOMCAT Status group widget to check if the Tomcat application is running. At a glance, you can see if any of the following conditions apply to the server: v v v v v v The server is not running. The response time of requests is too slow. The JVM requires more memory. The JVM is consuming too much CPU. The amount of heap memory that is used is excessive. The rate at which requests are failing (error rate) is too high. The following group widgets are available in this dashboard: TOMCAT Status Current Tomcat application server summary status. The following KPIs for the group widget are derived from the attributes as described: v Error Rate (%): The rate of requests that ended in errors to all requests. v Heap Used (%): The current percentage of the JVM heap used. v JVM CPU Used (%): Process CPU load. This data is derived from the ProcessCpuLoad attribute in the KOT OPERATINGSYSTEM RUNTIME data set. v JVM Memory Committed (KB): The amount of JVM committed memory. This data is derived from the JVMCommittedMem attribute in the KOT MEMORY data set. v JVM Memory Used (KB): The number of kilobytes in the heap that were in use following the garbage-collection cycle at the collection interval. This data is derived from the JVMMemUsage attribute in the KOT MEMORY data set. v Server Status: The current state of the application server. This data is derived from the statename attribute in the KOT SERVER data set. v Slowest Response Time (ms): Slowest request response time in the current interval. Transaction Volume Description needed in JSON The following KPIs for the group widget are derived from the attributes as described: v Failed requests: Is not derived directly from a single attribute. The value is calculated. v Good requests: Is not derived directly from a single attribute. The value is calculated. v Slow requests: Is not derived directly from a single attribute. The value is calculated. v Timestamp: Is not derived directly from a single attribute. The value is calculated. Chapter 2. Dashboards 5

12 TOMCAT Application Detail Dashboard Use this dashboard to identify trends in the performance of a selected application. You can view the average response time and throughput of all requests in the application over recent periods, as well as a table of requests. Select any request in the table to view the average response time and throughput or this particular request. The following group widgets are available in this dashboard: Application Requests (history) The throughput and average response time of application requests during the history period. The following KPIs for the group widget are derived from the attributes as described: v ms: Average response time (in milliseconds) during the collection interval. This data is derived from the averageresponsetime attribute in the KOT J2EEAPPLICATION RUNTIME data set. v Sample Date and Time: The local time at the agent when the data was collected. This data is derived from the Timestamp attribute in the KOT J2EEAPPLICATION RUNTIME data set. v Throughput (req/s): The throughput of requests per second during the collection interval. This data is derived from the throughput attribute in the KOT J2EEAPPLICATION RUNTIME data set. Requests (history) The throughput and average response time of requests during the history period. The following KPIs for the group widget are derived from the attributes as described: v ms: The average response time (in milliseconds) of the request during the current interval. This data is derived from the averageresponsetime attribute in the KOT SERVLET RUNTIME data set. v Sample Date and Time: The local time at the agent when the data was collected. This data is derived from the Timestamp attribute in the KOT SERVLET RUNTIME data set. v Throughput (req/s): The cumulative throughput of requests per second. This data is derived from the throughput attribute in the KOT SERVLET RUNTIME data set. Requests Summary The average response time, the number of times the requests ran, and the throughput for the specified application during the current interval. The following KPIs for the group widget are derived from the attributes as described: v Application Name: The name of the application. This data is derived from the WebModule attribute in the KOT SERVLET RUNTIME data set. v Average Response Time(ms): Average response time during the current interval. v Request Count: The number of times that the request ran during the current interval. This data is derived from the requestcount attribute in the KOT SERVLET RUNTIME data set. v URL: The URL of the request. This data is derived from the url attribute in the KOT SERVLET RUNTIME data set. TOMCAT Server GC Dashboard Use this dashboard to determine if memory leaks are occurring on the server and if the heap is poorly structured. You can view the JVM CPU usage, total heap usage, throughput, and average response over time the last 24 hours, so you can investigate the relation between application server load and heap usage. You can also view the garbage collection count and duration over a recent time period. The following group widgets are available in this dashboard: 6 Tomcat agent Reference

13 Garbage Collection Analysis The number of times the garbage collector ran during the current interval and the resulting number of objects that the collector freed. The following KPIs for the group widget are derived from the attributes as described: v Collector Name: The type of garbage collector. This data is derived from the Name attribute in the KOT GARBAGECOLLECTOR RUNTIME data set. v GC Count: The number of times that the garbage collection ran during the collection interval. This data is derived from the CollectionCount attribute in the KOT GARBAGECOLLECTOR RUNTIME data set. v GC Duration (%): The percentage of real time that the garbage collector was active during the current interval. This data is derived from the GCDuration attribute in the KOT GARBAGECOLLECTOR RUNTIME data set. v GC Duration (ms): The amount of time (in milliseconds) that garbage collection took during the collection interval. This data is derived from the CollectionTime attribute in the KOT GARBAGECOLLECTOR RUNTIME data set. v GC Rate (per min): The rate (per minute) at which the Java Virtual Machine is starting its garbage-collection routine during the current interval. This data is derived from the GCDurationPerMin attribute in the KOT GARBAGECOLLECTOR RUNTIME data set. Heap Usage (history) The size of free memory and used memory in the application server heap during the history period. The following KPIs for the group widget are derived from the attributes as described: v Free Heap (KB): The total number of free kilobytes in the heap following the garbage-collection cycle at the collection interval. This data is derived from the freekbytes attribute in the KOT MEMORY data set. v Heap Used (KB): The number of kilobytes in the heap that were in use following the garbage-collection cycle at the collection interval. This data is derived from the JVMMemUsage attribute in the KOT MEMORY data set. v Sample Date and Time: The local time at the agent when the data was collected. This data is derived from the Timestamp attribute in the KOT MEMORY data set. JVM CPU Usage (history) The number of milliseconds of CPU that was used by the JVM during a recent time period. The following KPIs for the group widget are derived from the attributes as described: v CPU Usage (%): Process CPU load. This data is derived from the ProcessCpuLoad attribute in the KOT OPERATINGSYSTEM RUNTIME data set. v Sample Date and Time: The local time at the agent when the data was collected. This data is derived from the Timestamp attribute in the KOT OPERATINGSYSTEM RUNTIME data set. JVM Garbage Collection (history) The heap usage and the length of time that the garbage collector was active during the history period. The following KPIs for the group widget are derived from the attributes as described: v GC Count: GC Count. v GC Duration (ms): GC Duration (ms). v Sample Date and Time: Sample date and time. v Sample Date and Time: Sample date and time. Chapter 2. Dashboards 7

14 Throughput and Average Response Time (history) The average response time and the throughput for the selected request during the history period. The following KPIs for the group widget are derived from the attributes as described: v Average Response Time (ms): The cumulative average response time (in milliseconds). v Sample Date and Time: Sample date and time. v Sample Date and Time: Sample date and time. v Throughput: The cumulative throughput of requests per second. TOMCAT Server Thread Pool Dashboard Use this dashboard to investigate the performance of thread pools and identify if any of your thread pools are not large enough to handle the load that is placed on them. You can view a graph of average thread pool size over a recent period, as well as average usage for every thread pool and a table of thread pools with further details. Select a thread pool in the table to view an average usage graph for this thread pool. The following group widgets are available in this dashboard: Selected Thread Pool - Current Size (history) The current thread pool size during the history period. The following KPIs for the group widget are derived from the attributes as described: v Current pool size: The current size of the thread pool during the history period. This data is derived from the currentthreadcount attribute in the KOT THREADPOOL data set. v Sample date and time: The time and date that the agent collected the data. This data is derived from the Timestamp attribute in the KOT THREADPOOL data set. Selected Thread Pool - Usage (history) Information about the usage of the thread pool during the history period. The following KPIs for the group widget are derived from the attributes as described: v Current active threads: The current number of active threads. v Maximum pool size: The configured number of threads that are allowed in the thread pool. v Sample date and time: The time and date that the agent collected the data. This data is derived from the Timestamp attribute in the KOT THREADPOOL data set. Thread Pool Usage The current number of active threads and free threads for each thread pool. The following KPIs for the group widget are derived from the attributes as described: v Current Active Threads: The current number of concurrently active threads during the current interval. This data is derived from the currentthreadsbusy attribute in the KOT THREADPOOL data set. v Current Free Threads: The number of free threads during the current interval. This data is derived from the freethreads attribute in the KOT THREADPOOL data set. v Thread Pool Name: The thread pool name. This data is derived from the name attribute in the KOT THREADPOOL data set. Thread Pools Information about the performance of each thread pool during the current interval. The following KPIs for the group widget are derived from the attributes as described: v Current Active Threads: The number of concurrently active threads during the current interval. This data is derived from the currentthreadsbusy attribute in the KOT THREADPOOL data set. 8 Tomcat agent Reference

15 v Current Pool Size: The current number of connections in use during the current interval. This data is derived from the currentthreadcount attribute in the KOT THREADPOOL data set. v Maximum Pool Size: The configured number of threads that are allowed in the thread pool. This data is derived from the maxthreads attribute in the KOT THREADPOOL data set. v Thread Pool Name: The thread pool name. This data is derived from the name attribute in the KOT THREADPOOL data set. TOMCAT Summary Dashboard Use the group widgets in this dashboard to identify how applications on the Tomcat server are performing. You can also use this dashboard to see server information, such as the server version and state. The following group widgets are available in this dashboard: Applications Applications on the Tomcat application server, sorted by average response time for the current interval. Click an application to investigate its performance using the Application Detail dashboard. The following KPIs for the group widget are derived from the attributes as described: v Application Name: Name of the application. This data is derived from the name attribute in the KOT J2EEAPPLICATION data set. v Average Response Time (ms): Average response time (in milliseconds) during the collection interval. This data is derived from the averageresponsetime attribute in the KOT J2EEAPPLICATION data set. Busiest Sessions Top 5 applications with the highest number of user sessions for every application during the current period. The following KPIs for the group widget are derived from the attributes as described: v Session Count: Number of active sessions. v SESSNAME: Application name. This data is derived from the sessname attribute in the KOT SESSIONMGR data set. JVM CPU Usage The number of milliseconds of CPU that was used by the JVM during the current monitoring period. The following KPIs for the group widget are derived from the attributes as described: v CPU Usage (%): Process CPU load. This data is derived from the ProcessCpuLoad attribute in the KOT OPERATINGSYSTEM RUNTIME data set. v Sample Date and Time: The local time at the agent when the data was collected. This data is derived from the Timestamp attribute in the KOT OPERATINGSYSTEM RUNTIME data set. JVM GC The heap usage and the length of time that the garbage collector was active during the current monitoring period. Click this group widget to determine if memory leaks are occuring on the server using the Server GC dashboard. The following KPIs for the group widget are derived from the attributes as described: v GC Duration (ms): GC Duration (ms). v Heap Used (KB): The number of kilobytes in the heap that were in use following the garbage-collection cycle at the collection interval. This data is derived from the JVMMemUsage attribute in the KOT MEMORY data set. Chapter 2. Dashboards 9

16 v Max Heap (KB): The maximum heap size set on the application server (the -Xmx JVM parameter, if specified). This data is derived from the JVMMaxMem attribute in the KOT MEMORY data set. v Sample Date and Time: The local time at the agent when the data was collected. This data is derived from the Timestamp attribute in the KOT MEMORY data set. v Sample Date and Time: Sample date and time. Requests with Slowest Response Time The top 5 requests on the application server with the slowest average response times. Attention: Click Diagnose to view the Deep Dive dashboards and group widgets for Tomcat applications. The following KPIs for the group widget are derived from the attributes as described: v Application Name: Name of the application. This data is derived from the WebModule attribute in the KOT SERVLET data set. v Average Response Time (ms): The average response time (in milliseconds) of the request during the current interval. This data is derived from the averageresponsetime attribute in the KOT SERVLET data set. v URL: The url of the request. This data is derived from the url attribute in the KOT SERVLET data set. Server Information Summary information about the Tomcat application server. The following KPIs for the group widget are derived from the attributes as described: v Address: The address of the application server host. This data is derived from the address attribute in the KOT SERVER data set. v Port: The TCP/IP port number on which the server waits for a shutdown command. This data is derived from the port attribute in the KOT SERVER data set. v Process Id: The process ID of the JVM. This data is derived from the Name attribute in the KOT RUNTIME data set. v Server Status: The current state of the application server. This data is derived from the statename attribute in the KOT SERVER data set. v ServerInfo: Tomcat server release identifier. This data is derived from the serverinfo attribute in the KOT SERVER data set. v VM Name: VM name, for example, OpenJDK 64 bit. This data is derived from the VmName attribute in the KOT RUNTIME data set. Threads The current number of active threads and free threads for each thread pool. Click this group widget to review the usage and performance of individual thread pools. The following KPIs for the group widget are derived from the attributes as described: v Current Active Threads: The current number of concurrently active threads during the current interval. This data is derived from the currentthreadsbusy attribute in the KOT THREADPOOL data set. v Current Free Threads: The number of free threads during the current interval. This data is derived from the freethreads attribute in the KOT THREADPOOL data set. v Thread Pool Name: The thread pool name. This data is derived from the name attribute in the KOT THREADPOOL data set. Additional group widgets These pop-up group widgets are displayed after you click a group widget for more details. Some group widgets have links to more granular information in a popup widget, described here. The following group widgets are available in this dashboard: 10 Tomcat agent Reference

17 Cache Hit % Displays the cache hit percentage for the modele type. The following KPIs for the group widget are derived from the attributes as described: v Cache Hit %: Hit percent. This data is derived from the hitpercent attribute in the KOT STRINGCACHE data set. v Modele Type: Type of the modeled resource. Can be set only once. This data is derived from the modelertype attribute in the KOT STRINGCACHE data set. Group widgets for the deepdive dashboards Request Instances This is a diagnostics dashboard. Use the Request Instances dashboard to determine if all of the request instances of a request have a problem. Remember: A time selector bar might be displayed. The time period applies to all group widgets and dashboards that are derived from historical data. The time selector does not apply to the deep-dive dashboards. Using the dashboard Determine if only some instances of a request have a problem. v v v If all of the request instances are experiencing a problem, some of the underlying code might be poorly constructed. If only some instances are experiencing the problem, locate the hot spot where the problem occurred. To drill down to the Request Traces dashboard, click View request sequence on an instance row. The following group widgets are available in this dashboard: Requests Instances Displays the response time for individual requests that includes their nested requests. The table is sorted by response time by default. Use the group widget to identify the request instances with the highest response time. Tip: You can drill down to view the request trace for this instance. Click View request sequence on the request row. The following KPIs for the group widget are derived from the attributes as described: v Action: Link to the Request Traces dashboard for the selected request instance. v CPU Time (ms): The time (in milliseconds) that the CPU spent in processing the request instance. This data is derived from the CPUTime attribute in the KOT REQUEST INSTANCE data set. v Request Name: The name of the request. This data is derived from the RequestName attribute in the KOT REQUEST INSTANCE data set. v Request Type: The type of request that is being run. This data is derived from the RequestType attribute in the KOT REQUEST INSTANCE data set. v Response Time (ms): The response time (in milliseconds) of the request instance. This data is derived from the ResponseTime attribute in the KOT REQUEST INSTANCE data set. v Thread ID: The ID of the thread that processed the request. This data is derived from the ThreadID attribute in the KOT REQUEST INSTANCE data set. v Timestamp: The time when the request instance was started. This data is derived from the RequestTimestamp attribute in the KOT REQUEST INSTANCE data set. Chapter 2. Dashboards 11

18 Request Summary This is a diagnostics dashboard. Use the Request Summary dashboard to identify in which Tomcat application segments the request spent the most time. From this dashboard, you can drill down to the request instances that took the most time. Remember: A time selector bar might be displayed. The time period applies to all group widgets and dashboards that are derived from historical data. The time selector does not apply to the deep-dive dashboards. Using the dashboard To identify which request instances resulted in a slow average response time for a specific request, complete these steps: 1. Locate a request with a slow average response time in the Request Summary table. 2. Select a request in the table to view the response time breakdown for the request. The Response Time Breakdown chart shows where the request spent the most time. 3. In the Response Time Breakdown chart, identify the request type that is taking up the most time, and click the request type. The Request Instances dashboard opens. From this dashboard, you see the request instances of this request type with the slowest response times. The following group widgets are available in this dashboard: Request Summary Displays an aggregated view of all requests in the Tomcat application. The requests are sorted by the average response time. The table displays the aggregated average response time and the aggregated average CPU usage for each request. Use the Request Summary table to identify which requests have a problem. Drill down into the Request Instance table to debug the problematic transactions. The following KPIs for the group widget are derived from the attributes as described: v Action: Link to the Request Instances dashboard for the selected request. v Average Response Time (ms): The average time (in milliseconds) that is required to respond to a request. This data is derived from the AvgResponseTime attribute in the KOT REQUEST SUMMARY data set. v CPU Time (ms): The average time (in milliseconds) that that the CPU spent in processing requests of a particular request type. This data is derived from the AvgCPUTime attribute in the KOT REQUEST SUMMARY data set. v End record date and time: The end date and time of the sampled period for all summary records. v Max Response Time (ms): The maximum time (in milliseconds) that is required to respond to a request. This data is derived from the MaxResponseTime attribute in the KOT REQUEST SUMMARY data set. v Min Response Time (ms): The minimum time (in milliseconds) that is required to respond to a request. This data is derived from the MinResponseTime attribute in the KOT REQUEST SUMMARY data set. v Request Count: The total number of requests of a request type. This data is derived from the RequestCount attribute in the KOT REQUEST SUMMARY data set. v Request Name: The name of the request. This data is derived from the RequestName attribute in the KOT REQUEST SUMMARY data set. v Request Type: The type of request. This data is derived from the RequestType attribute in the KOT REQUEST SUMMARY data set. v Start record date and time: The start date and time of the sampled period for all summary records. 12 Tomcat agent Reference

19 Response Time Breakdown Displays the percentage of time that the requests spent on each request type. Use this chart to see, on average, which request type consumed the most time. Tip: Click any bar on the chart to investigate the request instances for this request type. The Request Instances table shows all request instances for the selected request type. The following KPIs for the group widget are derived from the attributes as described: v Percent: The percentage of time that was spent in processing the request. This data is derived from the Percent attribute in the KOT REQUEST BREAKDOWN data set. v Request type: The type of request. This data is derived from the RequestType attribute in the KOT REQUEST BREAKDOWN data set. Response Time Distribution Displays the upper response times for percentiles of the requests. For example, if the bar at 50% shows a response time of 3000 ms, 50% of all requests were completed within 3000 ms. If the bar at 70% shows 6000 ms, 70% of all requests were completed within 6000 ms or less. Use this chart to determine what percentage of your requests have poor response times. Click any bar on the chart to investigate requests that have a response time in this percentile. For example, if the 50% bar shows a response time of 3000 ms and the 60% bar shows a response time of 4000 ms, click the 60% bar to investigate request instances with a response time between 3000 and 4000 ms. The following KPIs for the group widget are derived from the attributes as described: v Percent of request completion: The percentile value of application requests. This data is derived from the PercentileValue attribute in the KOT REQUEST DISTRIBUTION data set. v Upper-bound response time (ms): The upper-bound response time (in milliseconds) for the percentile value. This data is derived from the UpperBound attribute in the KOT REQUEST DISTRIBUTION data set. Request Traces This is a diagnostics dashboard. Use the Request Traces dashboard to identify the sequence of calls to nested requests and methods for a request instance. Use the dashboard to identify the root cause of a problem, if the problem relates to the code. Remember: A time selector bar might be displayed. The time period applies to all group widgets and dashboards that are derived from historical data. The time selector does not apply to the deep-dive dashboards. Using the dashboard v v v Compare the path taken by request instances that ran without a problem and request instances that performed poorly. Use the request sequence dashboard to gather information about the paths of each request instance. Depending on the input parameters, a request instance might take a different path to other instances. The difference in path taken might indicate the source of the resource issue or bottleneck. Use the stack tree to identify the nested requests or method call where the bottleneck or slow response time occurred. Use the request context to identify the specific resource that the nested request or method call was using. The following group widgets are available in this dashboard: Method Trace Displays a tree view of all the request instances and their nested requests. If method data was collected, calls to methods are included in this tree. Chapter 2. Dashboards 13

20 The request sequence table provides the response time and the CPU usage of request, nested request, or method call. Tip: v Use the response timeline to compare response times across requests, nested requests, and method calls. v When an event is an external call, an external call icon is displayed in the event type column. v Select any trace to filter the Request context and the Request stack trace tables for the specific request. To remove the filtering, click Clear Selection. v Expand a request in the method trace table to view subrequests that were called by the request. The following KPIs for the group widget are derived from the attributes as described: v Children: The order ID of child methods. This data is derived from the ChildrenOrderId attribute in the KOT REQUEST TRACE data set. v CPU time (ms): The time (in milliseconds) that the CPU spent in processing the method call or request. This data is derived from the CpuTime attribute in the KOT REQUEST TRACE data set. v Event Name: The name of the event. This data is derived from the EventName attribute in the KOT REQUEST TRACE data set. v Event Type: The type of event. This data is derived from the EventType attribute in the KOT REQUEST TRACE data set. v Response Time (ms): The response time (in milliseconds) of the trace method. This data is derived from the ResponseTime attribute in the KOT REQUEST TRACE data set. Request Context Displays the Tomcat context of each request. The type of information in the request context depends on the request type. When you have multiple instances of a resource in your environment, use the request context to identify which resource instance the request used. The following KPIs for the group widget are derived from the attributes as described: v Name: The parameter name in the name-value pair. This data is derived from the Key attribute in the KOT REQUEST CONTEXT data set. v Value: The parameter value in the name-value pair. This data is derived from the Value attribute in the KOT REQUEST CONTEXT data set. Request Stack Trace Displays the stack trace for the selected request or nested request. The data collector tracks the progress of a request. When a violation occurs, the data collector captures a stack trace. Use the stack trace to understand the context in which a method call was made and to identify and fix looping conditions. The following KPIs for the group widget are derived from the attributes as described: v Fully Qualified Method Name: The complete method name that includes the class name, the method name, and the relevant line number in the source. This data is derived from the FullyQualifiedMethodName attribute in the KOT REQUEST STACK TRACE data set. Additional group widgets These pop-up group widgets are displayed after you click a group widget for more details. Some group widgets have links to more granular information in a popup widget, described here. The following group widgets are available in this dashboard: 14 Tomcat agent Reference

21 Diagnose Description needed in JSON Custom views The following KPIs for the group widget are derived from the attributes as described: After you select an application that includes a Tomcat managed resource, select the Custom Views tab to create and display custom dashboard pages with attribute values from the Tomcat agent. You can quickly build monitoring pages for an application and save them for viewing by you alone or share with other users. Chapter 2. Dashboards 15

22 16 Tomcat agent Reference

23 Chapter 3. Thresholds Thresholds test for certain conditions on your managed systems, such as memory usage over 95%, and raise an event when the conditions have been met. The agent comes with predefined thresholds that you can use to monitor your Tomcat environment. You can create additional thresholds for the areas of interest. After you click System Configuration > Threshold Manager, select Tomcat as the data source type to see all the available thresholds. Predefined thresholds The thresholds are organized by the data set for which they were written. The Tomcat agent has the following predefined thresholds: KOT_KOT_AVG_RESTIME_HIGH_WARN The average response time greater than millisecond. The default configuration has the following SQL syntax: *IF *VALUE KOT_SERVLET.averageResponseTime *GT This threshold is evaluated every 1 minute. The severity of this threshold is Warning. KOT_KOT_MEMORY_USED_HIGH_CRIT The rate of memory used is larger than 90%. The default configuration has the following SQL syntax: *IF *VALUE KOT_MEMORY.heapUsed *GT 90 This threshold is evaluated every 1 minute. The severity of this threshold is Critical. KOT_KOT_MEMORY_USED_HIGH_WARN The rate of memory used is larger than 70% and less than or equal to 90%. The default configuration has the following SQL syntax: *IF *VALUE KOT_MEMORY.heapUsed *GT 70 *AND *VALUE KOT_MEMORY.heapUsed *LE 90 This threshold is evaluated every 1 minute. The severity of this threshold is Warning. KOT_KOT_PROCESS_CPU_HIGH_CRIT The process CPU load greater than 95%. The default configuration has the following SQL syntax: *IF *VALUE KOT_OPERATINGSYSTEM_RUNTIME.ProcessCpuLoad *GT 95 This threshold is evaluated every 1 minute. The severity of this threshold is Critical. KOT_KOT_PROCESS_CPU_HIGH_WARN The process CPU load greater than 80% and less than or equal to 95%. Copyright IBM Corp. 2014,

24 The default configuration has the following SQL syntax: *IF *VALUE KOT_OPERATINGSYSTEM_RUNTIME.ProcessCpuLoad *GT 80 *AND *VALUE KOT_OPERATINGSYSTEM_RUNTIME.ProcessCpuLoad *LE 95 This threshold is evaluated every 1 minute. The severity of this threshold is Warning. KOT_KOT_THPOOL_USED_HIGH_CRIT The rate of thread pool used greater than or equal to 100%. The default configuration has the following SQL syntax: *IF *VALUE KOT_THREADPOOL.threadPoolUsed *GE 100 This threshold is evaluated every 1 minute. The severity of this threshold is Critical. KOT_KOT_THPOOL_USED_HIGH_WARN The rate of thread pool used greater than 90% and less than 100%. The default configuration has the following SQL syntax: *IF *VALUE KOT_THREADPOOL.threadPoolUsed *GT 90 *AND *VALUE KOT_THREADPOOL.threadPoolUsed *LT 100 This threshold is evaluated every 1 minute. The severity of this threshold is Warning. Customized thresholds You can use the predefined thresholds as a starting point for event monitoring, and create your own thresholds as conditions arise that you want to monitor. Hover your mouse over a help icon to get user assistance for the field. Click the help tool to open the help system for the Threshold Manager help topic. The Tomcat agent has many data sets that you can use to create thresholds to monitor for specific conditions. Tip: If you are an IBM Tivoli Monitoring user, data sets are equivalent to attribute groups. 18 Tomcat agent Reference

25 Chapter 4. Attributes Attributes are the application properties that are being measured and reported by the Monitoring Agent for Tomcat. Attributes make up the key performance indicators (KPIs) that are reported, and you can use them to create thresholds for conditions that you want to monitor. About attributes Attributes are organized into data sets (also referred to as attribute groups). The values can be selectively displayed in dashboards or used to define a threshold. The most recent data sample of the attributes in the data set are used after you open a dashboard or start a threshold. Dashboards Attributes are displayed in the dashboards. The widgets specify which attribute values to request from a monitored resource. Thresholds You can define thresholds that monitor the state of your operating system, database, or application and open an event when the threshold is exceeded. You use attributes to define thresholds that describe a condition that you want to test. After the threshold is started, the values that are assigned to the attributes in the threshold definition are compared with the values collected by the Tomcat agent. After the condition is met, an event is registered and you are alerted by indicator icons in the Application Performance Dashboard navigator and the Events tab. The Tomcat agent comes with predefined thresholds that are enabled and started with the agent. If you edit a predefined threshold definition, such as to change a condition or severity, it is no longer treated as a predefined threshold but considered a custom threshold. Some attributes names display differently in the Threshold Editor, as shown in parentheses after the name, such as Object Count (OBJECT_COUNT). When the sampled values for the attributes that are referenced in a threshold meet the condition (such as attribute A is greater than 80%), an event is opened. Note the following conditions: v v v When no data can be collected for a data set, an empty result is returned (no rows of data) When a specific attribute cannot be collected, the value 0 or is returned unless otherwise specified in a particular attribute (for example, N/A ) Any numeric attribute value that is greater than the largest (positive or negative) number that can be represented by that type returns the corresponding maximum or minimum value. For example, the maximum value for a 32-bit number is 2,147,483,647. These values are displayed as text values that are defined by the data set, such as Value Exceeds Maximum or Value Exceeds Minimum. Historical data configurations The Tomcat agent collects historical data for key data sets that are shown in the dashboards. A dashboard page that includes historical views from the managed resource instance has a time selector tool for adjusting the time range. With line charts, you can also compare the values with a previous day, up to the number of days that have been saved. Numeric attributes have characteristics that are indicated in parentheses after the data type, such as (32-bit numeric property). A numeric attribute value can be 32-bit or 64-bit or some other size. The value type can be gauge, which means it varies, like a speedometer; counter, which counts and always increases; or numeric property, such as disk size. Copyright IBM Corp. 2014,

26 Additional information about attributes For a list of the data sets, a list of the attributes in each data set, and descriptions of the attributes in the Tomcat agent, see Data sets for the monitoring agent and Attribute descriptions on page 23. Data sets for the monitoring agent The Tomcat agent contains the following data sets. v Data set name: Cache Table name: KOTCACHE Historical table name: KOT_CACHE v Data set name: Connector Table name: KOTCONNECT Historical table name: KOT_CONNECTOR or KOTCONNECT v Data set name: Counter Notifications Table name: KOTCOUNTER Historical table name: KOT_COUNTER_NOTIFICATIONS or KOTCOUNTER v Data set name: CTX Counter Notifications Table name: KOTCNTCTX Historical table name: KOT_CTX_COUNTER_NOTIFICATIONS or KOTCNTCTX v Data set name: CTX Gauge Notifications Table name: KOTGAGCTX Historical table name: KOT_CTX_GAUGE_NOTIFICATIONS or KOTGAGCTX v Data set name: CTX Performance Object Status Table name: KOTCTXPOS Historical table name: KOT_CTX_PERFORMANCE_OBJECT_STATUS or KOTCTXPOS v Data set name: CTX Registered Monitors Table name: KOTREGCTX Historical table name: KOT_CTX_REGISTERED_MONITORS or KOTREGCTX v Data set name: CTX String Notifications Table name: KOTSTRCTX Historical table name: KOT_CTX_STRING_NOTIFICATIONS or KOTSTRCTX v Data set name: GarbageCollector Table name: KOTGARBAGE Historical table name: KOT_GARBAGECOLLECTOR or KOTGARBAGE v Data set name: GarbageCollector Runtime Table name: KOTGARBAG0 Historical table name: KOT_GARBAGECOLLECTOR_RUNTIME or KOTGARBAG0 v Data set name: Gauge Notifications Table name: KOTGAUGE Historical table name: KOT_GAUGE_NOTIFICATIONS or KOTGAUGE v Data set name: J2EEApplication Table name: KOTJ2EEAPP Historical table name: KOT_J2EEAPPLICATION or KOTJ2EEAPP v Data set name: J2EEApplication Runtime 20 Tomcat agent Reference

27 Table name: KOTJ2EEAP0 Historical table name: KOT_J2EEAPPLICATION_RUNTIME or KOTJ2EEAP0 v Data set name: JspMonitor Table name: KOTJSPMONI Historical table name: KOT_JSPMONITOR or KOTJSPMONI v Data set name: KOTCTX nodes Table name: KOTCTXDS Historical table name: KOT_KOTCTX_NODES or KOTCTXDS v Data set name: Manager Table name: KOTMANAGER Historical table name: KOT_MANAGER v Data set name: Memory Table name: KOTMEMORY Historical table name: KOT_MEMORY v Data set name: MemoryPool Table name: KOTMEMORYP Historical table name: KOT_MEMORYPOOL or KOTMEMORYP v Data set name: OperatingSystem Table name: KOTOPERATI Historical table name: KOT_OPERATINGSYSTEM or KOTOPERATI v Data set name: OperatingSystem Runtime Table name: KOTOPERAT0 Historical table name: KOT_OPERATINGSYSTEM_RUNTIME or KOTOPERAT0 v Data set name: Performance Object Status Table name: KOTPOBJST Historical table name: KOT_PERFORMANCE_OBJECT_STATUS or KOTPOBJST v Data set name: Registered Monitors Table name: KOTREGMONS Historical table name: KOT_REGISTERED_MONITORS or KOTREGMONS v Data set name: Request Breakdown Table name: KOTREQBRK Historical table name: KOT_REQUEST_BREAKDOWN or KOTREQBRK v Data set name: Request Context Table name: KOTREQCTX Historical table name: KOT_REQUEST_CONTEXT or KOTREQCTX v Data set name: Request Distribution Table name: KOTREQDIST Historical table name: KOT_REQUEST_DISTRIBUTION or KOTREQDIST v Data set name: Request Instance Table name: KOTREQINST Historical table name: KOT_REQUEST_INSTANCE or KOTREQINST v Data set name: Request Stack Trace Table name: KOTREQSTK Historical table name: KOT_REQUEST_STACK_TRACE or KOTREQSTK v Data set name: Request Summary Chapter 4. Attributes 21