<div id="header-title" style="padding: 10px 15px; border-width:1px; border-style:solid; border-color:#FFD28C; background-image: url(<nop>https://jazz.net/wiki/pub/Deployment/WebPreferences/TLASE.jpg); background-size: cover; font-size:120%"> ---+!!<!--img src="https://jazz.net/wiki/pub/Deployment/WebPreferences/uc.png" alt="uc.png" width="50" height="50" align="right"--> Smarter Server - Database Statement Monitor %DKGRAY% Authors: Main.JorgeAlbertoDiaz <br> Build basis: Collaborative Lifecycle Management 4.0.4 %ENDCOLOR%</div></sticky> <!-- Page contents top of page on right hand side in box --> <sticky><div style="float:right; border-width:1px; border-style:solid; border-color:#DFDFDF; background-color:#F6F6F6; margin:0 0 15px 15px; padding: 0 15px 0 15px;"> %TOC{title="Page contents"}% </div></sticky> <sticky><div style="margin:15px;"></sticky> #DBMonitorAnchor The DB Statement Monitor is responsible for gathering performance information of the creation and processing of database statements. *JMX Interface Name:* =com.ibm.team.server.monitoring.management.MonitorRollupMBean= <br/> *JMX Object Name:* team.server.<application public URI context>@<port>:type=DB Statement <br/> *JMX Object Name Example:* team.server./jts@9443:type=DB Statement <br/> A JMX object of this "type" will be created for each statement and each SQL statement processing phase: Prepare or Execute. * *DB Statement Monitor JMX Object Name:* team.server.<application public URI context>@<port>:type=DB Statement <br/> * *DB Statement JMX Object Name:* team.server.<application public URI context>@<port>:type=DB Statement,phase=(Prepare | Execute),name=<statement> <br/> The DB Statement Monitor performance metrics information gathered in its attributes is a rolled up of the performance information from all the individual monitored database statements. Visually, the DB Statement Monitor objects structure is like the following: <verbatim> team.server./<URL>@<port>:type=Cache | | |----Prepare | | | | | ---- team.server./<URL>@<port>:type=DB Statement,phase=Prepare,name="<statement>" | ... |----Execute | | ---- team.server./<URL>@<port>:type=DB Statement,phase=Execute,name="<statement>" ... </verbatim> ---++ Monitor Attributes Following are the attributes exposed by the DB Statement Monitor | *JMX Attribute* | *JMX Type* | *Is Writeable?* | *Default Value* | *Description* | | !AverageResponseTime | long | Yes | 0 | Average response time from all the DB statements | | !Count | long | Yes | 0 | Counter of all monitored operations | | !Duration | long | Yes | 0 | Total duration of DB statements processing operations | | !Enabled | boolean | Yes | false | Whether this monitor is enabled. Default is disabled so no performance monitoring of DB statements is performed | | !MaximumResponseTime | long | Yes | 0 | Maximum response time from all the DB statements operations | | !MinimumResponseTime | long | Yes | 0 | Minimum response time from all the DB statements operations | | !Threshold | java.lang.Long | Yes | 0 | Defines the maximum allowed time for a DB statement to be processed. If this time is exceeded a problem will be generated | | !TimeSinceLastReset | long | No | 0 | Total time since the last statistics reset | Note the attributes related with time statistics are expressed in miliseconds ---++ Monitor Operations | *JMX Operation Signature* | *Return Type* | *Description* | | dismissAllProblems() | void | When called, all the problems tracked by this monitor are dismissed | | reset() | void | When called, resets the statistics of the monitor | ---++ Child MBeans This section gathers information regarding MBeans that are contained within this monitor ---+++ DB Statement objects #DBStatementAnchor An instance of a monitored DB statement object in Prepare or Execute phase. A different JMX object is created for the Prepare and Execute phases of the statement processing. *JMX Interface Name:* =com.ibm.team.server.monitoring.jmx.beans.sql.SQLStatementRollupMBean= <br/> *JMX Object Name:* team.server.<application public URI context>@<port>:type=DB Statement,phase=(Prepare | Execute),name=<<statement>> <br/> *JMX Object Name Example 1 (DB Statement Prepare phase):* team.server./ccm@9443:type=DB Statement,phase=Prepare,name="select t1.ITEM_ID, t1.STATE_ID from FRIENDS.FRIEND t1"<br/> *JMX Object Name Example 2 (DB Statement Execute phase):* team.server./ccm@9443:type=DB Statement,phase=Execute,name="select t1.ITEM_ID, t1.STATE_ID from FRIENDS.FRIEND t1" ---++++ Attributes | *JMX Attribute* | *JMX Type* | *Is Writeable?* | *Default Value* | *Description* | | !AverageResponseTime | long | Yes | 0 | Average response time spent processing this statement | | !Count | long | Yes | 0 | Counter of monitored operations | | !Duration | long | Yes | 0 | Total duration of the processing operations for this statement | | !MaximumResponseTime | long | Yes | 0 | Maximum response time that took to process this statement | | !MinimumResponseTime | long | Yes | 0 | Minimum response time that took to process this statement | | !SQL | java.lang.String | No | SQL statement | SQL statement. It matches the value of "name" of the JMX Object name of this statement instance removing scaping characters | | !TimeSinceLastReset | long | No | 0 | Total time since the last statistics reset | Note the attributes related with time statistics are expressed in miliseconds ---++++ Operations | *JMX Operation Signature* | *Return Type* | *Description* | | reset() | void | When called, resets the statistics of this monitored statement | <br/> <hr/> ---+++++!! External links: * [[https://www.ibm.com][IBM]] ---+++++!! Additional contributors: Main.TWikiUser, Main.TWikiUser <sticky></div></sticky>
This topic: Deployment
>
SmarterServerDataDictionary
>
CLMServerMonitoringDBStatementMonitor
History: r2 - 2013-07-18 - 15:22:26 -
JorgeAlbertoDiaz
Copyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our
Terms of Use.
Please read the following
disclaimer
.