The User Session monitor gathers information regarding user sessions in CLM monitored applications and the different activities executed under a user session. Sessions tracked and monitored include both: the ones created by users' operation; and the ones generated as result of internal applications tasks or as consequence of serving requests. A JMX object of this "type" will be created for each individual session, identified by the internal session ID.
JMX Interface Name: com.ibm.team.server.monitoring.jmx.beans.SessionMBean
JMX Object Name: team.server.<application public URI context>@<port>:type=Session,name="<userID>",id=<sessionID>
JMX Object Name Example: team.server./jts@9443:type=Session,name="bob",id=00C8658131D887F8A845116CAF027374
Every individual operation carried out in the context of a monitored user session will be tracked as child MBeans registered with the following naming convention:
- Session Activity JMX Object Name: team.server.<application public URI context>@<port>:type=Session,name="<userID>",id=<sessionID>,request=Activity,activityid=<ID>
Visually, the Session Monitor objects structure would look like the following:
team.server./<URL>@<port>:type=Session,name="<userName>",id=<sessionID>
|
|
| ---- team.server./<URL>@<port>:type=Session,name="<userName>",id=<sessionID>,request=Activity,activityid=<activityID>
|
| ---- team.server./<URL>@<port>:type=Session,name="<userName>",id=<sessionID>,request=Activity,activityid=<activity2ID>
...
Monitor Attributes
Following are the attributes exposed by the Session Monitor
JMX Attribute |
JMX Type |
Is Writeable? |
Default Value |
Description |
CreationTime |
java.util.Date |
No |
0 |
Time when this session was created |
Expiry |
java.util.Date |
No |
0 |
Time when the session will expire if no new activity is tracked for it. It is calculated based on the last recorded accessed time and the maximum inactivity time allowed |
LastAccessedTime |
java.util.Date |
No |
0 |
Last time the client sent a request associated with this session |
Links |
TabularType (Open Type) |
No |
|
Links to associated performance information |
URI |
String |
No |
http://jazz.net/ns/smarterserver/team.server//<publicURI>@<port>/Session//<ID> ; |
RDF subject URI representation of the JMX Object |
Username |
String |
No |
|
The ID of the user for the session. "" for application internal activities with no associated user ID |
Child MBeans
This section gathers information regarding MBeans that are contained within this monitor
Activity objects
Every individual operation performed in the context of a monitored user session is tracked as Activity JMX objects.
JMX Interface Name: com.ibm.team.server.monitoring.jmx.beans.ActivityMBean
JMX Object Name: team.server.<application public URI context>@<port>:type=Session,name="<userName>",id=<sessionID>,request=Activity,activityid=<ID>
JMX Object Name Example: team.server./jts@9443:type=Session,name="bob",id=06AA593EB36B08481074DAE286411E3D,request=Activity,activityid=0db5a4dc-5fd2-4c4c-8328-2487b35fcbd6
Attributes
JMX Attribute |
JMX Type |
Is Writeable? |
Default Value |
Description |
Duration |
long |
No |
0 |
Duration of the activity execution |
ProblemCount |
long |
No |
0 |
Number of problems generated while performing this activity. The Session Monitor itself doesn't have a threshold; problems will be issued if the associated monitor for the request or call being performed in the context of this activity generate a problem |
ActivityName |
String |
No |
|
The activity being performed. Depending on the operation it can be the context URI of a request, or a particular service call |
FinishDate |
java.util.Date |
No |
|
Recorded finish time of the activity execution |
Links |
TabularType (Open Type) |
No |
|
Links to associated performance information. This attribute is not currently used in this release |
RDF |
String |
No |
|
RDF Representation of this object. This attribute is not currently used in this release |
StartDate |
java.util.Date |
No |
|
Recorded start time of the activity execution |
ThreadID |
long |
No |
|
The ID of thread executing the activity: the request or service call |
ThreadName |
String |
No |
|
The ID of thread executing the activity: the request or service call |
ThreadTraceRDF |
String |
No |
|
The trace of other monitored object invocations along with their associated metrics as RDF. This attribute is not currently used in this release |
URI |
String |
No |
|
This attribute is not currently used in this release |
Operations
JMX Operation Signature |
Return Type |
Description |
dismiss() |
void |
When called, all the tracked problems generated as result of this activity will be discarded. Note that the problem JMX object will be discarded but problems counters for the activity are kept |
Session Activity Problems
When a Problem is created in the context of a CLM Server Monitoring Monitor, a
Problem Activity object is also generated that correlates to the user session activity under which the offending operation was being performed. This object provides information that uniquely identifies the particular activity being performed, and the session. The generated JMX object follows the convention:
JMX Interface Name: com.ibm.team.server.monitoring.jmx.beans.ActivityMBean
JMX Object Name: team.server.<application public URI context>@<port>:type=Problem Activity, id=ID
Where
id
matches the
activityid
of a monitored activity under the User Session Monitor.
Attributes
Following are the attributes exposed by the Problem Activity objects
JMX Attribute |
JMX Type |
Is Writeable? |
Default Value |
Description |
ActivityName |
String |
No |
|
The activity being performed. Depending on the operation it can be the context URI of a request, or a particular service call |
Duration |
long |
No |
0 |
Duration of the activity execution |
FinishDate |
java.util.Date |
No |
|
Recorded finish time of the activity execution |
Links |
TabularType (Open Type) |
No |
|
Links to associated performance information. This attribute is not currently used in this release |
ProblemCount |
long |
No |
0 |
Number of problems generated while performing this activity. The Session Monitor itself doesn't have a threshold; problems will be issued if the associated monitor for the request or call being performed in the context of this activity generate a problem |
RDF |
String |
No |
|
RDF Representation of this object. This attribute is not currently used in this release |
StartDate |
java.util.Date |
No |
|
Recorded start time of the activity execution |
ThreadID |
long |
No |
|
The ID of thread executing the activity: the request or service call |
ThreadName |
String |
No |
|
The ID of thread executing the activity: the request or service call |
ThreadTraceRDF |
String |
No |
|
The trace of other monitored object invocations along with their associated metrics as RDF. This attribute is not currently used in this release |
URI |
String |
No |
|
This attribute is not currently used in this release |
Operations
External links: