Transaction Monitoring Version for AIX, Linux, and Windows. Reference IBM

Transcription

1 Transaction Monitoring Version for AIX, Linux, and Windows Reference IBM

2 Note Before using this information and the product it supports, read the information in Notices. This edition applies to V8.1.3 of Transaction Monitoring and to all subsequent releases and modifications until otherwise indicated in new editions. Copyright IBM Corporation 2013, US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

3 Contents About this publication v Chapter 1. Getting started Scenario: Monitoring the IBM Java application stack 5 Monitoring the IBM Java application stack... 5 Adding web applications to the Application Performance Dashboard Associating the IBM Java application stack with the web application Viewing results of IBM Java application stack monitoring Diagnosing problems in your environment Scenario: Monitoring the IBM integration stack.. 12 Monitoring the IBM integration stack Adding middleware applications to the Application Performance Dashboard Viewing results of IBM integration stack monitoring Diagnosing problems in your environment Chapter 2. Dashboards Dashboards - End User Transactions End User Transactions Summary dashboard.. 23 End User Transactions Details dashboard User Summary dashboard User Details dashboard Device Details dashboard Session Details dashboard Dashboards - Middleware Middleware Transactions Summary dashboard. 32 Middleware Transactions Details dashboard.. 33 Error Analysis dashboard Instance Analysis dashboard Dashboards - Transaction Instance Topology Transaction Instance Topology dashboard Chapter 3. Optimizing Transaction Tracking Chapter 4. Configuring the Response Time Monitoring agent Using the IBM HTTP Server Response Time module 43 Managing the IBM HTTP Server Response Time module manually Using the IBM HTTP Server Response Time module as a non-root user Using load balancers Limiting the CPU used to monitor IBM HTTP Server Using the Network Packet Analyzer Adding applications Customizing data collected by Response Time Monitoring agent Configuring applications to collect browser timing Configuring CPU overhead limit Customizing End User Transaction location values 66 Which user and session details are displayed? Chapter 5. Event thresholds for Transaction Monitoring Creating thresholds to generate events for transaction monitoring Chapter 6. Time periods Appendix A. Attributes Interaction Aggregate Data Transactions Aggregate Data WRT Transaction Status Appendix B. Dashboard metrics reference Accessibility features Notices Trademarks Terms and conditions for product documentation.. 91 IBM Online Privacy Statement Index Copyright IBM Corp. 2013, 2016 iii

4 iv Transaction Monitoring: Reference

5 About this publication This guide provides information about using the user interface. It describes how you access the workspaces for Transaction Monitoring components within the APM Console, and what information the dashboards and widgets display and what they can be used for. Intended audience This guide is for operators who use IBM Monitoring to monitor end user transactions; and IBM Application Performance Management to monitor transaction instances and middleware transactions in addition to end user transactions. Use this guide together with IBM Performance Management IBM Knowledge Center ( for a complete understanding of the following dashboard groups: v End User Transactions v Transactions, including middleware and topologies Copyright IBM Corp. 2013, 2016 v

6 vi Transaction Monitoring: Reference

7 Chapter 1. Getting started Transaction Monitoring comprises Response Time Monitoring and Transaction Tracking. Response Time Monitoring captures HTTP and HTTPS transaction data such as response times and status codes. Use Response Time Monitoring to monitor the performance and availability of web and Java applications from the browser through to the database, and to monitor mobile devices. Response Time Monitoring is available in both IBM Monitoring and IBM Performance Management. Use Transaction Tracking with middleware monitoring agents such as IBM MQ and IBM Integration Bus to monitor middleware transactions. Transaction Tracking is available only in IBM Performance Management. After you install the Response Time Monitoring agents on any web servers you want to monitor, data that is collected by these agents is displayed in the Application Performance Dashboard with little or no further configuration required. If Response Time Monitoring is the first agent you install, you are automatically prompted to add the applications that you want to monitor when you open Application Performance Dashboard. If Response Time Monitoring is not the first agent that is installed, you might need to add the applications manually. Tip: Data from the Response Time Monitoring agent is used for the End User Transactions dashboards. Data from the Response Time Monitoring agent is also used in the Application > Status Overview in the following widgets: v Requests and Response Time v Aggregate Transaction Topology. This feature is available only in IBM Application Performance Management. Copyright IBM Corp. 2013,

8 Transaction Tracking capable agents, such as Response Time Monitoring, WebSphere Applications agent, HTTP Server agent, or IBM MQ must be installed and configured for data to be displayed in the Aggregate Transaction Topology. Response Time Monitoring agents must be installed and configured for data to be displayed in the other highlighted widgets. Are my applications monitored? In the All My Applications overview, if the Transactions and Users icons are displayed, applications are being monitored and data from Response Time Monitoring is being displayed in Application Performance Dashboard. If the Transactions and Users icons are missing, no Response Time Monitoring data is available. Click Add and select the applications that you want to monitor from the list of applications that were discovered automatically. For more information, see Adding applications on page Transaction Monitoring: Reference

9 If no applications are displayed in the list of managed applications, check that the port number and HTTP and HTTPS settings are correct for your applications. For more information, see Customizing data collected by Response Time Monitoring agent on page 54. For Response Time Monitoring agents V and later, use Agent Configuration to see what versions of the agent are installed in your system and where they are installed. For more information, see Monitoring HTTP transactions on page 56. If no instances are listed for the group and the Transaction Instances widget on the End User Transactions Details page is blank, no transactions instance data is available. What's next? After you determine that your applications are being monitored, you can look at the dashboards to see whether there are any problems in your environment: Chapter 1. Getting started 3

10 v Use the End User Transactions dashboards to understand the performance and availability of transaction requests, applications, and servers in your environment v Use the Transaction Instance Topology dashboard to visualize where time is spent during a transaction instance v Use the Authenticated Users and Device Details dashboards to monitor mobile devices. How do I monitor interactions within web pages? To monitor interactions within your web pages, the JavaScript monitoring component must be added to your application. The component is either added automatically with the IBM HTTP Server Response Time module or manually. For more information, see Chapter 4, Configuring the Response Time Monitoring agent, on page 43. This information is used in the Client Total Time in the Transaction Requests and Response Time widget, in the Response Time for Client Time transactions in the Transactions - Top 10 widget, and is displayed in the Render Time Breakdown. The Render Time Breakdown widget in the End User Transactions Details page is blank if data collection from the browser is not enabled: How do I get help? Click the Help icon in a widget, page, or the menu bar to access help. Further help is available in IBM Knowledge Center and Service Management Connect. 4 Transaction Monitoring: Reference

11 Scenario: Monitoring the IBM Java application stack You can monitor and troubleshoot the IBM Java application stack to see transaction monitoring information from the browser through to the database, including resource monitoring from individual components. The IBM Java application stack includes the IBM HTTP Server, the WebSphere Application Server, and the IBM DB2 or Oracle database. Monitoring the IBM Java application stack To monitor the IBM Java application stack, install the agents that are listed for each component in the order given. Optionally, if you also want to monitor the system, install OS agents on all components. For the web server, complete the following steps: 1. Install the HTTP Server agent. Fast path: This installation also installs IBM HTTP Server Response Time module and automatically configures JavaScript injection. 2. Configure the HTTP Server agent installation. For more information, see Upgrading from V8.1.0 and configuring IBM HTTP Server Response Time module on page Install the Response Time Monitoring agent. For the application server, install the WebSphere Applications agent. For the database, install the Oracle Database agent or DB2 agent, depending on your database. Adding web applications to the Application Performance Dashboard Add the web applications that you want to monitor to the Application Performance Dashboard. Procedure To add web applications, complete the following steps: 1. In the Application Performance Dashboard, click Add Application. Chapter 1. Getting started 5

12 2. Click Read to open a list of discovered applications. 3. Select the web application that you want to monitor. 4. Click Save. Associating the IBM Java application stack with the web application Edit the web application to associate the WebSphere Application Server and database components that you want to monitor with it. Procedure To display the components in the Java application stack, complete the following steps in the Application Performance Dashboard: 1. Select the web server and click Edit Application. 2. In the Edit Application window, click Add components. 3. In the Select Component window, select WebSphere Application Server. 4. In the Component Editor, select the required component instances and click Add. Any detected WebSphere Application Server instances are automatically added to this list. 5. Click Back and repeat steps 3-4 for your database. Continue adding WebSphere Application Server and database instances until the Java application stack is complete. 6 Transaction Monitoring: Reference

13 6. Click Close, then Save to return to the Application Performance Dashboard. Results Tip: If the Aggregate Transaction Topology does not initially show the topology that you expect, wait for it to refresh and check again in a few minutes. If the topology is still not what you expect, your application might not be communicating with the expected components. Check your environment. Viewing results of IBM Java application stack monitoring You can view the results of IBM Java application stack monitoring in the topologies. About this task In the topologies, you will see transaction monitoring information from the browser to the database, including resource monitoring from individual components. The following nodes are displayed in the Aggregate Transaction Topology and Transaction Instance Topology: v Browser, displayed only when JavaScript Injection is enabled v HTTP server v WebSphere Application Server v Database Procedure You can link from nodes in the topology to more details about that node: 1. Hover your mouse over a node to display a window with additional information. 2. In that window, to drill down to a more detailed dashboard for the node, right-click the node and select the link. Chapter 1. Getting started 7

14 Aggregate Transaction Topology The Aggregate Transaction Topology is displayed in the Application summary dashboard. Aggregate Transaction topologies display the following information: v Node for browser-based clients, drill down to the end-user experience Remember: This node is displayed only when automatic JavaScript injection is measuring data from the browser. v Nodes for HTTP-based applications, drill down to the web server resource page 8 Transaction Monitoring: Reference

15 v Nodes for WebSphere Application Server based applications, drill down to an application resource page v Nodes for specific database servers, drill down to a database resource page Chapter 1. Getting started 9

16 Transaction Instance Topology Transaction instance topologies are displayed for real end-user transactions. Drill down from the End User Transactions summary through the following widgets: 1. Select a transaction in the Transactions - Top 10 table 2. Select an instance in the Transactions Instances table Transaction instance topologies display the following information: v Node for browser-based clients Remember: This node is displayed only when automatic JavaScript injection is measuring data from the browser. v HTTP nodes, including response times from the browser v WebSphere Application Server nodes, from which you can drill down to an application resource page 10 Transaction Monitoring: Reference

17 v Nodes for specific database servers, from which you can drill down to a database resource status, and SQL statement diagnostic information for JDBC requests Tip: When the topology indicates that most of the response time is spent in the database, SQL statement information is opened directly when you click Diagnose. Chapter 1. Getting started 11

18 Diagnosing problems in your environment If transaction instances for one of the components in your environment are slow or failing, the affected component is assigned an appropriate status. A node might have one of the following statuses: v Warning, the node has a yellow background and an exclamation point surrounded by a yellow triangle in the upper right corner v Critical, the node has a red background and a cross that is encircled with red in the upper right corner To identify the cause of the problems for these components, right-click the node and drill down to see more information about what might be causing the failures. Scenario: Monitoring the IBM integration stack You can monitor the IBM integration stack to see transaction tracking information for the middleware products and the services they expose and troubleshoot if any problems arise. The IBM integration stack includes IBM MQ, IBM Integration Bus, and DataPower appliance. Monitoring the IBM integration stack To monitor the IBM integration stack, install the agents that are listed for each component in the order given. Optionally, if you also want to monitor a system, install OS agents on that system. For IBM MQ, complete the following steps: 1. Install the Monitoring Agent for WebSphere MQ. 2. Configure the WebSphere MQ agent to connect to the queue manager. 3. Enable MQ Application Activity Trace in the queue manager. For IBM Integration Bus, complete the following steps: 12 Transaction Monitoring: Reference

19 1. Install the Monitoring Agent for IBM Integration Bus. 2. Enable IBM Integration Bus for transaction tracking. 3. Configure transaction tracking for the required IBM Integration Bus agent instances. For DataPower appliance, complete the following steps: 1. Install the Monitoring Agent for DataPower. 2. Configure the DataPower agent to connect to the DataPower appliance. 3. Ensure that transaction tracking is enabled for the required DataPower agent instances. 4. Set up the DataPower appliance. Adding middleware applications to the Application Performance Dashboard Create an IBM integration stack application and add the IBM MQ, IBM Integration Bus, and DataPower appliance instances that you want to monitor to it. Procedure To display the components in the IBM integration stack, complete the following steps in the Application Performance Dashboard: 1. In the Application Performance Dashboard, click Add Application. 2. In the Edit Application window, add an application name and click Add components. 3. In the Select Component window, select IBM Integration Bus. 4. In the Component Editor, select the required component instances and click Add. Any detected IBM Integration Bus instances are automatically added to this list. 5. Click Back and repeat steps 3-4 for WebSphere MQ and DataPower Appliance. Continue adding IBM Integration Bus, IBM MQ, and DataPower appliance instances until the IBM integration stack is complete. Chapter 1. Getting started 13

20 6. Click Close, then Save to return to the Application Performance Dashboard. Results Tip: If the Aggregate Transaction Topology does not initially show the topology that you expect, wait for it to refresh and check again in a few minutes. If the topology is still not what you expect, there might be a problem with your application not communicating with the expected components. Check your environment. Viewing results of IBM integration stack monitoring You can view the results of IBM integration stack monitoring in the topologies and middleware pages. You can also view events that are generated when a transaction violates a defined threshold. About this task In the topologies, you can see interactions between middleware components. The following middleware nodes are displayed in the Aggregate Transaction Topology and Transaction Instance Topology: v IBM Integration Bus v IBM MQ v DataPower appliance Hover your mouse over a node to display a Properties window that shows you information to explain why a node has a particular status. The status is determined by situations; the situations with a bad status are displayed. Procedure You can link from nodes in the topology to more details about that node: 1. Right-click a node. 14 Transaction Monitoring: Reference

21 2. Optional: Select Go to Component page to display information about the component. 3. Optional: Select Go to Transaction Summary page to display information about the middleware transactions. Tip: Select Groups > Components > middleware component in the navigator and select a request period in the volume widget to go to the same dashboard. Aggregate Transaction Topology The Aggregate Transaction Topology is displayed in the Application summary dashboard. Aggregate Transaction topologies display IBM MQ, IBM Integration Bus, and DataPower appliance nodes. Drill down from these nodes to more information about the middleware integration stack. To drill down, right-click a middleware node in the Aggregate Transaction Topology and select Go to Transaction Summary page. Alternatively, select Chapter 1. Getting started 15

22 Groups > Components > middleware component in the navigator and select a request period in the volume widget to access the same information. Middleware transaction details From the middleware Transactions Summary page, you can drill down to middleware transaction details. To drill down to middleware transaction details, complete the following steps: 16 Transaction Monitoring: Reference

23 1. In the middleware Transactions Summary page, select a monitoring interval in the Message or Volume chart. 2. On the Middleware Transaction Summary, in the Queues, Brokers, or Appliances widget, select a queue or broker. Analyzing errors and instances From the middleware Transactions Details page, you can drill down further to information that helps you to analyze errors and instances and access the Transaction Instance topology. To drill down to errors and instances for middleware components and then to the Transaction Instance Topology, on the Transaction Details page complete one of the following steps: v Click Analyze Errors to display the Error Analysis page, then select an error. Chapter 1. Getting started 17

24 18 Transaction Monitoring: Reference v Click Analyze Requests to display the Instance Analysis page, then select an instance.

25 Alternatively, in the Transaction Details page, select an error or an instance to go directly to the Transaction Instance Topology. Transaction instance topologies display the following middleware nodes: v Message queue managers v IBM Integration Bus brokers Chapter 1. Getting started 19

26 v DataPower Appliances Select a node to display its properties that explain why a node has a particular status. A Transaction Gantt Chart is displayed for the selected queue or broker. The Gantt chart helps you isolate the most significant contributors to the overall response time of the transaction. Events Events are generated for the IBM integration stack by the default Transaction Tracking thresholds. For example, the default Transaction_Time_Critical threshold generated an event, which is shown on the Events tab. For more information about default events, see Chapter 5, Event thresholds for Transaction Monitoring, on page 69. You can add thresholds to create more events, for example for transaction rates that slow or fall below a certain threshold. For more information about adding events, see Creating thresholds to generate events for transaction monitoring on page 71. Diagnosing problems in your environment If transaction instances for one of the components in your environment are slow or failing, the affected component is assigned an appropriate status. A node might have one of the following statuses: v Warning, the node has a yellow background and an exclamation point surrounded by a yellow triangle in the upper right corner 20 Transaction Monitoring: Reference

27 v Critical, the node has a red background and a cross that is encircled with red in the upper right corner To identify the cause of the problems for these components, right-click the node and drill down to see more information about what might be causing the failures. Chapter 1. Getting started 21

28 22 Transaction Monitoring: Reference

29 Chapter 2. Dashboards If they are available in your installation, use the Response Time Monitoring and Transaction Tracking dashboards to understand the performance and availability of transaction requests, applications, and servers, where time is spent during a transaction instance in your environment, and to monitor mobile devices. Dashboards - End User Transactions End User Transactions dashboards might be available in your installation. Use these dashboards to understand the performance and availability of applications in your environment. Tip: Data for the End User Transactions dashboards is provided by the Response Time Monitoring agent. To display End User Transactions dashboards, select Groups > Transactions > End User Transactions in the navigator. Use the Events tab to view the active events that relate to the Response Time Monitoring agent for the selected application. Each dashboard contains several group widgets. To view group widget help, click the help icon ( ) on the group widget. End User Transactions Summary dashboard Use the End User Transactions Summary dashboard to analyze the status of the transactions for the selected application over the selected history period, and identify the poorest performing transactions. For IBM Application Performance Management, you can also see user and session counts, and identify the poorest performing users and devices. Using the dashboard Tip: Data for the End User Transactions dashboards is provided by the Response Time Monitoring agent. The following image of the End User Transactions summary dashboard shows widgets available in IBM Monitoring highlighted in the smaller area (blue), which are a subset of the widgets available in IBM Application Performance Management. Copyright IBM Corp. 2013,

30 In IBM Application Performance Management, view user information and failures. Look at the three smaller widgets: Users and Sessions, Worst by User - Top 5, and Worst by Device - Top 5. Together these widgets show how many users are using an application, the five users who are experiencing the highest percentage of failures, and the five devices with the highest percentage of failures. The Users and Sessions widget also shows the number of unique users and sessions during the selected period. Click Analyze Users in the Users and Sessions widget to display a User Summary. View the number of good transactions for the application. Look at the bar chart in the Requests and Response Time widget to compare the number of good (green), slow (yellow), and failed (red) transactions for the selected application over the last hour. View the average response times of transactions for the selected application. In the Requests and Response Time, also look at the Server Response Time line to see the average response time for transactions from the server side. Look at the Client Total Time line to see the real experience of the user. This line represents the client-side response time, including JavaScript transactions. Use these lines together with the bar chart to identify any trends. View the transactions in the application identified as of most interest. Look at the transactions in the Transactions - Top 10 table. These transactions are those that create a poor user experience, and therefore are of the highest priority. In IBM Monitoring, notice client time transactions that show the response time as measured by the client's browser, and are a result of JavaScript monitoring. Select a transaction to display details about its instances. 24 Transaction Monitoring: Reference

31 Group widgets The End User Transactions summary dashboard shows the following group widgets: v Users and Sessions, only in IBM Application Performance Management v Worst by User - Top 5, only in IBM Application Performance Management v Worst by Device - Top 5, only in IBM Application Performance Management v Requests and Response Time v Transactions - Top 10 To view group widget help, click the help icon ( ) on the group widget. Metrics The following table summarizes the information available in each widget. Not all widgets are available in all offerings. Group widget Users and Sessions Not available in IBM Monitoring. Worst by User - Top 5 Not available in IBM Monitoring. Worst by Device - Top 5 Not available in IBM Monitoring. Data set from which data is derived F_TRANSACTION_USER_AGG_DATA F_TRANSACTION_USER_AGG_DATA F_TRANSACTION_USER_AGG_DATA Metrics Users Sessions Percentage Failures Percentage Failures Requests and Response Time WRT Transaction Status Overall Volume Server Response Time Client Total Time Transactions - Top 10 WRT Transaction Status Failed Slow Transaction Volume Response Time End User Transactions Details dashboard Use the End User Transactions Details dashboard to analyze the performance and availability of the selected transaction. For IBM Application Performance Management, you can also analyze the transaction instances for the selected transaction, and drill down to a topology of a selected instance. Using the dashboard Tip: Data for the End User Transactions dashboards is provided by the Response Time Monitoring agent. View the number of good subtransactions for the transaction on the selected server. Look at the bar chart in the Transaction Requests and Response Time Chapter 2. Dashboards 25

32 widget to compare the number of good (green), slow (yellow), and failed (red) subtransactions for the selected transaction. View the average response times of subtransactions for the selected application. In the Transaction Requests and Response Time widget, also look at the Server Response Time line to see the average response time for subtransactions other than those subtransactions that use JavaScript from the server side. Look at the Client Total Time line to see the real experience of the user. This line represents the client-side response time, including JavaScript transactions. Use these lines together with the bar chart to identify any trends. View the total time that is taken to load a web page as experienced by a user. Look at the chart in the Render Time Breakdown widget to see which parts within the web page take the longest time to load from a user perspective. Timing points are described by the W3C Navigation Timing specification. Restriction: For Response Time Monitoring to collect data from the browser, JavaScript monitoring code must be injected into the pages you want to monitor. If JavaScript monitoring is not enabled in your environment, this widget shows data only if the IBM HTTP Server Response Time module is installed. If neither JavaScript monitoring nor IBM HTTP Server monitoring with IBM HTTP Server Response Time module are enabled, this widget does not display any information. View the status of the server. Look at the Runs On table and check the status of the web server. View how subtransactions within the page are performing. Look at the Subtransactions table to see how interactions within a page, such as Ajax requests are performing. For example, check that the add to cart request is working as required. In IBM Application Performance Management, view how long it takes to load a page. Look at the Transaction Instances table to see the actual response times experienced by the end user, including render time. Select a transaction instance to view a topology of the instance broken down into network hops and subtransaction nodes. Group widgets The End User Transactions details dashboard shows the following group widgets: v Transaction Requests and Response Time v Render Time Breakdown v Runs On v Subtransactions v Transaction Instances, only in IBM Application Performance Management To view group widget help, click the help icon ( ) on the group widget. 26 Transaction Monitoring: Reference

33 Metrics Group widget Transaction Requests and Response Time Data set from which data is derived WRT Transaction Status Metrics Render Time Breakdown WRT Transaction Status Resolve Runs On WRT Transaction Status Failed Transaction Volume Server Response Time Client Total Time Page Transfer Content Loading Browser Load Slow Subtransactions WRT Transaction Status Type Transaction Instances Not available in IBM Monitoring. Mongo Interesting Instances Failed Slow Transaction Volume Response Time Status Response Time Source User Agent User Name User Summary dashboard Use the User Summary dashboard to analyze end user transactions by location. Understand who is accessing your application, and if users are experiencing problems, understand the scope of problems and who is impacted. Using the dashboard Tip: Data for this dashboard is provided by the Response Time Monitoring agent. Analyze end user transactions by location. Look at the Users by Location widget. You can see the locations that are experiencing the most transaction failures. Select a location to display user, session, and device details in the other widgets to help you can understand the problem. For the selected location, view the users and their details. Look at the Users at Selected Location widget to see the users at the location selected in the Users by Location widget. For each user, you can see the percentage of failed and slow transactions, the volume of transactions and the average response time of those transactions. Users experiencing problems are listed first. Click a user to go to the User Details Chapter 2. Dashboards 27

34 widget to see more details. You can also see the session count, and in the Users and Sessions at Selected Location widget, the number of users over time and unique user count. For the selected location, view the worst sessions and their details. Look at the User Sessions at Selected Location - Top 10 widget to see the sessions with the highest percentage of failures or slow transactions at the location selected in the Users by Location widget. For each session, you can also see the user affected, on which operating system and the user's IP address and port number. Click a session to go to the Session Details widget to see more details. You can also see the number of transaction requests per session, and in the Users and Sessions at Selected Location widget, the number of sessions over time and unique session count. Group widgets The Users Summary dashboard shows the following group widgets: v Users by Location v Users and Sessions at Selected Location v Users at Selected Location v User Sessions at Selected Location - Top 10 To view group widget help, click the help icon ( ) on the group widget. Metrics Group widget Table from which data is derived Metrics Users by Location F_TRANSACTION_USER_AGG_DATA Location Users and Sessions at Selected Location F_TRANSACTION_USER_AGG_DATA Failed Slow Users Sessions Response Time Users Sessions Users at Selected Location F_TRANSACTION_USER_AGG_DATA Users Failed Slow Sessions Volume Response Time 28 Transaction Monitoring: Reference

35 Group widget User Sessions at Selected Location - Top 10 Table from which data is derived F_TRANSACTION_DATA Metrics Start Time Users Failed Slow Volume Duration Device OS Location User Details dashboard Use the User Details dashboard to view load and response time for each user to discover who is having problems. Using the dashboard Tip: Data for the End User Transactions dashboards is provided by the Response Time Monitoring agent. Check the performance of the application in serving requests of the user. Look at the User Request and Response Time graph to see how many of the requests that are generated by the user failed (red), took too long to process (yellow), and completed successfully (green) over a recent period. Notice any trends with the average response time. View session information Look at the User Sessions - Top 10 table to see details of the sessions for the selected user. A session is measured from when a user of an operating system logs in to an application until they log out, or the session times out. Tip: Select a row to display session details. Group widgets The User Details dashboard shows the following group widgets: v User Request and Response Time v User Sessions - Top 10 To view group widget help, click the help icon ( ) on the group widget. Metrics Group widget User Request and Response Time Table from which data is derived F_TRANSACTION_USER_AGG_DATA Metrics Request Status Average Response Time Chapter 2. Dashboards 29

36 Group widget Table from which data is derived Metrics User Sessions - Top 10 F_TRANSACTION_DATA Start Time Duration Failed Slow Requests Device OS Location Device Details dashboard Use the Device Details dashboard to analyze the load created by devices that run a particular operating system, and the server performance on this load. Using the dashboard Tip: Data for the End User Transactions dashboards is provided by the Response Time Monitoring agent. View the performance of the application server that serves device requests. Look at the Device Request and Response Time graph to see how many of the requests that are generated by mobile devices failed (red), took too long to process (yellow), or completed successfully (green). Notice any trends with the average response time. View session information Look at the Device Sessions - Top 10 table to see details of the sessions for the selected operating system. A session is measured from when a user of an operating system logs in to an application until they log out, or the session times out. Tip: Select a row to display session details. Group widgets The Device Details dashboard shows the following group widgets: v Device Request and Response Time v Device Sessions - Top 10 To view group widget help, click the help icon ( ) on the group widget. Metrics Group widget Device Request and Response Time Table from which data is derived F_TRANSACTION_USER_AGG_DATA Metrics Request Status Average Response Time 30 Transaction Monitoring: Reference

37 Group widget Table from which data is derived Metrics Device Sessions - Top 10 F_TRANSACTION_DATA Start Time Duration Failed Slow Requests User Location Session Details dashboard Use the Session Details dashboard to view transaction requests and instances for the selected operating system or user. Using the dashboard Tip: Data for the Session Details dashboards is provided by the Response Time Monitoring agent. Tip: A session is measured from when a user of an operating system logs in to an application until they log out, or the session times out. View request information for the session Look at the Session Requests chart to see details of the number of requests over the length of the selected session. View transaction instance information for the session Look at the Session Instances table to see details of the transaction instances for the session. Click transactions experiencing problems to open a transaction instance topology from where you can drill down further to diagnose the root cause of the problem. Group widgets The Session Details dashboard shows the following group widgets: v Session v Session Requests v Session Instances To view group widget help, click the help icon ( ) on the group widget. Chapter 2. Dashboards 31

38 Metrics Group widget Table from which data is derived Metrics Session F_TRANSACTION_DATA Start Time Duration Failed Slow Requests User Device OS Session Requests F_TRANSACTION_DATA Request status Session Instances Transaction Instances Transaction Status Status Code Response Time Source Server Dashboards - Middleware The IBM integration stack middleware dashboards might be available in your installation. Use these dashboards to see transaction tracking information for the middleware products and the services they expose and troubleshoot if any problems arise. The IBM integration stack includes IBM MQ, IBM Integration Bus, and DataPower appliance. To display the middleware dashboards, select Components > middleware component in the navigator. In the Volume widget, select a monitoring interval to display the first of the middleware dashboards. Middleware Transactions Summary dashboard Use the Middleware Transactions Summary dashboard to view information about all transactions running across all instances of the selected middleware component, either IBM MQ, IBM Integration Bus, or DataPower appliance. 32 Transaction Monitoring: Reference Using the dashboard View the message or transaction volume. Look at the Message or Transaction Volume chart. The number of transactions or messages across all middleware instances are plotted for each period, together with the number of good, or failed transactions or messages. View the worst performing middleware instances. The middleware instances are listed in the Queues or Transactions table. Click a middleware instance to display details of the transactions or message queues for that instance. View information about the resource node and the services that it depends on. The Service Dependencies shows the resource node, such as an IBM Integration Bus and the services that it depends on, identified by

39 hostname:port. Service nodes are always displayed as uninstrumented services. The response time for each service is shown on the link. Hover your cursor over a node to display more information about that node. For uninstrumented services, the average transaction response and render times over each interval are also displayed. Group widgets The Middleware Transactions Summary dashboard shows the following group widgets: v Message or Transaction Volume v Queues or Transactions v Service Dependencies Metrics Group widget Message or Transaction Volume Table from which data is derived TRANSACTION AGG DATA Metrics Good requests Slow requests Failed requests Queues or Transactions TRANSACTION AGG DATA Transaction Service Dependencies Average Response Time Transaction Volume Failed Slow Middleware Transactions Details dashboard Use the Transactions Details dashboard to view information about a specific transaction or message for the selected middleware component, either IBM MQ, IBM Integration Bus, or DataPower appliance. Using the dashboard View a summary of response time and request volume for a transaction or message and compare the execution time with the wait time. Look at the response time summary. The average response time for the transaction or message requests and the percentage of requests that are failed or slow are shown. If these values are high, investigate any errors. Look at the transaction or message request volume chart (first chart in the Messages or Transactions widget). The total number of requests for the selected transaction or message are plotted for each period, and the failed requests are shown in red. Look at the response time chart (second chart in the Messages or Transactions widget). The time that is taken for the requests to execute (Execution Time) and the time spent waiting on service dependencies (Wait Time) are plotted. View information about the resource node and the transactions for its dependent services. The Transaction Dependencies shows the resource node, such as an IBM Chapter 2. Dashboards 33

40 Integration Bus and the transactions for the services that it depends on. Service nodes are always displayed as uninstrumented services. The response time for each service transaction is shown on the link. Hover your cursor over a node to display more information about that node. For uninstrumented services, properties and the average transaction response and render times are displayed for each interval. View the users for, and hosts of the selected application. The Users - Top 5 and Requestors - Top 5 widgets show which users are having the worst experience, and which client is using the application the most. Click a user or host to display only those instances in the Latest Errors and Latest Requests tables that relate to that user or host. Troubleshoot transaction or message request errors Look at the Latest Errors table. The most recent errors for the transactions or messages on the selected middleware instance are listed. Click an error to see the transaction in context in the Transaction Instance Topology. Click Analyze Errors to troubleshoot the errors. Troubleshoot latest transaction requests or messages Look at the Latest Requests table. The most recent requests for the transactions or messages on the selected middleware instance are listed. Select a request to display a transaction instance topology and Gantt chart for that request. Click a request to see it in context in the Transaction Instance Topology. Click Analyze Requests to troubleshoot failed requests. Group widgets The Transactions Details dashboard shows the following group widgets: v Messages or Transactions v Transaction Dependencies v Users - Top 5 v Requestors - Top 5 v Latest Errors v Latest Requests Metrics Group widget Table from which data is derived Metrics Messages or Transactions TRANSACTION AGG DATA Good requests Transaction Dependencies - - Slow requests Failed requests Execution Time Wait Time Response Time Volume Failed Slow Users - Top 5 TRANSACTION AGG DATA Users Average Response Time 34 Transaction Monitoring: Reference

41 Group widget Table from which data is derived Metrics Requestors - Top 5 TRANSACTION AGG DATA Host Volume Latest Errors TransactionInstances Error Code Error Description Latest Requests TransactionInstances Component Name Status Response Time Error Analysis dashboard Use the Error Analysis dashboard to view details about specific errors for the selected middleware component, either IBM MQ, IBM Integration Bus, or DataPower appliance as they occur over time. Using the dashboard View the error rate over time. Look at the Error Rate chart. If you have been experiencing problems, isolate the time period, or notice any increases in errors. View error codes and descriptions. Look at the Error Details widget. The most recent errors in the middleware transaction requests are listed together with an error message and the time at which the error occurred. Group widgets The Error Analysis dashboard shows the following group widgets: v Error Rate v Error Details Metrics Group widget Table from which data is derived Metrics Error Rate TRANSACTION AGG DATA Total Error Details TransactionInstances Error Code Error Message Chapter 2. Dashboards 35

42 Instance Analysis dashboard Use the Instance Analysis dashboard to view details about errors in specific transaction instances for the selected middleware transaction request, either IBM MQ, or IBM Integration Bus, as they occur over time. Using the dashboard View the error rate over time. Look at the Transaction Volume chart. If you have been experiencing problems, isolate the time period, or notice any increases in errors. View error codes and response times. Look at the Instance Details widget. The most recent errors in the middleware transaction request are listed together with time at which the error occurred and the impact to the response time. Tip: Select an instance to display the Transaction Instance topology. Group widgets The Instance Analysis dashboard shows the following group widgets: v Transaction Volume v Instance Details Metrics Group widget Table from which data is derived Metrics Transaction Volume TRANSACTION AGG DATA Failed requests Instance Details TRANSACTION AGG DATA Status Response Time Dashboards - Transaction Instance Topology The Transaction Instance Topology dashboard might be available in your installation. Use this dashboard to visualize where time is spent during a transaction instance. Use the Transaction Instance Topology to view summary information about, and a topology for the selected transaction instance. You can drill down to the Transaction Instance Topology through End User Transactions, or middleware dashboards. For example, in the navigator, select Groups > Transactions > End User Transactions. In the Transaction Summary page, select a transaction in the Transactions - Top 10 table, and then a transaction instance in the Transaction Instances table. 36 Transaction Monitoring: Reference

43 Transaction Instance Topology dashboard Use the Transaction Instance Topology dashboard to analyze a transaction instance. Using the dashboard View summary information for the transaction instance. Look at the Transaction Instances summary table for details about the transaction instance. View where time is spent during a transaction instance. Look at the Transaction Instance Topology. The topology shows each network hop and subtransaction node in the transaction instance. The time that is taken for each hop is shown on the link between nodes. View the status of each subtransaction. Look at the Transaction Instance Topology. The status for each subtransaction node is shown in the icon. Where a request has failed, the node is highlighted in red, and the status shows the failure with a cross. View information about each node. Select a node in the Transaction Instance Topology. Details about that node are displayed in the Node Properties, Server Status, or Transaction Gantt Chart widgets. Identify the root cause of a problem for nodes that have a status of warning or failed. In the Node properties widget, click Diagnose: v v If deep-dive diagnostics are available, and there is a matching instance, further information is displayed If a deep-dive does not have a matching instance, choose an instance from a list of other instances for the same transaction, on the same server instance, at a sampled time within a few minutes of the requested instance. Further information is displayed for this alternative instance. v For IBM Java application stack monitoring, depending on the node you can drill down further to application resource pages or database resource status, and SQL statement diagnostic information. Group widgets The Transaction Instance Topology dashboard shows the following group widgets: v Transaction Instances v Transaction Instances Topology v Node Properties v Server Status v Transaction Gantt Chart To view group widget help, click the help icon ( ) on the group widget. Limitations of the topology For transactions with URLs longer than 254 characters (excluding query strings), the transaction topology does not show a node for the back-end application server, such as WebSphere Portal Server, when you drill down from the Transaction Instances table. Chapter 2. Dashboards 37

44 Metrics Group widget Table from which data is derived Metrics Transaction Instances Transaction Instance Status Response Time Source User Agent User Name Node Properties Transaction Instance Transaction Response Time Component Name Host Name Server Status Transaction Gantt Chart TXINSGANTT_STATUS Transaction Status Timeline Icons and values for nodes in topologies The icons and values that are displayed for each node in the Aggregate Transaction Topology and the Transaction Instance Topology are determined by the source of the data for each node. Table 1. Icons and values for nodes in topologies Node type Value on the node Description Icon Browser BROWSER, IPAddress, or client name Source node for browser-based clients, displayed only when automatic JavaScript injection is measuring data from the browser. For example, BROWSER or /daytrader/app HTTP Server Transaction Name Nodes for HTTP-based applications. For example,/ PlantsByWebSphereAjax/index.html/ Client IPAddress, or client name Nodes for clients. For example, /daytrader/app WebSphere Application Server node Application name Nodes for WebSphere Application Server based applications. For example, /daytrader/app 38 Transaction Monitoring: Reference