Page tree

The following table lists events that you can generate from application servers with BMC Application Diagnostics Agents. An event is a notification that sent by the system when a threshold is breached. Events are sent from the Diagnostics Agents set to App, Web, or Business Tiers. Some events are platform dependent (either Java servers or .NET servers), but most can be sent from both platforms.

You can configure the most of the default threshold for events on the Transaction SLA Configuration and the Server SLA Configuration pages, and some events are managed in the agent policy files. If the value of a threshold is not provided (or commented out in the agent policy), then events are not sent for that threshold.

Tip

To expand the table for online reading, press the F key to turn the full screen view on or off.

Events sent for App, Web, or Business tiers

EventUnitDescription

Warning1
threshold

Critical1
threshold
Platform

Vendor
limitations

CPU Usage - Average

 
%

Java: Average percentage of CPU used by the JVM process

.NET: Average percentage of CPU used by all traced ASP.NET worker processes

2535Java and .NETNone
Database Breach Rate%

Percentage of database requests that cross the latency threshold

510Java and .NET.NET: MS SQL 2005 and 2008, Oracle 10 and 11 
Database Durationms

Maximum time spent on database exits, as measured on sampled database requests

Event not sent by default

nonenone None
Database Error Rate%Percentage of database requests with errors510Java and .NET.NET: MS SQL 2005 and 2008, Oracle 10 and 11

Deadlock - Average

# of threadsAverage number of threads in a deadlock state510JavaNone

Garbage Collection Count

# of GC cycles

Java: Sum of garbage collection (GC) cycles invoked by all GC algorithms

.NET: Sum of the number of generation 0 calls

Note: For WebSphere 8.5 application servers, the Garbage Collection Count metric and event displays a value that is different from the value displayed in the JConsole tool. The value in BMC Application Diagnostics is displayed as it is received from WebSphere.

Event not sent by default.

nonenoneJava and .NETNone

Garbage Collection Time

ms

Java: Sum of the time spent on GC cycles by all GC algorithms

.NET: Sum of the time spent on generation 0 calls

30

60

Java and .NETNone

Heap Size Committed

MB

Java: Sum of committed memory in all heap pools, measured after GC and as reported by JVM

.NET: Amount of virtual memory currently committed by the GC

Event not sent by default

nonenoneJava and .NETNone

Heap Size Used

MB

Java: Sum of committed memory in all heap pools, measured after GC and as reported by JVM

.NET: Amount of virtual memory currently committed by the GC

Event not sent by default

nonenoneJava and .NETNone
JCA Connection Pool%JCA Connection Pool on WebSphere and WebLogic8090JavaNone
JDBC Connection Pool%JDBC Connection Pool on WebSphere and WebLogic8090JavaNone

Memory Pages Per Second

pages/sRate of paging memory to and from the server100200.NETNone

Memory Usage - Average

%

Java: Percentage of memory marked as used by all heap pools

.NET: Percentage of the average values of virtual and private memory used by all traced ASP.NET worker processes. The values are defined in the agent policy file.

Note: For WebSphere 7 application servers, the Memory Usage metrics and events sometimes display values greater than 100%. The value is displayed as it is received from WebSphere, and the same results are displayed in the JConsole tool.

7590Java and .NETNone

Permanent Generation - Used

MB

Memory used for the Permanent Generation pool

Event not sent by default

nonenoneJavaNone
Permanent Generation - MaximumMB

Maximum memory used for the Permanent Generation pool

Event not sent by default

nonenoneJavaNone

Processor Queue Length

# of threadsNumber of ready (not running) threads in the processor queue8001000.NETNone

Processor Time

%

Percentage of elapsed time for all processes of the OS that the processor spends to execute a nonidle thread

Event not sent by default

nonenone.NETNone

Requests Queued

# of requestsAverage number of ASP.NET requests waiting to be processed500750.NETNone

Requests Wait Time

ms

Average time that the ASP.NET request waited in the queue. The request time is measured periodically and does not correspond to all requests, serving as an indicator.

Event not sent by default

510.NETNone

Restarted Application Pools

# of processes

Sum of all restarted worker processes in all of the application pools

Event not sent by default

nonenone.NETNone

Thread Count - Average

# of threads

Java: Average number of threads used by the JVM process

.NET: Average number of threads used by all traced ASP.NET worker processes

500750Java and .NETNone

Thread Pools Active Threads

# of threads

 Number of active threads on the application server

 

500750JavaWebSphere, WebLogic 11g and later
Percent of Thread Pool Used%Percentage of the thread pool that is used8090JavaWebSphere, WebLogic
Transaction Error Violations%Percentage of the transactions with errors510Java and .NETNone

Transaction Latency Violations

%Percentage of the transactions that cross the latency threshold510Java and .NETNone
Web Services Duration - AveragemsAverage time spent on web service exits, as measured on sampled requests, that are marked as exit points and as tier "w_s" in the recording profile3060.NETNone

1 If you upgraded from an earlier version of BMC Application Diagnostics, the names of the properties appear in the Agent Policy files and use the terms tolerating and frustrated to represent warning and critical thresholds, respectively; for example:
global.error.tolerating.event.threshold=5
global.error.frustrated.event.threshold=10

Related topics

Application server metrics

Modifying an Agent policy file

Configuring SLA rules for application servers

Configuring SLA rules for business transactions