CLM Server Monitoring - HTTP Client Request Monitor (DEPRECATED: CLM Server Monitoring is no longer supported and was dropped in version 6.0.3.)

The HTTP Client Request Monitor is responsible for gathering performance information of outgoing HTTP requests from the application; and monitoring whether a particular request exceeds the defined threshold.

JMX Interface Name: com.ibm.team.server.monitoring.management.MonitorRollupMBean
JMX Object Name: team.server.<application public URI context>@<port>:type=HTTP Client Request
JMX Object Name Example: team.server./jts@9443:type=HTTP Client Request

A JMX object of this "type" will be created for each monitored request URI. Different HTTP client requests to the same URI will be tracked and monitored by the same JMX object (identified by the URI); therefore the statistics gathered by that JMX object will consist of information of all the different outgoing HTTP client requests served at that URI.

• HTTP Client Request Monitor JMX Object Name: team.server.<application public URI context>@<port>:type=HTTP Client Request
  
• HTTP Client Request JMX Object Name: team.server.<application public URI context>@<port>:type=HTTP Client Request,name="<request URI>"
  

The HTTP Client Request performance metrics information are rolled up from the performance information from all the individual monitored request URIs invocations. Visually, the structure is like the following:

   team.server./<URL>@<port>:type=HTTP Client Request
          |
          |
          |---- team.server./<URL>@<port>:type=HTTP Client Request,name="<requestURI>"
          |---- team.server./<URL>@<port>:type=HTTP Client Request,name="<requestURI2>"
                                ...    
   

Monitor Attributes

Following are the attributes exposed by the HTTP Client Request

Note the attributes related with time statistics are expressed in milliseconds

Monitor Operations

Child MBeans

This section gathers information regarding MBeans that are contained within this monitor

HTTP Client Request objects

JMX Interface Name: com.ibm.team.server.monitoring.jmx.beans.HTTPClientMBean
JMX Object Name: team.server.<application public URI context>@<port>:type=HTTP Client Request,name="<requestURI>"
JMX Object Name Example: team.server./jts@9443:type=HTTP Client Request,name="https://<publicURI>:9443/jts/application-about"

It is important to understand that individual client operations can result in several HTTP requests performed, and all of these are tracked and monitored.

Attributes

Note the attributes related with time statistics are expressed in milliseconds

Operations

HTTP Client Request Problems

When a HTTP Client Request execution exceeds the monitor defined threshold, a Problem HTTP Client Request object is created. This object provides information that uniquely identifies the particular HTTP client request being served, that exceeded the threshold. The generated JMX object follows the convention:

JMX Interface Name: com.ibm.team.server.monitoring.jmx.beans.ResourceInstanceMBean
JMX Object Name: team.server.<application public URI context>@<port>:type=Problem HTTP Client Request,name="<requestURI>",id=ID
JMX Object Name Example: team.server./ccm@9443:type=Problem HTTP Client Request,name="https://sp013146.ibm.com:9443/jts/application-about",id=1d19f35a-54ab-4bb6-8318-0eac09fad878

Where name matches the one of the HTTP Client Request monitor object of which a execution originated this problem. A different problem object instance (with different ID) will be created each request call exceeding the defined threshold.

Attributes

Following are the attributes exposed by the Problem HTTP Client Request objects

Operations

External links:

• IBM

Additional contributors: TWikiUser, TWikiUser