Agileload Logo

Anomalies Management

The WebSphere collector allows to insert the following types of anomalies in an anomalies profile:

CPU Usage

CPU Usage Alert is raised when the use of server CPU excess the defined severities.

The default anomaly conditions are:
Severity 1: The ratio is greater than 75%
Severity 2: The ratio is 
greater than 80%
Severity 3: The ratio is 
greater than 90%

JVM Used Memory

JVM Used Memory Alert is the ratio between used memory and current memory in the JVM Heap.

The JVM Used Memory is the currently memory really used by the memory. The current memory in the heap is different, because it matches to the current memory that the JVM keeps, but don't use. If the used memory is too important, the JVM will then increase the size of the allocated memory.

The default anomaly conditions are:
Severity 1: The ratio is greater than 75%
Severity 2: The ratio is 
greater than 80%
Severity 3: The ratio is 
greater than 90%


Thread Pool Size

Thread Pool Size alert is raised when the ratio of used thread on total thread is greater than the selected severities.

The default anomaly conditions are:
Severity 1: The ratio is greater than 70%
Severity 2: The ratio is 
greater than 80%
Severity 3: The ratio is 
greater than 90%


Servlet Response Time

Servlet response time is the ratio of recent average response time (last polling cycle) to the historical average response time (since the server was restarted).

The default anomaly conditions are:
Severity 1: The ratio is greater than 5%
Severity 2: The 
ratio is greater than 50%
Severity 3: The 
ratio is greater than 100%


EJB Response Time

EJB response time is the ratio of recent average response time (last polling cycle) to the historical average response time (since the server was restarted). This alert will raised for any kind of EJB type (Stateless, Stateful, Entity and Message Driven).

The default anomaly conditions are:
Severity 1: The ratio is greater than 5%
Severity 2: The 
ratio is greater than 50%
Severity 3: The 
ratio is greater than 100%


JCA Resource
Response Time

JCA Resource response time is the ratio of recent average response time (last polling cycle) to the historical average response time (since the server was restarted).

The default anomaly conditions are:
Severity 1: The ratio is greater than 5%
Severity 2: The 
ratio is greater than 50%
Severity 3: The 
ratio is greater than 100%


JCA Resource Pool Size

JCA Resource Pool Used is the number of active connections divided by the capacity of the pool.

The default anomaly conditions are:
Severity 1: The ratio is greater than 70%
Severity 2: The ratio is 
greater than 80%
Severity 3: The ratio is 
greater than 90%


JCA Resource Waiting Threads

JCA Resource Waiting Threads is the number of threads waiting for a free instance of a connections.

The default anomaly conditions are:
Severity 1: The thread count is greater than 0
Severity 2: The 
thread count is greater than 2
Severity 3: The 
thread count is greater than 6


JDBC Resource Response Time

JDBC Resource response time is the ratio of recent average response time (last polling cycle) to the historical average response time (since the server was restarted).

The default anomaly conditions are:
Severity 1: The ratio is greater than 5%
Severity 2: The 
ratio is greater than 50%
Severity 3: The 
ratio is greater than 100%


JDBC Resource Pool Size

JDBC Resource Pool Used is the number of active connections divided by the capacity of the pool.

The default anomaly conditions are:
Severity 1: The ratio is greater than 70%
Severity 2: The ratio is 
greater than 80%
Severity 3: The ratio is 
greater than 90%


JDBC Resource Waiting Threads

JDBC Resource Waiting Threads is the number of threads waiting for a free instance of a connections.

The default anomaly conditions are:
Severity 1: The thread count is greater than 0
Severity 2: The 
thread count is greater than 2
Severity 3: The 
thread count is greater than 6


JTA Resource Rollback

JTA Rollback Alert is raised when the number of transactions rolled back divided by the total of transactions is greater than the selected severities.

The default anomaly conditions are:
Severity 1: The ratio is greater than 25%
Severity 2: The ratio is 
greater than 50%
Severity 3: The ratio is 
greater than 60%






Go back to the Learning center:


Copyright © AgileLoad. All rights reserved.
Agile Load testing tool| Contact AgileLoad | Terms of Use | Sitemap