Monitoring Agent for Microsoft.NET Version Reference IBM

Transcription

1 Monitoring Agent for Microsoft.NET Version Reference IBM

2

3 Monitoring Agent for Microsoft.NET Version Reference IBM

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

5 Contents Chapter 1. Monitoring Agent for Microsoft.NET Chapter 2. Dashboards Default dashboards deepdive dashboards Group widgets for the Default dashboards Group widgets for the deepdive dashboards Custom charts and tables Chapter 3. Eventing thresholds Predefined eventing thresholds Customized eventing thresholds Chapter 4. Attributes Data sets for the monitoring agent Attribute descriptions Agent Event data set ASP.NET Applications Error Filter data set ASP.NET Applications Filter data set ASP.NET Applications V2.0 data set ASP.NET Applications V bit data set ASP.NET Applications V bit Error data set 57 ASP.NET Applications V4.0 data set ASP.NET Applications V4.0 - WebSockets data set 67 ASP.NET Applications V4.0 Error data set ASP.NET Filter data set ASP.NET V2.0 data set ASP.NET V bit data set ASP.NET V4.0 data set Event Log data set HTTP Operation Level Data data set IIS Web Sites Detail data set NET CLR Exceptions data set NET CLR Interop data set NET CLR Loading data set NET CLR Memory data set NET CLR Networking data set NET CLR Networking Filter data set NET CLR Networking V4.0 data set NET CLR Remoting data set NET CLR Security data set NET Components data set NET Data Provider Filter data set NET Data Provider for Oracle data set NET Data Provider For SQL Server data set NET Process data set Performance Object Status data set RequestBreakdown data set RequestContext data set RequestDistribution data set RequestInstance data set RequestStackTrace data set RequestStatus data set RequestSummary data set RequestTrace data set Service Model Endpoint data set Service Model Endpoint Filter data set Service Model Endpoint V4.0 data set Service Model Operation data set Service Model Operation Filter data set Service Model Operation V4.0 data set Service Model Service data set Service Model Service Filter data set Service Model Service V4.0 data set Service Model Svc Host data set Service Model Svc Host Filter data set Service Model Svc Host V4.0 data set WCF Operation Level Data data set Websites W3C Logs data set Windows Workflow Foundation data set Windows Workflow Foundation Filter data set 187 Windows Workflow Foundation V4 data set Workflow ServiceHost V4 data set Accessibility features Notices Trademarks Terms and conditions for product documentation 203 IBM Online Privacy Statement Index Copyright IBM Corp. 2008, 2016 iii

6 iv Monitoring Agent for Microsoft.NET Reference

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

8 2 Monitoring Agent for Microsoft.NET Reference

9 Chapter 2. Dashboards Open the Application Performance Dashboard in the Performance Management console to see a status summary of all your applications. As you drill down to dashboards for specific applications and their supporting elements, more details are available about the selected item. Use the Microsoft.NET agent dashboards to proactively monitor your Microsoft.NET deployment. Each dashboard contains one or more group widgets with key performance indicators. After you select an application that includes Microsoft.NET managed systems, you can see Microsoft.NET KPIs in the application dashboard: v At the application level, the Current Component Status stacked bar chart shows an average of the critical, warning, and normal status severities from all the Microsoft.NET managed systems in the application. v Click the Microsoft.NET bar in the Current Component Status chart or expand Components in the navigator Groups section and click Microsoft.NET to see a summary group widget for each Microsoft.NET managed system in the application. v Click inside a Microsoft.NET summary group widget or click a Microsoft.NET managed system from the navigator Microsoft.NET instances section to open a dashboard with details from the selected managed system. For more information about the KPIs, click in the group widget or click in the upper-right corner of the dashboard. Default dashboards MS. Net The summary dashboard shows the current status and availability of each monitored.net application. Review the resource usage and investigate any warning or critical thresholds. If the Events tab shows a warning or critical status indicator, open the tab to see the open events and status for the application. Click anywhere on a group widget to drill down to detailed information about the application instance..net Process Memory Use the.net Process Memory dashboard to know the following historical trends of a selected.net application: v v Private bytes, virtual bytes, and bytes in all heaps Percentage of processor time that is spent by the process Aggregated Services and Runs On Summary Use the Aggregated Services and Runs On Summary dashboard to view the aggregated performance of all WCF services used by the selected application. The dashboard also shows the aggregated performance of each WCF service on each individual.net server. Aggregated Services Details Use the Aggregated Services Details dashboard to view the aggregated performance of the selected WCF service over time. The dashboard also displays the aggregated performance of the selected WCF service on each individual.net server during the history interval. Microsoft.NET Framework Use the Overview dashboard to know the overall status of the following.net framework resources: Copyright IBM Corp. 2008,

10 v v v.net processes with high exceptions rate, high handle count, and high percentage of time that is spent in garbage collection Rejected requests for ASP.NET applications ASP.NET requests with high response time Service Details on Server Use the Service Details on Server dashboard to see a summary of the performance of a selected WCF service on a selected server during the history period. Service Details on Server Use the Service Details on Server dashboard to view the performance of a selected WCF service on a selected server during the history period. Additional group widgets These pop-up group widgets are displayed after you click a group widget for more details. Some group widgets have links to more granular information in a popup widget, described here. deepdive dashboards Request Instances This is a diagnostics dashboard. Use the Request Instances dashboard to determine if all of the request instances of a request have a problem. Remember: A time selector bar might be displayed. The time period applies to all group widgets and dashboards that are derived from historical data. The time selector does not apply to the deep-dive dashboards. Using the dashboard Determine if only some instances of a request have a problem. v v v If all of the request instances are experiencing a problem, some of the underlying code might be poorly constructed. If only some instances are experiencing the problem, locate the hot spot where the problem occurred. To drill down to the Request Traces dashboard, click View request sequence on an instance row. Request Summary This is a diagnostics dashboard. Use the Request Summary dashboard to identify in which.net segments the request spent the most time. From this dashboard, you can drill down to the request instances that took the most time. Remember: A time selector bar might be displayed. The time period applies to all group widgets and dashboards that are derived from historical data. The time selector does not apply to the deep-dive dashboards. Using the dashboard To identify which request instances resulted in a slow average response time for a specific request, complete these steps: 1. Locate a request with a slow average response time in the Request Summary table. 2. Select a request in the table to view the response time breakdown for the request. The Response Time Breakdown chart shows where the request spent the most time. 3. In the Response Time Breakdown chart, identify the request type that is taking up the most time, and click the request type. The Request Instances dashboard opens. From this dashboard, you see the request instances of this request type that had the slowest response times. 4 Monitoring Agent for Microsoft.NET Reference

11 Request Traces This is a diagnostics dashboard. Use the Request Traces dashboard to identify the sequence of calls to nested requests and methods for a request instance. Use the dashboard to identify the root cause of a problem, if the problem relates to the code. Remember: A time selector bar might be displayed. The time period applies to all group widgets and dashboards that are derived from historical data. The time selector does not apply to the deep-dive dashboards. Using the dashboard v v v Compare the path taken by request instances that ran without a problem and request instances that performed poorly. Use the request sequence dashboard to gather information about the paths of each request instance. Depending on the input parameters, a request instance might take a different path to other instances. The difference in path taken might indicate the source of the resource issue or bottleneck. Use the stack tree to identify the nested requests or method call where the bottleneck or slow response time occurred. Use the request context to identify the specific resource that the nested request or method call was using. Additional group widgets These pop-up group widgets are displayed after you click a group widget for more details. Some group widgets have links to more granular information in a popup widget, described here. Group widgets for the Default dashboards MS. Net The summary dashboard shows the current status and availability of each monitored.net application. Review the resource usage and investigate any warning or critical thresholds. If the Events tab shows a warning or critical status indicator, open the tab to see the open events and status for the application. Click anywhere on a group widget to drill down to detailed information about the application instance. The following group widgets are available in this dashboard: Aggregated WCF Services The Aggregated WCF Services group widget displays the overall status and number of WCF services that run on a selected server during the history period. The following KPIs for the group widget are derived from the attributes as described: v WCF Services (critical): The number of WCF Services call failures that resulted in the critical state. v WCF Services (normal): The number of completed WCF Services calls that resulted in the normal state. v WCF Services (warning): The number of WCF Services call failures that resulted in the warning state. MS.NET The MS.NET group widget provides HTML tables and status summary widgets that show a consolidated status of.net processes and ASP.NET applications. The following KPIs for the group widget are derived from the attributes as described: v ASP.NET applications (critical): The number of ASP.NET applications with high request rejections. v ASP.NET applications (normal): The count of ASP.NET applications with no request rejections. v CLR exceptions rate: The number of processes for which exceptions per second are greater than normal. Chapter 2. Dashboards 5

12 v GC collections: The number of processes for which the garbage collection status is critical or time for garbage collection is greater than normal. v Handle count: The number of processes with the handle count greater than the threshold. v WCF calls status: Indicates whether the number of calls that failed per second for services is greater than normal..net Process Memory Use the.net Process Memory dashboard to know the following historical trends of a selected.net application: v v Private bytes, virtual bytes, and bytes in all heaps Percentage of processor time that is spent by the process The following group widgets are available in this dashboard:.net Processes The.NET Processes group widget provides an HTML table that displays the.net processes that are running on the monitored server. The following KPIs for the group widget are derived from the attributes as described: v Process Name: This attribute displays the name of Process. This data is derived from the Process Name attribute in the KQE NET PROCESS data set. Bytes in All Heaps (history) The Bytes in All Heaps (history) group widget provides a line chart that displays the historical trend of bytes in all heaps during a specified period for the selected.net process. The following KPIs for the group widget are derived from the attributes as described: v Bytes in all heaps: This attribute displays the 'Bytes in all Heaps' in MB. This data is derived from the Bytes in all Heaps in MB attribute in the KQE NET CLR MEMORY data set. v Time: The local time at the agent when the data was collected. This data is derived from the Timestamp attribute in the KQE NET CLR MEMORY data set. Private Bytes (history) The Private Bytes (history) group widget provides a line chart that displays the historical trend of private bytes in heaps during a specified period for the selected.net process. The following KPIs for the group widget are derived from the attributes as described: v Private Bytes: This attribute displays the 'Private Bytes' in MB. This data is derived from the Private Bytes in MB attribute in the KQE NET PROCESS data set. v Time: The local time at the agent when the data was collected. This data is derived from the Timestamp attribute in the KQE NET PROCESS data set. Time Spent by Process in Processor (%) (history) The Time Spent by Process in Processor (%) (history) group widget provides a line chart that displays the percentage of processor time that was taken by the selected process during a specified period. The following KPIs for the group widget are derived from the attributes as described: v Percent Processor Time: This attribute displays the percentage of elapsed time that all of process threads used the processor to execution instructions. This data is derived from the Percent Processor Time attribute in the KQE NET PROCESS data set. v Time: The local time at the agent when the data was collected. This data is derived from the Timestamp attribute in the KQE NET PROCESS data set. 6 Monitoring Agent for Microsoft.NET Reference

13 Virtual Bytes (history) The Virtual Bytes (history) group widget provides a line chart that displays the historical trend of virtual bytes in the heaps during a specified period for the selected process. The following KPIs for the group widget are derived from the attributes as described: v Time: The local time at the agent when the data was collected. This data is derived from the Timestamp attribute in the KQE NET PROCESS data set. v Virtual Bytes: This attribute displays the 'Virtual Bytes' in MB. This data is derived from the Virtual Bytes in MB attribute in the KQE NET PROCESS data set. Aggregated Services and Runs On Summary Use the Aggregated Services and Runs On Summary dashboard to view the aggregated performance of all WCF services used by the selected application. The dashboard also shows the aggregated performance of each WCF service on each individual.net server. The following group widgets are available in this dashboard: Aggregated WCF Services Runs On The Aggregated WCF Services Runs On group widget displays the performance summary of all WCF services that ran on each.net server during the history period. The table is sorted by the error count. Tip: Click a server in the Aggregated WCF Services Runs On table to drill down to view WCF Service Summary on the Service Details on Server dashboard. The following KPIs for the group widget are derived from the attributes as described: v Average Response Time (ms): The average duration of calls, in seconds, that were made to WCF services on this.net server during the history period. v Error Count: The total number of calls to WCF services on this server that returned fault and failed messages during the history period. v Error Rate(%): The ratio (in percentage) of error count to request count. If the request count is zero, the error rate is zero. v Host Name: The host name of the.net server. v Request Count: The total number of calls that were made to WCF services on this server during the history period. v Server Name: The name of the.net server. Aggregated WCF Services Summary The Aggregated WCF Services Summary group widget displays the performance summary of each WCF service across all Microsoft.NET servers during the history period. The table is sorted by the error count. Tip: Click a WCF service in the Aggregated WCF Services Summary table to drill down to view the Aggregated Services Details dashboard. The following KPIs for the group widget are derived from the attributes as described: v Average Response Time (ms): The average duration of calls that were made to the WCF service, in milliseconds, across all.net servers during the history period. v Error Count: The total number of calls to the WCF service that returned fault and failed messages across all.net servers for the selected time period. v Error Rate(%): The ratio (in percentage) of error count to request count. If the request count is zero, the error rate is zero. v Request Count: The total number of calls that were made to the WCF service across all.net servers during the history period. Chapter 2. Dashboards 7

14 v WCF Service Name: The name of the WCF service. Aggregated Services Details Use the Aggregated Services Details dashboard to view the aggregated performance of the selected WCF service over time. The dashboard also displays the aggregated performance of the selected WCF service on each individual.net server during the history interval. The following group widgets are available in this dashboard: WCF Service Performance The WCF Service Performance group widget displays a graph that shows the aggregated performance of the selected WCF service at each interval during the history period. The following KPIs for the group widget are derived from the attributes as described: v Number of Error Requests: The total number of calls that were made to the WCF service that returned fault and failed messages at each interval during the history period. v Number of Requests: The total number of calls that were made to the WCF service at each interval during the history period. v Service Response Time (ms): The average duration of calls, in seconds, that were made to the WCF service at each interval during the history period. v Timestamp: The time interval. WCF Service Runs On The WCF Service Runs On group widget displays the performance summary of all WCF services on each.net server during the history period. The table is sorted by the error count. Tip: Click a server to drill down to view the WCF Service Performance on Server table on the Service Details on Server dashboard. The following KPIs for the group widget are derived from the attributes as described: v Average Response Time (ms): The average duration of calls, in seconds, that were made to the WCF service on this.net server during the history period. v Base Address: The base address of the service. It is the substring after in the web service name. v Error Count: The total number of calls to the WCF service on this server that returned fault and failed messages during the history period. v Error Rate(%): The ratio (in percentage) of error count to request count. If the request count is zero, the error rate is zero. v Host Name: The host name of the.net server. v Request Count: The total number of calls that were made to the WCF service on this server during the history period. v Server Name: The name of the.net server. Microsoft.NET Framework Use the Overview dashboard to know the overall status of the following.net framework resources: v v v.net processes with high exceptions rate, high handle count, and high percentage of time that is spent in garbage collection Rejected requests for ASP.NET applications ASP.NET requests with high response time The following group widgets are available in this dashboard: 8 Monitoring Agent for Microsoft.NET Reference

15 .NET CLR Exception Details The.NET CLR Exception Details group widget provides a grid widget that summarizes the exceptions that are thrown by ASP.NET applications. The following KPIs for the group widget are derived from the attributes as described: v Exceptions per Second: The number of exceptions that are produced per second. When the number of exceptions that are produced per second exceeds 100, this attribute displays non-zero value. This data is derived from the Number of Exceps Thrown Per Sec attribute in the KQE NET CLR EXCEPTIONS data set. v Name: The name of the.net application. This data is derived from the Name attribute in the KQE NET CLR EXCEPTIONS data set. v Total Exceptions: The total number of exceptions thrown since the application started. This data is derived from the Number of Exceps Thrown attribute in the KQE NET CLR EXCEPTIONS data set..net Processes Handles - Top 5 The.NET Processes Handles - Top 5 group widget provides a grid widget that shows the handle count, private bytes, and virtual bytes for.net processes. The grid widget is sorted according to the handle count. The.NET process with the highest handle count is placed at the top. The following KPIs for the group widget are derived from the attributes as described: v Handle Count: This attribute displays the total number of handles currently open by this process. This data is derived from the Handle Count attribute in the KQE NET PROCESS data set. v Name: This attribute displays the name of Process. This data is derived from the Process Name attribute in the KQE NET PROCESS data set. v Private Bytes (MB): This attribute displays the 'Private Bytes' in MB. This data is derived from the Private Bytes in MB attribute in the KQE NET PROCESS data set. v Virtual Bytes (MB): This attribute displays the 'Virtual Bytes' in MB. This data is derived from the Virtual Bytes in MB attribute in the KQE NET PROCESS data set. ASP.NET Applications Requests The ASP.NET Applications Requests group widget provides a grid widget that displays the number of requests that are rejected for the applications. Remember: Click an application name in the Application column to view the details of requests for the application, such as total requests, failed requests, and requests rate. The following KPIs for the group widget are derived from the attributes as described: v Application: The instance name of the ASP.NET application. This data is derived from the Name attribute in the KQE ASP NET APPS FILTER data set. v ASP.NET Version: The ASP.NET version of the application. This data is derived from the Version attribute in the KQE ASP NET APPS FILTER data set. v Rejected: The number of requests that are rejected (because the application request queue is full) since the application was started. This data is derived from the Requests Rejected attribute in the KQE ASP NET APPS FILTER data set. GC Details The GC Details group widget provides a grid widget that shows the status of garbage collection and the percentage of time that is spent by.net processes in garbage collection. Remember: Chapter 2. Dashboards 9

16 Click in the GC Status column corresponding to a process to view the historical trend of generation 0, generation 1, and generation 2 objects that are collected for the process. Click in the Time in GC (%) column corresponding to a process to view the historical trend of percent time that was spent in garbage collection for the process. The following KPIs for the group widget are derived from the attributes as described: v GC Status: The status of generation 0, generation 1, and generation 2 objects that are collected. v Process: The name of the.net application. This data is derived from the Name attribute in the KQE NET CLR MEMORY data set. v Time in GC (%): This attribute displays the percentage of time spent in garbage collection since the end of the last garbage collection. This data is derived from the Percent Time in GC attribute in the KQE NET CLR MEMORY data set. Slow Requests - Top 10 The Slow Requests - Top 10 group widget provides a grid widget that displays the top 10 requests with high response time. The requests are sorted according to their response time. The request with the highest response time is placed at the top. Tip: Click Diagnose to view details of requests. This option is available for the offerings that contain the diagnostics capability. The following KPIs for the group widget are derived from the attributes as described: v Method: The name of the method. v Response Time (ms): The average duration of requests that were made to the selected web address during the history period. v URL: The base address of the service. WCF Service Summary The WCF Service Summary group widget displays the aggregated performance summary of a selected WCF service on a selected server during the history period. The following KPIs for the group widget are derived from the attributes as described: v Average Response Time (ms): The average duration of calls that were made to the WCF service, in seconds, for the selected server during the history interval. v Error Count: The number of calls to the WCF service that returned fault and failed messages for the selected server during the history interval. v Error Rate(%): The ratio (in percentage) of error count to request count. If the request count is zero, the error rate is zero. v Request Count: The number of calls that were made to the WCF service on the selected server during the history interval. v Service URL: The service base address. It is the substring after in the web service name. v WCF Service Name: The name of the service and the service base address. Service Details on Server Use the Service Details on Server dashboard to see a summary of the performance of a selected WCF service on a selected server during the history period. The following group widgets are available in this dashboard: WCF Service Performance on Server The WCF Service Performance on Server group widget displays the performance summary of a selected WCF service on a selected server during the history period. The following KPIs for the group widget are derived from the attributes as described: 10 Monitoring Agent for Microsoft.NET Reference

17 v Number of Error Requests: The number of calls to the WCF service that returned fault and failed messages on the server during the history interval. v Number of Requests: The number of calls that were made to the WCF service on the server during the history interval. v Service Response Time (ms): The average duration of calls that were made to the WCF service, in seconds, on the server during the history interval. v Timestamp: The time interval. Service Details on Server Use the Service Details on Server dashboard to view the performance of a selected WCF service on a selected server during the history period. The following group widgets are available in this dashboard: WCF Service Summary The WCF Service Summary group widget displays the aggregated performance summary of a selected WCF service on a selected server during the history period. The following KPIs for the group widget are derived from the attributes as described: v Average Response Time (ms): The average duration of calls that were made to the WCF service, in seconds, for the selected server during the history interval. v Error Count: The number of calls to the WCF service that returned fault and failed messages for the selected server during the history interval. v Error Rate(%): The ratio (in percentage) of error count to request count. If the request count is zero, the error rate is zero. v Request Count: The number of calls that were made to the WCF service on the selected server during the history interval. v Service URL: The service base address. It is the substring after in the web service name. v WCF Service Name: The name of the service and the service base address. Additional group widgets These pop-up group widgets are displayed after you click a group widget for more details. Some group widgets have links to more granular information in a popup widget, described here. The following group widgets are available in this dashboard: ASP.NET Application The ASP.NET Application group widget provides an HTML table and line charts that display the count and historical trend of ASP.NET requests for the selected application. The following KPIs for the group widget are derived from the attributes as described: v Count: This attribute displays the total number of errors that currently occurred per second during preprocessing, parsing, compilation, and runtime processing of a request. This data is derived from the Errors Total Per Sec attribute in the KQE ASP NET APPS ERROR FILTER data set. v Errors (time): The local time at the agent when the data was collected. This data is derived from the Timestamp attribute in the KQE ASP NET APPS ERROR FILTER data set. v Failed requests: The total number of failed requests since the application was started. This data is derived from the Requests Failed attribute in the KQE ASP NET APPS FILTER data set. v Requests: The number of requests that are run per second. This data is derived from the Requests Per Sec attribute in the KQE ASP NET APPS FILTER data set. v Requests (time): The local time at the agent when the data was collected. This data is derived from the Timestamp attribute in the KQE ASP NET APPS FILTER data set. Chapter 2. Dashboards 11

18 v Total requests: The total number of requests since the application was started. This data is derived from the Requests Total attribute in the KQE ASP NET APPS FILTER data set. GC Collections (history) The GC Collections (history) group widget provides line charts that display the historical trend of generation 0, generation 1, and generation 2 objects that were collected for the selected process. The following KPIs for the group widget are derived from the attributes as described: v Gen 0 Collections: This attribute displays the number of times the generation 0 objects are collected as garbage from the start of the application. This data is derived from the Gen 0 Collections attribute in the KQE NET CLR MEMORY data set. v Gen 1 Collections: This attribute displays the number of times the generation 1 objects are collected as garbage from the start of the application. This data is derived from the Gen 1 Collections attribute in the KQE NET CLR MEMORY data set. v Gen 2 Collections: This attribute displays the number of times the generation 2 objects are collected as garbage from the start of the application. This data is derived from the Gen 2 Collections attribute in the KQE NET CLR MEMORY data set. v Time: The local time at the agent when the data was collected. This data is derived from the Timestamp attribute in the KQE NET CLR MEMORY data set. Time in GC (%) (history) The Time in GC (%) (history) group widget provides a line chart that displays the historical trend of time (in percentage) that was spent in garbage collection for the selected process. The following KPIs for the group widget are derived from the attributes as described: v Percent: This attribute displays the percentage of time spent in garbage collection since the end of the last garbage collection. This data is derived from the Percent Time in GC attribute in the KQE NET CLR MEMORY data set. v Time: The local time at the agent when the data was collected. This data is derived from the Timestamp attribute in the KQE NET CLR MEMORY data set. Transaction Volume The Transaction Volume widget displays a summary of transaction performance across all monitored Microsoft.NET applications. The following KPIs for the group widget are derived from the attributes as described: v Failed requests: Is not derived directly from a single attribute. The value is calculated. v Good requests: Is not derived directly from a single attribute. The value is calculated. v Slow requests: Is not derived directly from a single attribute. The value is calculated. v Timestamp: Is not derived directly from a single attribute. The value is calculated. Group widgets for the deepdive dashboards Request Instances This is a diagnostics dashboard. Use the Request Instances dashboard to determine if all of the request instances of a request have a problem. Remember: A time selector bar might be displayed. The time period applies to all group widgets and dashboards that are derived from historical data. The time selector does not apply to the deep-dive dashboards. Using the dashboard Determine if only some instances of a request have a problem. 12 Monitoring Agent for Microsoft.NET Reference

19 v v v If all of the request instances are experiencing a problem, some of the underlying code might be poorly constructed. If only some instances are experiencing the problem, locate the hot spot where the problem occurred. To drill down to the Request Traces dashboard, click View request sequence on an instance row. The following group widgets are available in this dashboard: Requests Instances Displays the response time for individual requests 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: You can drill down to view the request trace for this instance. Click View request sequence on the request row. The following KPIs for the group widget are derived from the attributes as described: v Action: Link to the Request Traces dashboard for the selected request instance. v CPU Time (ms): The CPU time of the request instance in milliseconds. This data is derived from the CPUTime attribute in the KQE REQUESTINSTANCE data set. v Request Name: The request name. This data is derived from the RequestName attribute in the KQE REQUESTINSTANCE data set. v Request Type: The type of request that is being run. This data is derived from the RequestType attribute in the KQE REQUESTINSTANCE data set. v Response Time (ms): The response time of the request instance in milliseconds. This data is derived from the ResponseTime attribute in the KQE REQUESTINSTANCE data set. v Thread ID: The ID of the thread that processed the request. This data is derived from the ThreadID attribute in the KQE REQUESTINSTANCE data set. v Timestamp: The time when the request instance started. This data is derived from the RequestTimestamp attribute in the KQE REQUESTINSTANCE data set. Request Summary This is a diagnostics 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. Remember: A time selector bar might be displayed. The time period applies to all group widgets and dashboards that are derived from historical data. The time selector does not apply to the deep-dive dashboards. Using the dashboard To identify which request instances resulted in a slow average response time for a specific request, complete these steps: 1. Locate a request with a slow average response time in the Request Summary table. 2. Select a request in the table to view the response time breakdown for the request. The Response Time Breakdown chart shows where the request spent the most time. 3. In the Response Time Breakdown chart, identify the request type that is taking up the most time, and click the request type. The Request Instances dashboard opens. From this dashboard, you see the request instances of this request type that had the slowest response times. The following group widgets are available in this dashboard: Request Summary Displays an aggregated view of all requests on the.net application. The requests are Chapter 2. Dashboards 13

20 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 View instance data on the request row. The following KPIs for the group widget are derived from the attributes as described: v Action: Link to the Request Instances dashboard for the selected request. v Average Response Time (ms): The average response time, in milliseconds, for requests of the same request name. This data is derived from the AvgResponseTime attribute in the KQE REQUESTSUMMARY data set. v CPU Time (ms): The average CPU time, in millisecons, for requests of the same request name. This data is derived from the AvgCPUTime attribute in the KQE REQUESTSUMMARY data set. v End record date and time: The end date and time of the sampled period for all summary records. v Max Response Time (ms): The maxinum response time in milliseconds. This data is derived from the MaxResponseTime attribute in the KQE REQUESTSUMMARY data set. v Min Response Time (ms): The minimun response time in milliseconds. This data is derived from the MinResponseTime attribute in the KQE REQUESTSUMMARY data set. v Request Count: The number of total requests for the same request name. This data is derived from the RequestCount attribute in the KQE REQUESTSUMMARY data set. v Request Name: The request name. This data is derived from the RequestName attribute in the KQE REQUESTSUMMARY data set. v Request Type: The type of request. This data is derived from the RequestType attribute in the KQE REQUESTSUMMARY data set. v Start record date and time: The start date and time of the sampled period for all summary records. Response Time Breakdown Displays the percentage of time that the requests spent on each request type. Use this chart to see, on average, which request type consumed the most time. Tip: Click any bar on the chart to investigate the request instances for this request type. The Request Instances table shows all request instances for the selected request type. The following KPIs for the group widget are derived from the attributes as described: v Percent: The percentage of time that request spent on the request type. This data is derived from the Percent attribute in the KQE REQUESTBREAKDOWN data set. v Request type: The type of request. This data is derived from the RequestType attribute in the KQE REQUESTBREAKDOWN data set. Response Time Distribution Displays the upper response times for percentiles of the requests. 14 Monitoring Agent for Microsoft.NET Reference

21 For example, if the bar at 50% shows a response time of 3000 ms, 50% of all requests were completed within 3000 ms. If the bar at 70% shows 6000 ms, 70% of all requests were completed within 6000 ms or less. Use this chart to determine what percentage of your requests have poor response times. Click any bar on the chart to investigate requests that have a response time in this percentile. For example, if the 50% bar shows a response time of 3000 ms and the 60% bar shows a response time of 4000 ms, click the 60% bar to investigate request instances with a response time between 3000 and 4000 ms. The following KPIs for the group widget are derived from the attributes as described: v Percent of request completion: The percentile value. This data is derived from the PercentileValue attribute in the KQE REQUESTDISTRIBUTION data set. v Upper-bound response time (ms): The upper-bound response time, in millisecond, for the percentile value. This data is derived from the UpperBound attribute in the KQE REQUESTDISTRIBUTION data set. Request Traces This is a diagnostics dashboard. Use the Request Traces dashboard to identify the sequence of calls to nested requests and methods for a request instance. Use the dashboard to identify the root cause of a problem, if the problem relates to the code. Remember: A time selector bar might be displayed. The time period applies to all group widgets and dashboards that are derived from historical data. The time selector does not apply to the deep-dive dashboards. Using the dashboard v v v Compare the path taken by request instances that ran without a problem and request instances that performed poorly. Use the request sequence dashboard to gather information about the paths of each request instance. Depending on the input parameters, a request instance might take a different path to other instances. The difference in path taken might indicate the source of the resource issue or bottleneck. Use the stack tree to identify the nested requests or method call where the bottleneck or slow response time occurred. Use the request context to identify the specific resource that the nested request or method call was using. The following group widgets are available in this dashboard: Method Trace Displays a tree view of all the request instances and their nested requests. If method data was collected, calls to methods are included in this tree. The request sequence table provides the response time and the CPU usage of request, nested request, or method call. Tip: v Use the response timeline to compare response times across requests, nested requests, and method calls. v When an event is an external call, an external call icon is displayed in the event type column. v Select any trace to filter the Request context and the Request stack trace tables for the specific request. To remove the filtering, click Clear Selection. v Expand a request in the method trace table to view subrequests that were called by the request. The following KPIs for the group widget are derived from the attributes as described: Chapter 2. Dashboards 15

22 v Children: The order of child methods. This data is derived from the ChildrenOrderId attribute in the KQE REQUESTTRACE data set. v CPU time (ms): The CPU time, in milliseconds, of the method call or request. This data is derived from the CpuTime attribute in the KQE REQUESTTRACE data set. v Event Name: The event name. This data is derived from the EventName attribute in the KQE REQUESTTRACE data set. v Event Type: The event type. This data is derived from the EventType attribute in the KQE REQUESTTRACE data set. v Response Time (ms): The response time of the trace method in milliseconds. In the Method Trace group widget, a timeline represents the duration of the response time. This data is derived from the ResponseTime attribute in the KQE REQUESTTRACE data set. Request context Displays the.net context of each request. The type of information in the request context depends on the request type. v For a JNDI request, the request context includes the JNDI resource URI. v For a JDBC request, the request context includes the data source name, the request name, and an SQL statement. v 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: No data is available if diagnostics mode is disabled. Select a trace in the method trace table to show context information for the trace. The following KPIs for the group widget are derived from the attributes as described: v Name: The parameter name in the name-value pair. This data is derived from the Key attribute in the KQE REQUESTCONTEXT data set. v Value: The parameter value in the name-value pair. This data is derived from the Value attribute in the KQE REQUESTCONTEXT data set. Request stack trace Displays the stack trace for the selected request or nested request. The data collector tracks the progress of a request. When a violation occurs, the data collector captures a stack trace. Use the stack trace to understand the context in which a method call was made. 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 No data is available if diagnostics mode is disabled. v No data is available if you disabled the collection of stack trace data. v Select a request in the method trace table to show the stack trace for the trace. The following KPIs for the group widget are derived from the attributes as described: v Fully Qualified Method Name: The class name, the method name within the class name, and the relevant line of the source. This data is derived from the FullyQualifiedMethodName attribute in the KQE REQUESTSTACKTRACE data set. 16 Monitoring Agent for Microsoft.NET Reference

23 Additional group widgets These pop-up group widgets are displayed after you click a group widget for more details. Some group widgets have links to more granular information in a popup widget, described here. The following group widgets are available in this dashboard: Diagnose Use diagnostics dashboards to get more details about requests. The following KPIs for the group widget are derived from the attributes as described: Custom charts and tables After you select a Microsoft.NET managed system instance, the Attribute Details tab is displayed in the dashboard. Open the tab to display options for creating a custom table or chart with attribute values from the Microsoft.NET data set that you select. Chapter 2. Dashboards 17

24 18 Monitoring Agent for Microsoft.NET Reference

25 Chapter 3. Eventing thresholds Thresholds test for certain conditions on your managed systems, such as memory usage over 95%, and raise an event when the conditions have been met. The agent comes with predefined thresholds that you can use to monitor your Microsoft.NET environment. You can create additional thresholds for the areas of interest. After you click System Configuration > Threshold Manager, select Microsoft.NET as the data source type to see all the available thresholds. Predefined eventing thresholds The thresholds are organized by the data set for which they were written. The Microsoft.NET agent has the following predefined thresholds: KQE_NET_AppRestarts Application restart. The default configuration has the following SQL syntax: *IF *VALUE KQE_ASP_NET_FILTER.Worker_Process_Restarts *GT 1 This threshold is evaluated every 5 minutes. The severity of this threshold is Warning. KQE_NET_Concurrent_Calls_Warn The connection to the socket is broken. The default configuration has the following SQL syntax: *IF *VALUE KQE_SERVICE_MODEL_SERVICE_FILTER.Percent_Of_Max_Concurrent_Calls *GT 90 This threshold is evaluated every 5 minutes. The severity of this threshold is Warning. KQE_NET_Exceptions_ThrownCrit The number of generated exceptions has exceeded the critical threshold. The default configuration has the following SQL syntax: *IF *VALUE KQE_NET_CLR_EXCEPTIONS.Number_of_Exceps_Thrown_Per_Sec *GE 500 *AND *VALUE KQE_NET_CLR_EXCEPTIONS.Name *NE _Global_ This threshold is evaluated every 2 minutes. The severity of this threshold is Critical. KQE_NET_Memory_ExGCcall_Warn Unexpected explicit calls to GC. The default configuration has the following SQL syntax: *IF *VALUE KQE_NET_CLR_MEMORY.Induced_GC *GT 100 *AND *VALUE KQE_NET_CLR_MEMORY.Name *NE _Global_ This threshold is evaluated every 15 minutes. The severity of this threshold is Warning. Copyright IBM Corp. 2008,

26 KQE_NET_Memory_GCtimeHIGH_CRIT High GC Time The default configuration has the following SQL syntax: *IF *VALUE KQE_NET_CLR_MEMORY.Percent_Time_in_GC *GT 15 *AND *VALUE KQE_NET_CLR_MEMORY.Name *NE _Global_ This threshold is evaluated every 5 minutes. The severity of this threshold is Critical. KQE_NET_Memory_GCtimeHIGH_WARN High GC Time The default configuration has the following SQL syntax: *IF *VALUE KQE_NET_CLR_MEMORY.Percent_Time_in_GC *GT 10 *AND *VALUE KQE_NET_CLR_MEMORY.Percent_Time_in_GC *LE 15 *AND *VALUE KQE_NET_CLR_MEMORY.Name *NE _Global_ This threshold is evaluated every 5 minutes. The severity of this threshold is Warning. KQE_NET_Memory_GC_HANDLES_HIGH More handlers to the external resources. The default configuration has the following SQL syntax: *IF *VALUE KQE_NET_CLR_MEMORY.Change_in_GC_Handles *GT 100 *AND *VALUE KQE_NET_CLR_MEMORY.Name *NE _Global_ This threshold is evaluated every 5 minutes. The severity of this threshold is Warning. KQE_NET_Memory_HighByteAlloc Unexpected rate of bytes allocation. The default configuration has the following SQL syntax: *IF *VALUE KQE_NET_CLR_MEMORY.Allocated_Bytes_Per_Sec *GT *AND *VALUE KQE_NET_CLR_MEMORY.Name *NE _Global_ This threshold is evaluated every 5 minutes. The severity of this threshold is Warning. KQE_NET_Memory_HighLOH Unexpected use of Large Object Heaps. The default configuration has the following SQL syntax: *IF *VALUE KQE_NET_CLR_MEMORY.Change_in_Large_Object_Heap_size *GT *AND *VALUE KQE_NET_CLR_MEMORY.Name *NE _Global_ This threshold is evaluated every 5 minutes. The severity of this threshold is Warning. KQE_NET_Memory_HighPinning Maximum objects are getting pinned. The default configuration has the following SQL syntax: *IF *VALUE KQE_NET_CLR_MEMORY.Number_of_Pinned_Objects *GT 100 *AND *VALUE KQE_NET_CLR_MEMORY.Name *NE _Global_ This threshold is evaluated every 5 minutes. 20 Monitoring Agent for Microsoft.NET Reference