Monitoring Agent for Microsoft.NET - BETA Version 1.2. User's Guide SC

Transcription

1 Monitoring Agent for Microsoft.NET - BETA Version 1.2 User's Guide SC

2

3 Monitoring Agent for Microsoft.NET - BETA Version 1.2 User's Guide SC

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

5 Contents About this publication v Intended audience v Publications v Application Performance Diagnostics library.. v Related publications v Accessing terminology online vi Accessing publications online vi Ordering publications vi Accessibility vii Application Performance Management community on Service Management Connect vii Tivoli technical training vii Tivoli user groups vii Support information vii Conventions used in this publication..... viii Typeface conventions viii Operating system-dependent variables and paths viii Chapter 1. Overview Chapter 2. Starting the Application Performance Management console... 3 Chapter 3. Application Performance Management console Navigating to the diagnostics dashboards Chapter 6. Diagnostics dashboards.. 11 MS.NET Deep Dive Component dashboard MS.NET Deep Dive Request Summary dashboard Request Summary Response Time Breakdown Response Time Distribution Request Instances dashboard Request Instances Request Traces dashboard Method Trace Request Context Request Stack Trace Chapter 7. Troubleshooting dashboard data display problems Appendix. Accessibility Index Trademarks Notices Privacy policy considerations Chapter 4. Configuration pages Chapter 5. Configuring the Monitoring Agent for Microsoft.NET Configuring event thresholds Copyright IBM Corp iii

6 iv Monitoring Agent for Microsoft.NET: User's Guide

7 About this publication Intended audience Publications This publication provides information about using the agent to monitor Microsoft.NET framework applications. This publication is for personnel who use the Monitoring Agent for Microsoft.NET to monitor.net Framework applications. Users of this publication must be familiar with the following topics: v Monitoring concepts v Cloud computing concepts and management of the provisioning system in the environment v Administration basics for the operating system on the monitored servers This section lists publications in the product library and related documents. It also describes how to access Tivoli publications online and how to order Tivoli publications. Application Performance Diagnostics library The following publications are included in the Application Performance Diagnostics library, available on the IBM web site: v Monitoring Agent for Microsoft.NET Installation and Configuration Guide Provides the planning information and procedures you need to install and configure Monitoring Agent for Microsoft.NET, including the agent and the support files for the infrastructure node. v Monitoring Agent for Microsoft.NET User's Guide Provides the information on diagnosing.net framework applications using the Monitoring Agent for Microsoft.NET. v Monitoring Agent for Microsoft.NET Installation and Configuration Guide Provides the planning information and procedures you need to install and configure Agent for WebSphere Applications, including the agent and the support files for the infrastructure node. v Monitoring Agent for WebSphere Applications User's Guide Provides the information on monitoring and diagnosing application servers using Agent for WebSphere Applications. Reference and troubleshooting information for Application Performance Diagnostics is available on Service Management Connect. Related publications The following documentation also provides useful information: v IBM Tivoli Documentation Central: Copyright IBM Corp v

8 v v Information about IBM Tivoli Documentation is provided on the following website: IBM SmartCloud Monitoring - Application Insight Information about IBM SmartCloud Monitoring - Application Insight is provided on the following website: %2Fcom.ibm.scmai.doc_1.2%2Fwelcome.htm IBM SmartCloud Application Performance Management UI: The IBM SmartCloud Application Performance Management User Interface User's Guide is available from the IBM SmartCloud Application Performance Management information center at the following URL: %2Fcom.ibm.apm.doc_7.7%2Fapm_ui_docs%2Fapmui_77 %2Ffac_landing_user.html Accessing terminology online The IBM Terminology website consolidates the terminology from IBM product libraries in one convenient location. You can access the Terminology website at Accessing publications online The documentation DVD contains the publications that are in the product library. The format of the publications is PDF, HTML, or both. IBM posts publications for this and all other Tivoli products, as they become available and whenever they are updated, to the Tivoli Documentation Central website at Important: If you print PDF documents on other than letter-sized paper, set the option in the File Print window that allows Adobe Reader to print letter-sized pages on your local paper. Ordering publications You can order many Tivoli publications online at: You can also order by telephone by calling one of these numbers: v In the United States: v In Canada: In other countries, contact your software account representative to order Tivoli publications. To locate the telephone number of your local representative, perform the following steps: 1. Go to 2. Select your country from the list and click Go. 3. Click About this site in the main panel to see an information page that includes the telephone number of your local representative. vi Monitoring Agent for Microsoft.NET: User's Guide

9 Accessibility Accessibility features help users with a physical disability, such as restricted mobility or limited vision, to use software products successfully. With this product, you can use assistive technologies to hear and navigate the interface. You can also use the keyboard instead of the mouse to operate all features of the graphical user interface. For additional information, see Accessibility, on page 21. Application Performance Management community on Service Management Connect Tivoli technical training Connect, learn, and share with Service Management professionals: product support technical experts who provide their perspectives and expertise. Access Service Management Connect at servicemanagement/apm/index.html. Use Service Management Connect in the following ways: v v v v Tivoli user groups Support information Become involved with transparent development, an ongoing, open engagement between other users and IBM developers of Tivoli products. You can access early designs, sprint demonstrations, product roadmaps, and prerelease code. Connect one-on-one with the experts to collaborate and network about Tivoli and the (enter your community name here) community. Read blogs to benefit from the expertise and experience of others. Use wikis and forums to collaborate with the broader user community. For Tivoli technical training information, refer to the following IBM Tivoli Education website: Tivoli user groups are independent, user-run membership organizations that provide Tivoli users with information to assist them in the implementation of Tivoli Software solutions. Through these groups, members can share information and learn from the knowledge and experience of other Tivoli users. For more information about Tivoli Users Group, see If you have a problem with your IBM software, you want to resolve it quickly. IBM provides the following ways for you to obtain the support you need: Online Access the IBM Software Support site at support/probsub.html. About this publication vii

10 Troubleshooting reference For more information about resolving problems, see the troubleshooting reference information in Service Management Connect. Conventions used in this publication This publication uses several conventions for special terms and actions, operating system-dependent commands and paths, and margin graphics. Typeface conventions This publication uses the following typeface conventions: Bold v Lowercase commands and mixed case commands that are otherwise difficult to distinguish from surrounding text v Interface controls (check boxes, push buttons, radio buttons, spin buttons, fields, folders, icons, list boxes, items inside list boxes, multicolumn lists, containers, menu choices, menu names, tabs, property sheets), labels (such as Tip:, and Operating system considerations:) v Keywords and parameters in text Italic v Citations (examples: titles of publications, diskettes, and CDs v Words defined in text (example: a nonswitched line is called a point-to-point line) v Emphasis of words and letters (words as words example: "Use the word that to introduce a restrictive clause."; letters as letters example: "The LUN address must start with the letter L.") v New terms in text (except in a definition list): a view is a frame in a workspace that contains data. v Variables and values you must provide:... where myname represents... Monospace v Examples and code examples v File names, programming keywords, and other elements that are difficult to distinguish from surrounding text v Message text and prompts addressed to the user v Text that the user must type v Values for arguments or command options Operating system-dependent variables and paths This guide refers to the following variables: viii Monitoring Agent for Microsoft.NET: User's Guide

11 Chapter 1. Overview IBM Application Performance Diagnostics version 1.2 provides deep-dive diagnostics of.net framework applications. Application Performance Diagnostics includes the following components: v Monitoring Agent for Microsoft.NET v Monitoring Agent for WebSphere Applications v Monitoring Infrastructure Node v Application Performance Diagnostics dashboards The Monitoring Agent for Microsoft.NET monitoring agent and data collector are key components of Application Performance Diagnostics. The data collector gathers data from the.net framework applications and communicates the data to the monitoring agent. The monitoring agent routes data from the data collector to the monitoring infrastructure where the information is processed. You install the monitoring infrastructure on a virtual machine (VM) that is referred to as the Monitoring Infrastructure Node. You install the monitoring agent and data collector on a VM that is referred to as the consumer VM. You use a Service Delivery Platform, for example, IBM SmartCloud Provisioning, to provision the virtual machines. The metrics that you collect from your.net applications are available for viewing from the Monitoring Agent for Microsoft.NET diagnostics dashboards. The dashboards are available from the Application Performance Management console. The Application Performance Management console is a web-based user interface for monitoring resources in your IT environment. A number of predefined thresholds are provided with the Monitoring Agent for Microsoft.NET. When a KPI exceeds a threshold value, an event is opened. The event is visible in the Events tab of the Application Performance Dashboard. Figure 1 on page 2 shows how the Monitoring Agent for Microsoft.NET interacts with the Monitoring Infrastructure Node, the Application Performance Management console, and the Service Delivery Platform components. Copyright IBM Corp

12 Service Delivery Platform(SDP) SDP: Service Delivery Platform VM: Virtual machine DC: Data collector JMX: Java Management Extensions JVM: Java virtual machine UI: User interface Diagnostics ext: Diagnostics extension Browser-based Application Performance Management console UI Infrastructure SDP Plugin Monitoring Infrastructure Node Consumer VM1.NETFramework Application Figure 1. Interaction with Application Insight, User Interface, and Service Delivery Platform components On the consumer VM, the.net Data Collector is configured on the system where the.net framework is installed. The data collector gathers diagnostics data and sends the data to the diagnostics extension at the monitoring agent for processing. For more information about installing and configuring the Monitoring Agent for Microsoft.NET, see the Monitoring Agent for Microsoft.NET: Installation and Configuration Guide in the IBM Application Performance Diagnostics Information Center. For more information about the Monitoring Agent for WebSphere Applications, see the IBM Application Performance Diagnostics Information Center. 2 Monitoring Agent for Microsoft.NET: User's Guide

13 Chapter 2. Starting the Application Performance Management console Go to the login page to start the Application Performance Management console. Procedure 1. To start the console, go to where MIN_host is the Monitoring Infrastructure Node and console_port is the port of the Application Performance Management console. 2. Log in with the user name and password. The default user name is apmadmin and the password is apmpass. Results You start the console successfully. Copyright IBM Corp

14 4 Monitoring Agent for Microsoft.NET: User's Guide

15 Chapter 3. Application Performance Management console The Application Performance Management console provides you with access to dashboards for monitoring your applications, access to configuration pages for configuring your data sources, and access to the help system. After you log in to the console, the Getting Started page or the Application Performance Dashboard is displayed, depending on whether you cleared the checkbox for showing the Getting Started page at startup. If you are in the Getting Started page, you can open the Application Performance Dashboard by selecting View Application Status > Start Now. If you cleared the checkbox for showing the Getting Started page at startup, you can open the Application Performance Dashboard at any time by selecting Performance > Application Performance Dashboard from the navigation bar. The dashboard opens with a tabbed dashboard and a navigator. The Application Performance Dashboard provides a tabbed dashboard and a navigator for switching between applications and drilling down to show key performance indicators (KPIs) for the elements of your applications. When you select All My Applications in the navigator, the Status Overview tab displays the status of your applications. When you select a specific application in the navigator, all of the components of the application appear under Groups. When you select a component of the application from Groups, the Status Overview tab updates to show the group widgets for that component. The Events tab is filtered to display events that are opened for the component. For example, if you select Microsoft.NET Deep Dive under Groups in the navigator, the Status Overview tab shows the MS.NET Deep Dive group widgets. The events tab shows events from the.net framework applications. For information about using the Application Performance Dashboard, see the Application Performance Dashboard help. Navigating to the diagnostics dashboards Use the Application Performance Dashboard navigator to navigate through the application hierarchy down to a.net framework instance level. From the.net framework instance level, open the dashboards for diagnosing problems with the.net framework applications. About this task Take these steps to navigate to the Monitoring Agent for Microsoft.NET diagnostics dashboards. Copyright IBM Corp

16 Procedure 1. In the applications section of the Application Performance Dashboard navigator, expand the All My Applications node and click an application that uses a.net framework. The Groups section of the navigator shows the groups that are contained in the application. 2. In the Groups section of the navigator, navigate to Microsoft.NET Deep Dive. The Status Overview tab displays the MS.NET Deep Dive group widget for each.net framework in the group. 3. In the Instances section of the navigator, click a.net framework instance. The Status Overview tab displays the Request Summary dashboard for the framework. 4. Click a request name on the Request Summary group widget to navigate to the Request Instances dashboards. 5. Click a thread ID on the Request Instances group widget to navigate to the Request Traces dashboard. Results A diagnostics dashboard is displayed. 6 Monitoring Agent for Microsoft.NET: User's Guide

17 Chapter 4. Configuration pages You can configure your monitoring infrastructure and your Monitoring Agent for Microsoft.NET settings using the configuration pages. Application Performance Management console provides several configuration pages: v v v v Use the Historical Data Configuration page for configuring historical data collection for all monitored resources. For more information, see the Historical Data Configuration section of the IBM SmartCloud Monitoring - Application Insight help. Use the Threshold Manager page for setting thresholds for all monitored resources. For more information, see the Threshold Manager section of the IBM SmartCloud Monitoring - Application Insight help. Use the Advanced Configuration page for configuring the Monitoring Infrastructure Node. For more information, see the Advanced Configuration section of the IBM SmartCloud Monitoring - Application Insight help. To open the configuration pages, from the navigation bar, click System Configuration ( ) and choose a configuration option. Copyright IBM Corp

18 8 Monitoring Agent for Microsoft.NET: User's Guide

19 Chapter 5. Configuring the Monitoring Agent for Microsoft.NET Configuring event thresholds You can configure your Monitoring Agent for Microsoft.NET through the configuration pages on the Application Performance Management console. Thresholds are used to compare the sampled value of an attribute with the value set in the threshold. If the sampled value meets or exceeds the threshold, an event is opened. The event closes automatically when the threshold comparison is no longer true. Use the Threshold Manager to view the predefined thresholds and to create and edit thresholds. The Monitoring Agent for Microsoft.NET provides a set of predefined thresholds. For more information about the predefined thresholds, see the Thresholds section of the Monitoring Agent for Microsoft.NET Reference Guide on Service Management Connect. You can use the Events tab to view the events triggered by metrics that exceed a threshold. If the predefined threshold values for various metrics do not suit your business needs, adjust them using the Threshold Manager. To open the Threshold Manager, click System Configuration > Threshold Manager. For information about configuring event thresholds, see the Threshold Manager section of the IBM SmartCloud Monitoring - Application Insight help. Copyright IBM Corp

20 10 Monitoring Agent for Microsoft.NET: User's Guide

21 Chapter 6. Diagnostics dashboards The Monitoring Agent for Microsoft.NET provides several dashboards for performing deep-dive diagnosis of.net framework applications. Each dashboard contains several group widgets. To view group widget help, click the online help icon ( ) on the group widget on the user interface. The Monitoring Agent for Microsoft.NET diagnostics dashboards rely on diagnostic and trace data. MS.NET Deep Dive Component dashboard When you select Microsoft.NET Deep Dive in the navigator, the Status Overview tab is populated with a MS.NET Deep Dive group widget for each.net framework used by the application. Using the MS.NET Deep Dive group widget Use the MS.NET Deep Dive group widget to check the overall status of the.net process and to view a summary of requests. For each KPI, the colors have the following meaning: v Green indicates that no threshold is exceeded. v Amber indicates that the normal threshold is exceeded. v Red indicates that the warning threshold is exceeded. To investigate a problem further, click the MS.NET Deep Dive group widget to drill down to the Request Summary dashboard. MS.NET Deep Dive The MS.NET Deep Dive group widget provides a consolidated view of the overall status of the.net application. Tip: v Click the group widget to drill down to the Request Summary dashboard. v You cannot modify the threshold values through the Threshold Editor. KPI Description Definition.NET process status Indicates whether the total number of handles that are currently opened by this process is greater than normal. Thresholds: v Normal is less than 2000 v Warning is greater than 2000 and less that v Critical is greater than or equal to KQENETPROC.HANDLE_COU Copyright IBM Corp

22 KPI Description Definition Time in GC (%) Indicates whether the percentage of time that is spent in garbage collection is greater than normal. KQENETCLRM.TIME_IN_GC.NET CLR exception status WCF status Request summary status Midlife crisis status Indicates whether the number of exceptions that are currently thrown per second is greater than normal. Thresholds: v Normal is less than 100 v v Warning is greater than 100 and less that 500 Critical is greater than or equal to 500 Indicates whether the number of calls that failed in the service per second is greater than normal. Thresholds: v Normal is 0 v Critical is greater than or equal to 1 Displays the number of requests that fall within the normal, warning, and critical thresholds. Thresholds: v Normal is less than 200 seconds v Warning is equal to or greater than 200 but less than 500 seconds v Critical is greater than 500 seconds Indicates whether the application is in a critical status. The widget displays a critical status when the following conditions are met: 1. The number of generation 2 objects collected as garbage is greater than one-tenth of the value of the generation 1 objects collected as garbage. 2. The value of the change in the heap size of generation 2 objects is less than zero. KQENETCLRE.OF_EXCEPS0 KQESERMSER.CALLSFAIL0 KQEREQSMRY.REQ_NAME KQEREQSMRY.AVG_RESP KQENETCLRM.GEN_2_COLL KQENETCLRM.GEN1COLL10 KQENETCLRM.X 12 Monitoring Agent for Microsoft.NET: User's Guide

23 KPI Description Definition ASP.NET applications status Displays the number of requests that are rejected because the request queue is full. Thresholds: v Normal is 0 v Critical is greater than 0 KQEASPNETF.REQUESTS_R Request Summary dashboard Use the Request Summary dashboard to identify in which.net segments the request spent the most time. From this dashboard, you can drill down to the request instances that took the most time. Using the dashboard To identify if many of the requests on the framework are experiencing a slow response time, complete these steps: 1. Check the Request Summary table to see if many requests have a slow average response time. 2. Click the 100% percentile in the Response Time Distribution chart to identity potential outliers. The Request Instances dashboard opens. From this dashboard, you see the slowest request instances. 3. Select each request instance to view more information about the context of the request to help you determine why it was slow. 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. Click the request type. The Request Instances dashboard opens. From this dashboard, you see the request instances of this request type that had the slowest response times. Group Widgets The Request Summary dashboard shows the following group widgets: v Request Summary v Response Time Breakdown v Response Time Distribution To view group widget help, click the online help icon ( ) on the group widget. Chapter 6. Diagnostics dashboards 13

24 Request Summary The Request Summary group widget displays an aggregated view of all requests on the.net 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. Tip: v Select any request to filter the Response Time Breakdown and the Response Time Distribution charts for the specific request. To remove the filtering, click Clear Selection. v You can drill down to view the request instances that are associated with a request. Click a request name on the request row. KPI Description Definition Start record date and time The start date and time of the sampled period for all summary records. KQEREQSMRY.SREC_DTTIM End record date and time The end date and time of the sampled period for all summary records. KQEREQSMRY.EREC_DTTIM Request name The request name. KQEREQSMRY.REQ_NAME Request type The request type. For KQEREQSMRY.REQ_TYPE example, ASP.NET. Request count The number of requests KQEREQSMRY.REQ_COUNTT instances. Response time (ms) The average response time, in KYNREQSMRY.AVG_RESP milliseconds, for the request. Max response time (ms) The maximum response time, in milliseconds, for the request. KQEREQSMRY.MAX_RESP Min response time (ms) CPU time (ms) The minimum response time, in milliseconds, for the request. The average CPU time for the request. KQEREQSMRY.MIN_RESP KQEREQSMRY.AVG_CPU Response Time Breakdown The Response Time Breakdown group widget 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: v 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. 14 Monitoring Agent for Microsoft.NET: User's Guide

25 KPI Description Definition Request type Percent The request type. For example, ASP.NET. The percentage of time that the request spent on the request type. KQEREQBRK.REQ_TYPE KQEREQBRK.PERCENT Response Time Distribution The Response Time Distribution group widget 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. Tip: v 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. KPI Description Definition Upper-bound response time (ms) Percent of request completion The upper-bound response time, in seconds, for the percentile value. For example, if the bar at the 80% percentile shows a value of 6500 ms, 80% of requests were processed within 6500 ms. The percentile value. KQEREQDIST.UB KQEREQDIST.PV Request Instances dashboard Use the Request Instances dashboard to determine if all of the request instances of a request have a problem. Using the dashboard Determine if only some instances of a request have a problem. 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. Group Widgets The Request Instances dashboard shows the following group widgets: v Request Instances Chapter 6. Diagnostics dashboards 15

26 To view group widget help, click the online help icon ( ) on the group widget. Request Instances The Request Instances group widget displays the response time for individual requests inclusive of 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: v You can drill down to view the request trace for this instance. Click a thread on the request row. KPI Description Definition Thread ID The ID of the request. KQEREQINST.REQ_ID Request name The request name. KQEREQINST.REQ_NAME Request type Response time (ms) CPU (ms) Timestamp The request type. For example, ASP.NET. The response time, in milliseconds, of the request instance. The amount of CPU time that is consumed by the request instance, in milliseconds. The date and time that this request instance took place. KQEREQINST.REQ_TYPE KQEREQINST.REQ_RESP KQEREQINST.REQ_CPU KQEREQINST.REQ_TMSTMP Request Traces 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. Using the dashboard Compare the paths taken by different requests. 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. Identify the nested requests or method call were the bottleneck or slow response time occurred. Use the stack trace to gather more information about the caller methods. Identify the specific resource that the nested request or method call was using. Use the request context to identify the specific resource. Group Widgets The Request Traces dashboard shows the following group widgets: v Method Trace v Request Context 16 Monitoring Agent for Microsoft.NET: User's Guide

27 v Request Stack Trace To view group widget help, click the online help icon ( ) on the group widget. Method Trace The Method Trace group widget 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. The request sequence table provides the average response time and the CPU usage of request, nested request, or method call. Tip: 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. KPI Description Definition Event name Response time (ms) CPU time (ms) Event Type The name of the request instance, nested request, or method call. For example, if the event type is ASP.NET, the event name might be execute. If the event type is ASP.NET, the event name might be the method name. The response time, in milliseconds, of the request instance, nested request, or method call. The total amount of CPU time that is consumed by the request instance, nested request, or method call, in milliseconds. The request instance or nested request type. For example, ASP.NET. KQEREQTRC.EVENT_NAME KQEREQTRC.REQ_RESP KQEREQTRC.CPU_TME KQEREQTRC.EVENT_TYPE Request Context The Request Context group widget displays the context of each request. The type of information in the request context depends on the request type. For a JNDI request, the request context includes the JNDI resource URI. For a JDBC request, the request context includes the data source name, the request name, and an SQL statement. For an EJB method and servlet requests, the request context includes the request name and the application module name. When you have multiple instances of a resource in your environment, use the request context to identify which resource instance the request used. Tip: Chapter 6. Diagnostics dashboards 17

28 v Select a trace in the method trace table to show context information for the trace. KPI Description Definition Name Value The parameter name in the name-value pair. The parameter value in the name-value pair. KQEREQCTX.VNAME KQEREQCTX.VAL Request Stack Trace The Request Stack Trace group widget 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. A method trace might perform differently depending on caller method. Each caller method might pass different input parameters to the method call. Use the stack trace to identify and fix looping conditions. The stack trace also provides the depth of a method call. A high number of nested calls might lead to a high method response time. Tip: v Select a request in the method trace table to show the stack trace for the trace. KPI Description Definition Fully Qualified Method Name The class name, the method name within the class name, and the relevant line of the source code. KQEREQSTK.FMTHD_NAME 18 Monitoring Agent for Microsoft.NET: User's Guide

29 Chapter 7. Troubleshooting dashboard data display problems If you do not see data in the Monitoring Agent for Microsoft.NET diagnostics dashboards, use the following checklist to verify the settings: Checkpoint User load is applied on the framework. Diagnostics mode is enabled and the data collector is registered. The profiler service is started. Comments The diagnostics dashboards display data only when user load is applied. Diagnostics mode must be enabled to view data in the dashboards. Verify that the profiler service is started. Copyright IBM Corp

30 20 Monitoring Agent for Microsoft.NET: User's Guide

31 Appendix. Accessibility Accessibility features help users with physical disabilities, such as restricted mobility or limited vision, to use software products successfully. The accessibility features in the product enable users to: v Use assistive technologies, such as screen reader software and digital speech synthesizers, to hear what is displayed on the screen. Consult the product documentation of the assistive technology for details on using the technology with this product. v Perform tasks with the software using only the keyboard. General Navigation Each page has four main sections: v Headerbar v Toolbar v Main tabs v Content Each page has navigation points for screen readers. The following navigation points are all H1: v Title bar v Main tabs v Main form v Section labels v Table labels Menu Navigation You use the Go To menu to navigate to any of the applications that you have access to. The Go To menu is a cascading menu that is three levels deep at its deepest point. The following instructions describe how to get started with JAWS: 1. To get to the Go To menu press Alt+G. 2. When you open the menu, JAWS reads the first application in the menu. If JAWS does not begin to read the entry, restart the screen reader. 3. Navigate the list of applications in the menus by using the arrow keys. 4. JAWS indicates if a menu item has submenus. To get to a submenu, press the right arrow or enter. 5. Press the left arrow to move up a level in the hierarchy. If you press the left arrow at the highest level of the Go To menu, you leave the menu completely. 6. Press the Enter key to enter an application. Accessibility help The Accessibility Help panels provide details on general navigation, menu navigation, and hot keys. Click Accessibility Help from the toolbar of the product to access the help panels. Copyright IBM Corp

32 Screen reader setting The product contains a screen reader flag. When you turn on the screen reader flag, the user interface is optimized to work with JAWS for Windows. You use the User tab in the Users application to turn on the screen reader flag. Keyboard shortcuts You can navigate within the applications by using a combination of keys. Accessible reports To use the accessibility tools to read reports, you must access the reports in Microsoft Excel. In the reports applications, select the Run Reports option in the Select Action menu. With this option, you can an.xls file version of a report to yourself at a scheduled time. IBM and accessibility For more information about the commitment that IBM has to accessibility, see the IBM Human Ability and Accessibility Center. The IBM Human Ability and Accessibility Center is at the following web address: 22 Monitoring Agent for Microsoft.NET: User's Guide

33 Index A accessibility vii Application Performance Management console 5 MS.NET Deep Dive group widget 11 N navigating 5 V variables for directories viii B books v C Configuration Pages 7 configuring 9 Configuring event thresholds 9 conventions typeface viii cookies 28 D dashboard.net Applications Request Summary dashboard 13 WebSphere Applications Request Instances dashboard 15 Request Traces dashboard 16 dashboards 11 directories, variables for viii E education See Tivoli technical training G group widgets.net application Request Summary group widget 14.NET Application Method Trace group widget 17 MS.NET Deep Dive group widget 11 Request Context group widget 17 Request Instances group widget 16 Request Stack Trace group widget 18 Response Time Breakdown group widget 14 Response Time Distribution group widget 15 M manuals v Method Trace group widget 17 O ordering publications overview 1 P privacy policy 28 publications v ordering vi R reader requirements v Request Context group widget 17 Request Instances dashboard 15 Request Instances group widget 16 Request Stack Trace group widget 18 Request Summary dashboard 13 Request Summary group widget 14 Request Traces dashboard 16 requirements for readers v Response Time Breakdown group widget 14 Response Time Distribution group widget 15 S vi service vii service management connect SMC vii start 3 Status Overview 11 support vii T tab.net Applications Status Overview 11 Tivoli technical training vii Tivoli user groups vii training, Tivoli technical vii typeface conventions viii U user groups, Tivoli vii vii Copyright IBM Corp

34 24 Monitoring Agent for Microsoft.NET: User's Guide

35 Trademarks IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the web at Copyright and trademark information at Adobe and all Adobe-based trademarks are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, other countries, or both. Linux is a trademark of Linus Torvalds in the United States, other countries, or both. Microsoft, Windows, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates. or Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates. Copyright IBM Corp

36 26 Monitoring Agent for Microsoft.NET: User's Guide

37 Notices This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-ibm product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: Intellectual Property Licensing Legal and Intellectual Property Law IBM Japan, Ltd , Nihonbashi-Hakozakicho, Chuo-ku Tokyo , Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement might not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-ibm Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. Copyright IBM Corp

38 IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation 2Z4A/ Burnet Road Austin, TX U.S.A. Privacy policy considerations Such information may be available, subject to appropriate terms and conditions, including in some cases payment of a fee. The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us. Information concerning non-ibm products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-ibm products. Questions on the capabilities of non-ibm products should be addressed to the suppliers of those products. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. IBM Software products, including software as a service solutions, ( Software Offerings ) may use cookies or other technologies to collect product usage information, to help improve the end user experience, to tailor interactions with the end user, or for other purposes. In many cases no personally identifiable information is collected by the Software Offerings. Some of our Software Offerings can help enable you to collect personally identifiable information. If this Software Offering uses cookies to collect personally identifiable information, specific information about this offering s use of cookies is set forth below. Depending upon the configurations deployed, this Software Offering may use session cookies that collect each user s name for purposes of session management, authentication, and single sign-on configuration. These cookies can be disabled, but disabling them will also likely eliminate the functionality they enable. If the configurations deployed for this Software Offering provide you as customer the ability to collect personally identifiable information from end users via cookies and other technologies, you should seek your own legal advice about any laws applicable to such data collection, including any requirements for notice and consent. 28 Monitoring Agent for Microsoft.NET: User's Guide

39 For more information about the use of various technologies, including cookies, for these purposes, See IBM s Privacy Policy at and IBM s Online Privacy Statement at the section entitled Cookies, Web Beacons and Other Technologies and the IBM Software Products and Software-as-a-Service Privacy Statement at Notices 29

40 30 Monitoring Agent for Microsoft.NET: User's Guide

41

42 Printed in USA SC