Opensta Performance testing tool

Response-Time Analysis Made Easy in Oracle Database 10g

2008-10-07T21:10:00.000-07:00

Response-Time Analysis Made Easy in Oracle Database 10g

With Oracle Database 10g, many previously difficult-to-attain response-time metrics are now at your fingertips.

Downloads for this article:

Oracle Database 10g

Historically, in trying to achieve maximum database performance, Oracle DBAs and performance analysts have fought an uphill battle to obtain solid response time metrics for system as well as user session activity. The problem facing DBAs has always had two facets: first, determining exactly "where" the database or user sessions have been spending their time; and second, determining the objective nature of the user experience.

Given all the possible activities and interactions within the database, these tasks are far from trivial. The Oracle Wait Interface, which was introduced many versions ago, has been a great jump-start for admins who know how to use it, but even it has lacked the ideal ability to tell a DBA how well the system or user sessions have efficiently processed transactions or queries. Enabling and poring over trace files can garner this level of detail, but for most overworked DBAs who have to manage large database farms, this exercise is a luxury.

Fortunately, those Oracle DBAs who have upgraded to Oracle Database 10g will find major response-time enhancements that allow a much better picture to be presented about system and session-level response-time metrics. Most significantly, the Oracle Automatic Database Diagnostic Monitor (ADDM) provides insights into response times and much more by automatically analyzing collected statistics, identifying problem areas, and even providing recommendations through the Oracle Enterprise Manager Grid Control GUI.

Furthermore, and most relevant to our discussion here, historical mechanisms in Oracle Database 10g allow DBAs to look back in time to perform their own response-time trend analysis, which helps them determine peak and nonpeak transaction/system times as well as locate rogue processes and SQL that elongate batch cycles or ETL jobs.

In this article, I'll explore the use of some of these historical mechanisms at the system, session, and SQL levels. For more information about ADDM, see the Oracle documentation as well as the "ADDM and SQL Tuning Advisor" installment of Arup Nanda's "Oracle Database 10g: Top 20 Features for DBAs."

System-Level Response-Time Analysis

Starting at the global or system level, DBAs typically want answers to these questions:

• In general, how well is my database running? What defines efficiency?

• What average response time are my users experiencing?

• Which activities affect overall response time the most?

The answers to these questions have been fairly elusive for DBAs before Oracle Database 10g, but now such metrics can be somewhat easy to capture if you happen to be using the latest and greatest Oracle database.

First of all, part of the answer to how well, in general, a database is running can be obtained by issuing this query in Oracle Database 10g:

select METRIC_NAME,

VALUE

from SYS.V_$SYSMETRIC

where METRIC_NAME IN ('Database CPU Time Ratio',

'Database Wait Time Ratio') AND

INTSIZE_CSEC =

(select max(INTSIZE_CSEC) from SYS.V_$SYSMETRIC);

METRIC_NAME VALUE

------------------------------ ----------

Database Wait Time Ratio 6

Database CPU Time Ratio 94

The Oracle Database 10g V$SYSMETRIC view contains several excellent response-time metrics, two of which are the Database Wait Time Ratio and Database CPU Time Ratio. The query above shows the latest snapshot of these two statistics, which help you determine if your database is currently experiencing a high percentage of waits/bottlenecks vs. smoothly running operations. The Database CPU Time Ratio is calculated by dividing the amount of CPU expended in the database by the amount of "database time," which is defined as the time spent by the database on user-level calls (with instance background process activity being excluded). High values (90-95+ percent) are good and indicate few wait/bottleneck actions, but take this threshold only as a general rule of thumb because every system is different.

You can also take a quick look over the last hour to see if the database has experienced any dips in overall performance by using this query:

select end_time,

value

from sys.v_$sysmetric_history

where metric_name = 'Database CPU Time Ratio'

order by 1;

END_TIME VALUE

-------------------- ----------

22-NOV-2004 10:00:38 98

22-NOV-2004 10:01:39 96

22-NOV-2004 10:02:37 99

22-NOV-2004 10:03:38 100

22-NOV-2004 10:04:37 99

22-NOV-2004 10:05:38 77

22-NOV-2004 10:06:36 100

22-NOV-2004 10:07:37 96

22-NOV-2004 10:08:39 100

And, you can get a good idea of the minimum, maximum, and average values of overall database efficiency by querying the V$SYSMETRIC_SUMMARY view with a query such as this:

select CASE METRIC_NAME

WHEN 'SQL Service Response Time' then 'SQL Service Response Time (secs)'

WHEN 'Response Time Per Txn' then 'Response Time Per Txn (secs)'

ELSE METRIC_NAME

END METRIC_NAME,

CASE METRIC_NAME

WHEN 'SQL Service Response Time' then ROUND((MINVAL / 100),2)

WHEN 'Response Time Per Txn' then ROUND((MINVAL / 100),2)

ELSE MINVAL

END MININUM,

CASE METRIC_NAME

WHEN 'SQL Service Response Time' then ROUND((MAXVAL / 100),2)

WHEN 'Response Time Per Txn' then ROUND((MAXVAL / 100),2)

ELSE MAXVAL

END MAXIMUM,

CASE METRIC_NAME

WHEN 'SQL Service Response Time' then ROUND((AVERAGE / 100),2)

WHEN 'Response Time Per Txn' then ROUND((AVERAGE / 100),2)

ELSE AVERAGE

END AVERAGE

from SYS.V_$SYSMETRIC_SUMMARY

where METRIC_NAME in ('CPU Usage Per Sec',

'CPU Usage Per Txn',

'Database CPU Time Ratio',

'Database Wait Time Ratio',

'Executions Per Sec',

'Executions Per Txn',

'Response Time Per Txn',

'SQL Service Response Time',

'User Transaction Per Sec')

ORDER BY 1

METRIC_NAME MINIMUM MAXIMUM AVERAGE

------------------------------ ---------- ---------- ----------

CPU Usage Per Sec 0 7 1

CPU Usage Per Txn 1 29 8

Database CPU Time Ratio 61 100 94

Database Wait Time Ratio 0 39 5

Executions Per Sec 2 60 8

Executions Per Txn 16 164 41

Response Time Per Txn (secs) 0 .28 .08

SQL Service Response Time (sec 0 0 0

User Transaction Per Sec 0 1 0

The query above contains more response-time metrics than simply the Database CPU and Wait Time Ratios (we'll cover those later), but you can see the benefit in being able to acquire this information. For this particular instance, the average Database CPU Time Ratio is 94, which is well within our acceptable limits.

The next question DBAs pose at the system level involves the average level of response time that their user community is experiencing. (Prior to Oracle Database 10g this type of data was difficult to capture, but not anymore.) The query shown above that interrogates the V$SYSMETRIC_SUMMARY view tells us what we need to know. If complaints of unacceptable response times are mounting from users, the DBA can check the Response Time Per Txn and SQL Service Response Time metrics to see if a database issue exists. For example, the statistics shown above report that the maximum response time per user transaction has been only .28 second, with the average response time being a blazing .08 second. Oracle certainly wouldn't be to blame in this case.

If, however, response times are longer than desired, the DBA will then want to know what types of user activities are responsible for making the database work so hard. Again, before Oracle Database 10g, this information was more difficult to acquire, but now the answer is only a query away:

select case db_stat_name

when 'parse time elapsed' then

'soft parse time'

else db_stat_name

end db_stat_name,

case db_stat_name

when 'sql execute elapsed time' then

time_secs - plsql_time

when 'parse time elapsed' then

time_secs - hard_parse_time

else time_secs

end time_secs,

case db_stat_name

when 'sql execute elapsed time' then

round(100 * (time_secs - plsql_time) / db_time,2)

when 'parse time elapsed' then

round(100 * (time_secs - hard_parse_time) / db_time,2)

else round(100 * time_secs / db_time,2)

end pct_time

from

(select stat_name db_stat_name,

round((value / 1000000),3) time_secs

from sys.v_$sys_time_model

where stat_name not in('DB time','background elapsed time',

'background cpu time','DB CPU')),

(select round((value / 1000000),3) db_time

from sys.v_$sys_time_model

where stat_name = 'DB time'),

(select round((value / 1000000),3) plsql_time

from sys.v_$sys_time_model

where stat_name = 'PL/SQL execution elapsed time'),

(select round((value / 1000000),3) hard_parse_time

from sys.v_$sys_time_model

where stat_name = 'hard parse elapsed time')

order by 2 desc;

DB_STAT TIME_SECS PCT_TIME

----------------------------- --------- --------

sql execute elapsed time 13263.707 45.84

PL/SQL execution elapsed time 13234.738 45.74

hard parse elapsed time 1943.687 6.72

soft parse time 520.584 1.8

The example output above shows a database that has spent the vast majority of its time handling SQL and PL/SQL requests. Complete descriptions of all the statistics supported by the V$SYS_TIME_MODEL view can be found here.

In addition to active time, a DBA will want to know the global wait times as well. Prior to Oracle Database 10g, a DBA had to view individual wait events to understand waits and bottlenecks, but now Oracle provides a summary/rollup mechanism for waits via wait classes:

select WAIT_CLASS,

TOTAL_WAITS,

round(100 * (TOTAL_WAITS / SUM_WAITS),2) PCT_WAITS,

ROUND((TIME_WAITED / 100),2) TIME_WAITED_SECS,

round(100 * (TIME_WAITED / SUM_TIME),2) PCT_TIME

from

(select WAIT_CLASS,

TOTAL_WAITS,

TIME_WAITED

from V$SYSTEM_WAIT_CLASS

where WAIT_CLASS != 'Idle'),

(select sum(TOTAL_WAITS) SUM_WAITS,

sum(TIME_WAITED) SUM_TIME

from V$SYSTEM_WAIT_CLASS

where WAIT_CLASS != 'Idle')

order by 5 desc;

WAIT_CLASS TOTAL_WAITS PCT_WAITS TIME_WAITED_SECS PCT_TIME

--------------- ----------- ---------- ---------------- ----------

User I/O 2245204 7.48 4839.43 54.39

System I/O 2438387 8.12 2486.21 27.94

Application 920385 3.07 513.56 5.77

Other 39962 .13 422.36 4.75

Commit 200872 .67 284.76 3.2

Network 24133213 80.38 162.26 1.82

Concurrency 6867 .02 102.63 1.15

Configuration 39377 .13 86.21 .97

It's much easier to tell now that the bulk of overall wait time is due, for example, to user I/O waits than to try to tally individual wait events to get a global picture. As with response-time metrics, you can also look back in time over the last hour with a query like this one:

select to_char(a.end_time,'DD-MON-YYYY HH:MI:SS') end_time,

b.wait_class,

round((a.time_waited / 100),2) time_waited

from sys.v_$waitclassmetric_history a,

sys.v_$system_wait_class b

where a.wait_class# = b.wait_class# and

b.wait_class != 'Idle'

order by 1,2;

END_TIME WAIT_CLASS TIME_WAITED

-------------------- --------------- -----------

22-NOV-2004 11:28:37 Application 0

22-NOV-2004 11:28:37 Commit .02

22-NOV-2004 11:28:37 Concurrency 0

22-NOV-2004 11:28:37 Configuration 0

22-NOV-2004 11:28:37 Network .01

22-NOV-2004 11:28:37 Other 0

22-NOV-2004 11:28:37 System I/O .05

22-NOV-2004 11:28:37 User I/O 0

You can, of course, just focus on a single SID with the V$SESS_TIME_MODEL view and obtain data for all statistical areas of a session. You can also view current session wait activity using the new wait classes using the following query:

select a.sid,

b.username,

a.wait_class,

a.total_waits,

round((a.time_waited / 100),2) time_waited_secs

from sys.v_$session_wait_class a,

sys.v_$session b

where b.sid = a.sid and

b.username is not null and

a.wait_class != 'Idle'

order by 5 desc;

SID USERNAME WAIT_CLASS TOTAL_WAITS TIME_WAITED_SECS

--- ---------- --------------- ----------- ----------------

257 SYSMAN Application 356104 75.22

255 SYSMAN Commit 14508 25.76

257 SYSMAN Commit 25026 22.02

257 SYSMAN User I/O 11924 19.98

After this stage, you can check the standard individual wait events as you've been able to do in earlier versions of Oracle with V$SESSION_WAIT and V$SESSION_EVENT. You'll also find the new wait classes in these two modified views with Oracle Database 10g.

If you need to look back in time to discover what sessions were logged on and consuming the most resources, you can use the following query. In the example below, we're looking at activity from midnight to 5 a.m. on November 21, 2004, that involved user I/O waits:

select sess_id,

username,

program,

wait_event,

sess_time,

round(100 * (sess_time / total_time),2) pct_time_waited

from

(select a.session_id sess_id,

decode(session_type,'background',session_type,c.username) username,

a.program program,

b.name wait_event,

sum(a.time_waited) sess_time

from sys.v_$active_session_history a,

sys.v_$event_name b,

sys.dba_users c

where a.event# = b.event# and

a.user_id = c.user_id and

sample_time > '21-NOV-04 12:00:00 AM' and

sample_time < '21-NOV-04 05:00:00 AM' and

b.wait_class = 'User I/O'

group by a.session_id,

decode(session_type,'background',session_type,c.username),

a.program,

b.name),

(select sum(a.time_waited) total_time

from sys.v_$active_session_history a,

sys.v_$event_name b

where a.event# = b.event# and

sample_time > '21-NOV-04 12:00:00 AM' and

sample_time < '21-NOV-04 05:00:00 AM' and

b.wait_class = 'User I/O')

order by 6 desc;

SESS_ID USERNAME PROGRAM WAIT_EVENT SESS_TIME PCT_TIME_WAITED

------- -------- ---------- ------------------------- ---------- -------------

242 SYS exp@RHAT9K db file scattered read 3502978 33.49

242 SYS oracle@RHA db file sequential read 2368153 22.64

242 SYS oracle@RHA db file scattered read 1113896 10.65

243 SYS oracle@RHA db file sequential read 992168 9.49

The Oracle Database 10g V$ACTIVE_SESSION_HISTORY view comes into play here to provide an insightful look back in time at session experiences for a given time period. This view gives you a lot of excellent information without the need for laborious tracing functions. We'll see more use of it in the next section, which deals with analyzing the response times of SQL statements.

SQL Response-Time Analysis

Examining the response time of SQL statements became easier in Oracle9i, and with Oracle Database 10g, DBAs have many tools at their disposal to help them track inefficient database code.

Historically the applicable V$ view here has been V$SQLAREA. Starting with Oracle9i, Oracle added the ELAPSED_TIME and CPU_TIME columns, which have been a huge help in determining the actual end user experience of a SQL statement execution (at least, when dividing them by the EXECUTIONS column, which produces the average amount of time per execution).

In Oracle Database 10g, six new wait-related and timing columns have been added to V$SQLAREA:

• APPLICATION_WAIT_TIME

• CONCURRENCY_WAIT_TIME

• CLUSTER_WAIT_TIME

• USER_IO_WAIT_TIME

• PLSQL_EXEC_TIME

• JAVA_EXEC_TIME

The new columns are helpful in determining, for example, the amount of time that a procedure spends in PL/SQL code vs. standard SQL execution, and if a SQL statement has experienced any particular user I/O waits. For example, a query you could use to find the top five SQL statements with the highest user I/O waits would be:

select *

from

(select sql_text,

sql_id,

elapsed_time,

cpu_time,

user_io_wait_time

from sys.v_$sqlarea

order by 5 desc)

where rownum < 6;

SQL_TEXT SQL_ID ELAPSED_TIME CPU_TIME USER_IO_WAIT_TIME

------------------------- ------------ ------------ ---------- ---------------

select /*+ rule */ bucket db78fxqxwxt7 47815369 19000939 3423

SELECT :"SYS_B_0" FROM SY agdpzr94rf6v 36182205 10170226 2649

select obj#,type#,ctime,m 04xtrk7uyhkn 28815527 16768040 1345

select grantee#,privilege 2q93zsrvbdw4 28565755 19619114 803

select /*+ rule */ bucket 96g93hntrzjt 9411028 3754542 606

Of course, getting the SQL statements with the highest elapsed time or wait time is good, but you need more detail to get to the heart of the matter—which is where the V$ACTIVE_SESSION_HISTORY view again comes into play. With this view, you can find out what actual wait events delayed the SQL statement along with the actual files, objects, and object blocks that caused the waits (where applicable).

For example, let's say you've found a particular SQL statement that appears to be extremely deficient in terms of user I/O wait time. You can issue the following query to get the individual wait events associated with the query along with the corresponding wait times, files, and objects that were the source of those waits:

select event,

time_waited,

owner,

object_name,

current_file#,

current_block#

from sys.v_$active_session_history a,

sys.dba_objects b

where sql_id = '6gvch1xu9ca3g' and

a.current_obj# = b.object_id and

time_waited <> 0;

EVENT TIME_WAITED OWNER OBJECT_NAME file block

------------------------- ----------- ------ --------------------- ---- ------

db file sequential read 27665 SYSMAN MGMT_METRICS_1HOUR_PK 3 29438

db file sequential read 3985 SYSMAN SEVERITY_PRIMARY_KEY 3 52877

Of course, you can use V$ACTIVE_SESSION_HISTORY in a historical fashion to narrow down unoptimized SQL statements for a particular time period. The point is that Oracle Database 10g makes it a lot easier to conduct response-time analysis on SQL statements with simplified data dictionary views, as opposed to the time-consuming trace-and-digest method.

Conclusion

DBAs and performance analysts who manage the performance of Oracle Database 10g will find many of the response-time metrics they've yearned for over the years now at their fingertips in the latest release of Oracle's flagship database. Such statistics will help accelerate the process of finding the proverbial needle in the haystack of large and complex database performance situations.

________________________________________

Robin Schumacher (Robin.Schumacher@embarcadero.com) is vice president of product management at Embarcadero Technologies, a leading supplier of database software tools. He has 16 years' experience with database engines and has been a feature writer and software reviewer for many database-related publications. Robin is also the author of Oracle Performance Troubleshooting (Rampant TechPress), which has been updated to include Oracle Database 10g diagnostics.

Microsoft BizTalk Server Metrics

2008-09-22T08:37:00.000-07:00

Microsoft BizTalk Server Metrics

The Microsoft BizTalk Server 2004 management plug-in for Oracle Enterprise Manager provides performance monitoring of BizTalk Server using performance counters and application events.

This chapter provides descriptions for all Microsoft BizTalk Server metric categories, and tables list and describe associated metrics for each category. The tables also provide user actions if any of the metrics for a particular category support user actions.

BizTalk BAS Inbox Document Library Metrics

A document library in SharePoint Services that BAS uses for receiving messages and documents from a running business process (BizTalk Orchestration) is called an Inbox. This is conceptually analogous to the Inbox used in a typical e-mail system.

The metrics in this category provide performance-related information about the Inbox.

Table 6-1 BizTalk BAS Inbox Document Library Metrics

Metric	Description
Total Fallbacks to Orphaned Messages	Total number of messages redirected from the partner index library, Inbox folder, to the Orphaned Messages document library because of an issue with the partner.
Total Inbox Failures	Total number of messages submitted by the Microsoft BizTalk Server that failed to persist into Windows SharePoint Services. The BizTalk Server resubmits these messages until they persist successfully or until the number of retries is exceeded.
Total Non Office Documents Created	Total number of messages successfully saved as is in the partner index library, Inbox folder, because of failure(s) to transform into InfoPath document(s).
Total Office Documents Created	Total number of InfoPath documents created in the partner document library, Inbox folder.

BizTalk BAS Outbox Document Library Metrics

A document library in SharePoint Services that BAS uses for sending messages and documents to a running business process (BizTalk Orchestration) is called an Outbox. This is conceptually analogous to the Outbox used in a typical e-mail system.

The metrics in this category provide information about the Outbox.

Table 6-2 BizTalk BAS Outbox Document Library Metrics

Metric	Description
Total Documents Not Sent	Total number of documents that the BizTalk SharePoint Messaging Adapter service failed to process and send to the BizTalk Server.
Total Documents Sent	Total number of documents that the BizTalk SharePoint Messaging Adapter service has successfully processed and asynchronously sent to the BizTalk Server.

BizTalk BAS Sent Items Document Library Metrics

A document library in SharePoint Services that BAS uses for archiving messages and sent documents is referred to as Sent Items. The Sent Items folder serves as the storing mechanism for tracking the sent business documents for future reference and auditing needs.

The metrics in this category provide information about Sent Items.

Table 6-3 BizTalk BAS Sent Items Document Library Metrics

Metric	Description
Total Documents Moved	Total number of documents successfully moved from the Outbox document library to the Sent Items folder of the partner document library.
Total Documents Moved with Rename	Total number of documents successfully moved from the Outbox document library to the partner document library, Sent Items folder, after they have been renamed because of a name collision.
Total Move Failures	Total number of messages submitted by the BizTalk Server that failed to be moved from the Outbox.
Total Move Fallbacks to Orphaned Messages	Total number of move operations that were redirected from the partner document library, Sent Items folder, to the Orphaned Messages document library because of an issue with the partner.
Total Non Office Documents Recreated	Total number of documents successfully recreated as is in the Sent Items folder because of failure(s) to transform them into InfoPath documents.
Total Office Documents Recreated	Total number of InfoPath documents recreated in the Sent Items folder of partner document libraries.
Total Recreated Fallbacks to Orphaned Messages	Total number of messages redirected to the Orphaned Messages document library because of an issue with the partner. The BizTalk Server resubmits these messages until they persist successfully or until the number of retries is exceeded.
Total Sent Items Failures	Total number of confirmation messages submitted by the BizTalk Server that failed to persist into Windows SharePoint Services.

BizTalk BAS TPM Management Web Service Metrics

Trading Partner Management (TPM) tools are used to create and update partner profiles to:

· Manage key information about addresses, contacts, and so forth

· Create groups of partners based on business needs

· Create and manage documents with partners

· Analyze and track the business process with partners.

The metric in this category provides information about the Trading Partner Management Web Service.

Table 6-4 BizTalk BAS TPM Management Web Service Metrics

Metric	Description
Get Parameter Calls	Number of GetParameter calls.

BizTalk BAS TPM Publishing Web Service Metrics

Trading Partner Management (TPM) tools are used to create and update partner profiles to:

· Manage key information about addresses, contacts, and so forth.

· Create groups of partners based on business needs

· Create and manage documents with partners

· Analyze and track the business process with partners.

The metrics in this category provide information about publishing Web Service.

Table 6-5 BizTalk BAS TPM Publishing Web Service Metrics

Metric	Description
Get Parameters Value Calls	Number of GetParameterValue calls.

BizTalk Enterprise SSO Metrics

BizTalk's Enterprise Single Sign-On (SSO) is a standalone service that enables you to map a Windows user account to one or more alternative Windows or non-Windows accounts. These accounts are mapped per application to securely access applications that require credentials other then those originally provided by the end user.The metrics in this category provide information about Single Sign On.

Table 6-6 BizTalk Enterprise SSO Metrics

Metric	Description
Credential Cache Size	Total number of credentials in cache. The credential cache size provides data about user login activity.
Get Configuration Info
Get Configuration Info Per Sec	Configuration infomation accessed per second.
Get Credentials
Get Credentials Per Sec	Credentials accessed per second.
Issue Ticket
Issue Ticket Per Sec	Tickets issued per second.
Redeem Ticket
Redeem Ticket Per Sec	Tickets redeemed per second.
Validate and Redeem Ticket
Validate and Redeem Ticket Per Sec	Tickets validated and redeemed per second.

BizTalk Error Events Metrics

The metric in this category provides information about ERROR events the application raises.

Table 6-7 BizTalk Error Events Metrics

Metric	Description
Windows Event Severity	Severity of the ERROR event.

BizTalk Human Workflow Service Metrics

Human Workflow Services (HWS) is a component of BizTalk Server 2004 that enables the creation of both a priori and ad hoc workflow models. This provides support for both well known constraint-driven models of processing, as well as the ability to compose steps into a workflow on the fly.The metrics in this category provide information about HWS.

Table 6-8 BizTalk Human Workflow Service Metrics

Metric	Description
Activity Flows Retrieved	Number of requests for retrieving activity flow information.
New Action Added	Number of requests for instantiating actions or activity blocks.
New Activity Flows	Number of requests for creating new activity flows.
Steps Retrieved	Number of requests for retrieving step information.
Tasks Retrieved	Number of requests for retrieving task information.

BizTalk Messaging Documents Metrics

The metrics in this category provide information about Messaging Engines that process documents.

Table 6-9 BizTalk Messaging Documents Metrics

Metric	Description
Documents Processed	Processed BizTalk Messaging Documents.
Documents Processed Per Sec	Processed BizTalk Messaging Documents per second.
Documents Received	Received BizTalk Messaging Documents.
Documents Received Per Sec	Received BizTalk Messaging Documents per second.
Documents Suspended	Suspended BizTalk Messaging Documents.
Documents Suspended Per Sec	Suspended BizTalk Messaging Documents per second.
Process ID	Process ID for BizTalk Messaging Documents.

BizTalk Response Metrics

The metrics in this category provide information about BizTalk status.

Table 6-10 BizTalk Response Metrics

Metric	Description
Status	0 or 1 based on the status of the BTSSvc service as Running or Stopped.

BizTalk Tracking Data Decode Service Metrics

The metrics in this category provide information about the Tracking Data Decode Service (TDDS), also known as the BAM Event Bus Service.

Table 6-11 BizTalk Tracking Data Decode Service Metrics

Metric	Description
Batches Being Processed	Currently processing BizTalk TDDS batches.
Batches Committed	Committed BizTalk TDDS batches.
Events Being Processed	Currently processing BizTalk TDDS events.
Events Committed	Committed BizTalk TDDS events.
Records Being Processed	Currently processing BizTalk TDDS records.
Records Committed	Committed BizTalk TDDS records.
Total Batches	BizTalk TDDS total batches.
Total Events	BizTalk TDDS total events.
Total Failed Batches	BizTalk TDDS total failed batches.
Total Failed Events	BizTalk TDDS total failed events.
Total Records	BizTalk TDDS total records.

BizTalk Warning Events Metrics

The metrics in this category provide information about WARNING events the application raises.

Table 6-12 BizTalk Warning Events Metrics

Metric	Description
Description	Description of the WARNING event.
Windows Event Severity	Severity of the event.

Orchestrations Metrics

BizTalk Orchestration services provide a development and execution environment that integrates loosely-coupled, long-running business processes, both within and between businesses. It allows business analysts and developers to visually model their business processes using a Visio-like design environment and then bind that visual representation to its physical implementation.The metrics in this category provide information about the Orchestration Service.

Table 6-13 Orchestrations Metrics

Metric	Description
Allocated Private Memory (MB)	Megabytes of allocated private memory for the host instance.
Allocated Virtual Memory (MB)	Megabytes reserved for virtual memory for the host instance.
Dehydratable Orchestrations	Number of orchestrations instances that can be dehydrated that are currently hosted by the host instance.
Dehydrating Orchestrations	Number of orchestrations that are in the process of dehydrating.
Dehydration Cycle in Progress	Indicates whether there is a dehydration cycle currently in progress.
Dehydration Cycles	Number of completed dehydration cycles.
Dehydration Threshold	Number in milliseconds that determines how aggressively orchestrations are being dehydrated. If the orchestration engine predicts that an instance is dehydratable for an amount of time longer than this threshold, it dehydrates the instance.
Idle Orchestrations	Number of idle orchestration instances currently hosted by the host instance. This refers to orchestrations that are not making progress but are not dehydratable, such as when the orchestration is blocked waiting for a receive, listen, or delay in an atomic transaction.
Message Box Database Connection Failures	Number of attempted database connections that failed since the host instance started.
Orchestrations Completed Per Sec	Average number of orchestrations completed per second.
Orchestrations Created Per Sec	Average number of orchestration instances created per second.
Orchestrations Dehydrated Per Sec	Average number of orchestration instances dehydrated per second.
Orchestrations Discarded Per Sec	Average number of orchestration instances discarded per second from memory. An orchestration can be discarded if the engine fails to persist its state.
Orchestrations Rehydrated Per Sec	Number of orchestration instances rehydrated per second.
Orchestrations Resident in Memory	Number of orchestration instances currently hosted by the host interface.
Orchestrations Scheduled for Dehydration	Number of dehydratable orchestrations for which there is a dehydration request pending.
Orchestrations Suspended Per Sec	Average number of orchestrations suspended per second.
Pending Messages	Number of received messages for which receipt has not yet been acknowledged to the message box.
Pending Work Items	Number of code execution blocks scheduled for execution.
Persistence Points Per Sec	Average number of orchestration instances persisted per second.
Runnable Orchestrations	Number of orchestration instances ready to execute.
Running Orchestrations	Number of orchestration instances currently executing.

Physical Memory and Application Domain Metrics

The metrics in this category provide information about loaded application domains and memory usage.

Table 6-14 Physical Memory and Application Domain Metrics

Metric	Description and User Action
Active Application Domains	Number of loaded orchestration application domains in the process. Much like the process, the application domain is designed as a security boundary that confines errors and faults to a specific domain. The application domain is designed as a virtual process that isolates applications. Often, especially for security reasons, you cannot avoid using multiple application domains. However, doing so can limit performance at startup. You can reduce the impact of multiple application domains by loading assemblies as domain neutral, enforcing efficient cross-AppDomain communication, using NeutralResourcesLanguageAttribute, and using serialization wisely.
Average Batch Factor	Number of persistence points reached since the host instance started, divided by the number of underlying transactions. This metric is beneficial where the Orchestration engine merges multiple atomic transactions into a single transaction. Assuming that a "persistence point" is really a segment boundary, this metric provides some substantial facts about the effect of batching atomic transactions. The greater the number, the greater the effect of "transaction batching" (that is, the less underlying transactions are being created).
Percent Used Physical Memory	Percentage of total used physical memory on the computer. The value of this metric should be about 75%. A consistently high value of 100% may indicate a problem.

Process Metrics

The metrics in this category provide process-related information.

Table 6-15 Process Metrics

Metric	Description and User Action
Page File Bytes	Current amount of virtual memory in bytes that this process has reserved for use in the paging file(s). Paging files store pages of memory used by the process that are not contained in other files. Paging files are shared by all processes, and the lack of space in paging files can prevent other processes from allocating memory. If there is no paging file, this metric reflects the current amount of virtual memory that the process has reserved for use in physical memory.
Page File Bytes Peak	Maximum amount of virtual memory in bytes that this process has reserved for use in the paging file(s). Paging files store pages of memory used by the process that are not contained in other files.
Percent Processor Time	Elapsed time that all process threads used the processor to execute instructions. The average value of this metric should be approximately 70%. An instruction is the basic unit of execution in a computer, a thread is the object that executes instructions, and a process is the object created when a program is run. Code executed to handle some hardware interrupts and trap conditions are included in this count.
Private Bytes	Current size in bytes of memory that this process has allocated that cannot be shared with other processes.
Thread Count	Number of threads currently active in this process. An instruction is the basic unit of execution in a computer, and a thread is the object that executes instructions. Every running process has at least one thread.
Virtual Bytes	Current size in bytes of the virtual address space the process is using. Use of virtual address space does not necessarily imply corresponding use of either disk or main memory pages. Virtual space is finite, and the process can limit its ability to load libraries.
Working Set	Current size in bytes of the Working Set of this process. The Working Set is the set of memory pages touched recently by the threads in the process. If free memory in the computer is above a threshold, pages are left in the Working Set of a process even if they are not in use. When free memory falls below a threshold, pages are trimmed from Working Sets. If they are needed, they are soft-faulted back into the Working Set before leaving main memory. This metric measures the number of memory pages that each process uses. If the system has sufficient memory, it can maintain enough space in the working set so that IIS 6.0 rarely must perform disk operations. One indicator of memory sufficiency is how much the size of the process working set fluctuates in response to general memory availability on the server. Significant fluctuation can indicate a lack of available memory.

Transaction Metrics

The metrics in this category provide information about database transactions.

Table 6-16 Transaction Metrics

Metric	Description
Database Transactions Per Sec	Average number of database transactions performed per second.
Transactional Scopes Aborted	Number of aborted long-running or atomic scopes since the host instance started.
Transactional Scopes Committed Per Sec	Average number of transactions committed per second.
Transactional Scopes Compensated Per Sec	Average number of long-running or atomic scopes per second that have successfully completed compensation scopes.

JBoss Application Server Metrics

2008-09-22T08:35:00.000-07:00

JBoss Application Server Metrics

JBoss Application Server is the market-leading, open source Java 2 Enterprise Edition (J2EE) application server, delivering a high-performance and enterprise-class platform for e-business applications. JBoss provides enterprise-class security, transaction support, resource management, load balancing, and clustering.

This chapter provides descriptions for all JBoss Application Server metric categories, and tables list and describe associated metrics for each category.

JBoss Clustering Service Metrics

This category provides metrics about High Availability JNDI (HAJNDI) service of JBoss.

Table 5-1 JBoss Clustering Service Metics

Metric	Description
Partition Name	Shows the name of the partition under which JBoss Application Server is running.
Service - Bind Address	Shows the IP address to which the High Availability JNDI (HAJNDI) Service is bound.
Service - Port	Shows the port used by the HAJNDI service.
Service - Rmi Port	Shows the RMI port of the HAJNDI service.
Service - State	Shows the state of the HAJNDI service. Number "3" is for "OK" state.
Service - State (Text)	Shows the state of the HAJNDI service.

JBoss Connection Pools Metrics

This category provides Managed Connection Pool details for JBoss Application Server.

Table 5-2 JBoss Connection Pools Metrics

Metric	Description
Criteria	Shows the criteria for managed connection pool for JBoss Application Server.
Maximum Size	Shows the maximum size for managed connection pool for JBoss Application Server.
Minimum Size	Shows the maximum size for managed connection pool for JBoss Application Server.

JBoss DataSource Bind Metrics

This category provides DataSourceBinding service details for JBoss Application Server.

Table 5-3 JBoss DataSource Bind Metrics

Metic	Description
JNDI Name	shows the JNDI Name for DataSourceBinding service for JBoss Application Server.

JBoss Ejb Modules Metrics

This category shows the information for the EJB modules that are loaded inside the JBoss Application Server.

Default Collection Interval — Every 15 minutes

Table 5-4 JBoss Ejb Modules Metrics

Metric	Description
Name	Shows the name of the EJB module.
Stastistic Provider	This metric shows that the "Statistic Provider" and "State Manageable" attributes are provided to inform a client that the EJB module that is being looked at does or does not support state management, or does or does not provide statistics as defined by the JSR-77 specification.

JBoss Entity Ejb Metrics

This metric category shows information for all the entity EJBs loaded inside the JBoss Application Server.

Default Collection Interval — Every 15 minutes

Table 5-5 JBoss Entity Ejb Metrics

Metric	Description
Entity EJB - Current Instances Pooled Count	Shows the number of instance kept in the pool currently.
Entity EJB - Current Ready Instances Count	Shows the number of instance of this EJB are in the ready state.
Entity EJB - Instances Created Count	Shows the count of the instances created for this EJB by the EJB container.
Entity EJB - Instances Removed Count	Shows the number of instance of this EJB that are removed from the EJB container.
Entity EJB - Maximum Instances in the Pool	Shows the maximum number of instance of this EJB that can be put in the pool.
Entity EJB - Maximum Ready Instances Count	shows the maximum number of instance of this EJB that can be in the passive state.
Entity EJB - Minimum Instances in the Pool	Shows the minimum number of instance of this EJB that should be there in the pool.
Entity EJB - Minimum Ready Instances Count	Shows the minimum number of instance of this EJB that should be in the ready state.
Entity EJB - Name	Shows the name of the EJB.
Entity EJB - Parent	Shows the parent or the JAR file to which this EJB belongs.
Statistic Provider	Shows performance statistics support for this managed object (whether true or false).

JBoss JCA Metrics

This metric category gives information for the Java Connector (JCA) resources of the JBoss Application Server.

Default Collection Interval — Every 15 minutes

Table 5-6 JBoss JCA Metrics

Metric	Description
JCA - Count Use Time	Shows the current use time (in ms) for JCA Resource.
JCA - Count Use Time (Sec)	Shows the current use time for JCA Resource (in seconds).
JCA - Count Wait Time	Shows the current wait time (in ms) for JCA Resource.
JCA - Current Free Pool Size	Shows the number of instances of this resource in the pool that are not being used currently.
JCA - Current Pool Size	Shows number of instances in the pool currently.
JCA - Current Waiting Thread Count	Shows the number of threads waiting to acquire JCA connections.
JCA - High Pool Size	Shows the High Water mark for JCA Connection pool.
JCA - Instances Close Count	Shows the number of instances closed.
JCA - Instances Created Count	Shows the number of instances created.
JCA - Low Pool Size	Shows the Low Water mark for JCA Connection pool.
JCA - Lower Bound Free Pool Size	Shows the minimum number of instances that can be free inside the pool.
JCA - Lower Bound Pool Size	Shows the lower bound for lower connection pool.
JCA - Max Wait Time	Shows the minimum wait time (in ms) for JCA Resource.
JCA - Maximum Pool Size	Shows the maximum number of instances of this resource that can be there in the pool.
JCA - Maximum Use Time	Shows the maximum usage time for JCA Resource.
JCA - Maximum Waiting Thread Count	Shows the high water mark for waiting thread count for JCA connections.
JCA - Min Wait Time	Shows the minimum wait time (in ms) for JCA Resource.
JCA - Minimum Pool Size	Shows the minimum free pool size.
JCA - Minimum Used Time	Shows the minimum usage time for JCA Resource.
JCA - Minimum Waiting Thread Count	Shows the low water mark for waiting thread count for JCA connections.
JCA - Total Used Time	Shows the total usage time for JCA Resource.
JCA - Total Wait Time	Shows the total wait time for JCA Resource (in ms).
JCA - Upper Bound Free Pool Size	Shows the maximum number of instances that can be free inside the pool.
JCA - Upper Bound Pool Size	Shows the upper bound for JCA Connection Pool.
Name	Shows the name of the JCA resource.
Parent	Shows the name of the resource adaptor to which the JCA resource belongs.
Statistics Provider	Shows performance statistics support for this managed object (whether true or false).

JBoss JVM Metrics

This metric category provides information about the Java Virtual Machine (JVM) on which the JBoss Application Server is running. The upload frequency of this metric is after every sample and the Default Warning Threshold and Default Critical Threshold are 25 and 10 respectively.

Default Collection Interval — Every 30 minutes

Table 5-7 JBoss JVM Metrics

Metric	Description
JVM - Free Heap (%)	Shows the percentage of heap memory that is free and is not used by the JVM.
JVM - Heap Size (MB)	Shows the heap memory (in MB) used by the JVM that is used by JBoss Application Server.
JVM Name	Shows the name of the JVM on which JBoss Application Server is running.
JVM Version	Shows the version of the JVM that is used by the JBoss Application Server.
Vendor	Shows the name of the vendor or provider of the JVM.

JBoss Mail Service Metrics

This metric category provides information about the JBoss Mail Service.

Table 5-8 JBoss Mail Service Metrics

Metric	Description
Service - Default Sender	Shows the default sender of the any message that goes via JBoss mail service.
Service - JNDI Name	Shows the name by which the JBoss mail service is registered with the JNDI server.
Service - POP3 Server Host	Shows the host of the POP3 server for the JBoss mail service.
Service - SMTP Server Host	Shows the host of the SMTP server for the JBoss mail service.
Service - State	Shows the current state of the JBoss mail service. If the number is 3, then it is up.
Service - State (text)	Shows the state of the JBoss mail service.
Service - Store Protocol	Shows the protocol used by the JBoss mail service for receiving the messages.
Service - Transport Protocol	Shows the transport protocol used by the JBoss mail service for sending messages.

JBoss Message Driven Ejb Metrics

This metric category shows information for all the message driven EJBs loaded inside the JBoss Application Server.

Default Collection Interval — Every 15 minutes

Table 5-9 JBoss Message Driven Ejb Metrics

Metric	Description
MDB - Instances Created Count	Shows the count of the instances created for this EJB by the EJB container.
MDB - Instances Removed Count	Shows the number of instance of this EJB that are removed from the EJB container.
MDB - Messages Count	Shows the number of messages received by this EJB.
MDB - Name	Shows name of the EJB.
MDB - Parent	Shows the parent or the jar file to which this EJB belongs.
Statistic Provider	Shows performance statistics support for this managed object (whether true or false).

JBoss Naming Service Metrics

This metric category provides information about the naming service of JBoss Application Server.

Default Collection Interval — Every 15 minutes

Table 5-10 JBoss Naming Service Metrics

Metric	Description
Listen Port	Shows the port on which the naming service of JBoss Application Server is running.
RMI Port	Shows the RMI port of the naming service of JBoss Application Server.
Service Name	Shows the name of the service monitored, that is, in this case it is NamingService only.
Service State	Shows the current state of the naming service of JBoss Application Server.

JBoss Protocols Ports Metrics

This category provides connection details for JBoss Application Server.

Table 5-11 JBoss Protocols Ports Metrics

Metric	Description
JBoss - Connection Linger Value	Represents linger value on the incoming connection for JBoss Application Server.
JBoss - Connection Timeout	Shows the timeout value on the incoming connection for JBoss Application Server.
JBoss - KeyStore File	Shows the KeyStore file for JBoss Application Server.
KeyStore Type	Shows the configured keystore type for JBoss Application Server.
JBoss - Protocol	Shows the coyote protocol handler in use for JBoss Application Server.
JBoss - Redirect Port	Shows the redirect port for non-SSL to SSL redirects for JBoss Application Server.
JBoss - Redirect Port Protocol	Shows the protocol name for this Connector (http, https) for JBoss Application Server.

JBoss Server Configuration Metrics

This category provides information about the configuration of JBoss Application Server.

Default Collection Interval — Every 30 minutes

Table 5-12 JBoss Server Configuration Metrics

Metric	Description
JBoss - Base Directory	Shows the base directory (directory 'server') for the JBoss Application Server.
JBoss - Configuration Name	Shows the name of the configuration that is used by JBoss Application Server. By default, JBoss Application Server comes with some configuration, for example, 'all', 'minimal', and so on.
JBoss - Deployment Filename	Shows the name of the main deployment file of JBoss Application Server. By default, it is jboss-service.xml. The configuration directory contains the "jboss-service.xml" bootstrap descriptor file for a given server configuration. This defines the core service-configurations that are fixed for the lifetime of the server.
JBoss - Home Directory	Shows the installation directory of the JBoss Application Server.
JBoss - Server Home Directory	Shows the configuration directory of JBoss Application Server that is running. If JBoss Application Server is running under 'minimal' configuration, then this metric shows the path to that configuration.

JBoss Server Details Metrics

This category provides server details for JBoss Application Server.

Default Collection Interval — Every 15 minutes

Table 5-13 JBoss Server Details Metrics

Metric	Description
Active Thread Count	This metric shows the active thread count for JBoss Application Server.
Active Thread Group Count	This metric shows the active thread group count for JBoss Application Server.
Available No. of Processors	Shows the available number of processors for JBoss Application Server.
Free Heap Size	Shows the free heap memory for JBoss Application Server.
Free Heap Size %	Shows the percentage of available heap memory out of total configured heap memory for JBoss Application Server.
Heap Size	Show the available heap memory (in MB) for JBoss Application Server.
Heap Size (MB)	Shows the available heap memory (in MB) for JBoss Application Server.
Host Name	Provides the host name on which JBoss Application Server is installed.
Java Vendor Name	Provides Java Vendor Name for JBoss Application Server.
Java Version	Shows the version of JDK/JRE for JBoss Application Server.
Java VM Name	Show the name of the Java Virtual Machine (JVM) used for JBoss Application Server.
Java VM Vendor Name	Show the Java VM vendor name with which this JBoss Application Server is running.
Java VM Version	Show the Java VM version with which JBoss Application Server is running.
Maximum Memory	Shows the maximum available memory on which JBoss Application Server is running.
OS Architecture	Provides operating system architecture details on which JBoss Application Server is running.
OS Name	Provides operating system name on which JBoss Application Server is running.
OS Version	Show the operating system version on which JBoss Application Server is running.
Total Heap Size	Shows the total heap memory for JBoss Application Server.
Total Heap Size(MB)	Shows the total heap memory (in MB) for JBoss Application Server.

JBoss Server Metrics

This category provides information about JBoss Application Server.

Default Collection Interval — Every 30 minutes

Table 5-14 JBoss Server Metrics

Metric	Description
Host Address	Shows the IP address of the host on which the JBoss Application Serveris running.
Host Name	Shows the host name on which the JBoss Application Server is running.
Host Operating System	Shows the operating system of the host on which the JBoss Application Server is running.
JBoss - Build Date	Shows the build date for the JBoss Application Server.
JBoss - Build ID	Shows the build ID of the JBoss Application Server.
JBoss - Listen Port	Shows the naming service port or Java Naming Provider (JNP) port for the JBoss Application Server.
JBoss - Start Time	Shows date on which the JBoss Application Server was started.
JBoss - Version	Shows the version (build version) of the JBoss Application Server.
JBoss - Version Name	Shows the version name of the JBoss Application Server.

JBoss Servlets Raw Metrics

This metric category provides information for the servlets loaded inside the JBoss Application Server.

Default Collection Interval — Every 15 minutes

Table 5-15 JBoss Servlets Raw Metrics

Metric	Description
Parent	Shows the parent or the application to which this servlet belongs.
Servlet - Active Requests / Sec	Shows rate of requests (per sec) on the servlet.
Servlet - Active Requests since last Upload	Shows the current active requests for the servlet.
Servlet - Active Requests, Response Time (Sec)	Shows the response time(per sec) for the servlet for handling those requests.
Servlet - Maximum Response Time	Shows the maximum processing time of a request (depicted by a long value).
Servlet - Minimum Response Time	Shows the minimum processing time of a request (depicted by a long value).
Servlet - Response Time Unit	Shows the unit of time for the requests.
Servlet - Total Requests	Shows the number of requests processed by this servlet.
Servlet - Total Response Time	Shows the average response time for the request.
Servlet Name	Shows the name of the JBoss servlet.
Statistic Description	Shows the description of the statistic instance.
Statistic Name	Shows the name of the statistic instance.
Statistic Provider	Shows the performance statistics support for this managed object (whether true or false).

JBoss Stateful Session EJB Metrics

This category shows information about the stateful EJBs loaded inside the JBoss Application Server.

Default Collection Interval — Every 15 minutes

Table 5-16 JBoss Stateful Session EJB Metrics

Metric	Description
Stateful Ejb - Current Method Ready Count	Shows the count of the instances that are in the ready state in the EJB container.
Stateful Ejb - Current Passive Instances Count	Shows the number of instances (of this EJB) that are in the passive state.
Stateful Ejb - Instances Created Count	Shows the count of the instances created for this EJB by the EJB container.
Stateful Ejb - Instances Removed Count	Shows the number of instance of this EJB that are removed from the EJB container.
Stateful Ejb - Maximum Method Ready Count	Shows the maximum number of instances that can be in the ready state in the EJB container.
Stateful Ejb - Maximum Passive Instances Count	Shows the maximum number of instances that can be in the passive state.
Stateful Ejb - Minimum Method Ready Count	Shows the minimum number of instances that can be in the ready state in the EJB container.
Stateful Ejb - Minimum Passive Instances Count	Shows the minimum number of instances that can be in the ready state in the EJB container.
Stateful Ejb - Name	Shows the name of the EJB.
Stateful Ejb - Parent	Shows the parent or the JAR file to which this EJB belongs.
Statistic Provider	Shows performance statistics support for this managed object (whether true or false).

JBoss Stateless Session EJB Metrics

This category shows information about the stateless EJBs loaded inside the jboss server.

Default Collection Interval — Every 15 minutes

Table 5-17 JBoss Stateless Session EJB Metrics

Metric	Description
Stateless Ejb - Current Method Ready Count	Shows the count of the instances which are in the ready state in the EJB container.
Stateless Ejb - Instances Created Count	Shows the count of the instances created for this EJB by the EJB container.
Stateless Ejb - Instances Removed Count	Shows the count of the instances removed for this EJB by the EJB container.
Stateless Ejb - Maxinum Method Ready Count	Shows the maximum number of instances that can be in the ready state in the EJB container.
Stateless Ejb - Minimum Method Ready Count	Shows the minimum number of instances that can be in the ready state in the EJB container.
Stateless Ejb - Name	Shows the name of the EJB.
Stateless Ejb - Parent	Shows the parent or the JAR file to which this EJB belongs.
Statistic Provider	Shows performance statistics support for this managed object (whether true or false).

JBoss Top EJBs Metrics

This category shows information for the top performing EJBs of JBoss

Default Collection Interval — Every 15 minutes

Table 5-18 JBoss Top EJBs Metrics

Metric	Description
JBoss - Ejb Create Count	Shows the number of instances created for this EJB by the container.
JBoss - Ejb Remove Count	Shows the number of instances removed for this EJB by the container.
JBoss - Ejb Type	Shows the name of the EJB.

JBoss Top Servlets Metrics

This category gives information for the top performing servlets of the JBoss Application Server.

Table 5-19 JBoss Top Servlets Metrics

Metric	Description
JBoss - Servlet WAR Name	Shows the parent or application to which the servlet belongs.
JBoss - Web Component Type	Shows the name of the servlet.
Servlet - Active Requests / Sec	Shows rate of request/sec to this servlet.
Servlet - Active Requests since last Upload	Shows number of active requests for this servlet.
Servlet - Active Requests, Response Time (Sec)	Shows the response time in sec for these active requests by the servlet.

JBoss Transactions Metrics

This category shows the information for the transaction manager service of the JBoss Application Server.

Default Collection Interval — Every 15 minutes

Table 5-20 JBoss Transactions Metrics

Metric	Description
Committed last interval	Shows the number of transaction committed since last interval.
JBoss - Active Transactions Count	Shows the number of current active transactions.
JBoss - Transactions / Sec	Shows the rate of active transactions per second.
JBoss - Transactions Committed / Sec	Shows the rate of transactions committed per second.
JBoss - Transactions Committed Count	Shows the number of transaction that have been committed.
JBoss - Transactions Rolled Back / Sec	Shows the rate of transactions rolled back per second.
JBoss - Transactions RolledBack Count	Shows the number of transaction that have been rolled back.
JBoss - Transactions Timeout (Secs)	Shows the the time interval in secs after which the transactions will timeout.
Rolledback last interval	Shows the number of transactions rolled back since last interval.
Trans last interval	Shows the transaction that was made since last interval.

JBoss Web Applications Metrics

This category shows performance information about the Web application loaded inside the JBoss Application Server.

Default Collection Interval — Every 15 minutes

Table 5-21 JBoss Web Applications Metrics

Metric	Description
Web Apps - Active requests since last agent upload	Shows the current active requests for the application.
Web Apps - Average maximum response time	Shows the average maximum response time for the active requests.
Web Apps - Average minimum response time	Shows the average minimum response time for the active requests.
Web Apps - Average Response Time	Shows the average response given by these applications for the request.
Web Apps - Requests rate per second	Shows the current rate of requests (per sec) to this application.
Web Apps - Total Requests	Shows the total requests for the application.
Web Apps - Total Response Time	Shows the total time take for servicing those requests.
Web Apps - Total Response time for Active Requests	Shows the total response time for all the active requests.

JBoss WebService Service Metrics

This category provides information for the Web services running on the JBoss Application Server.

Table 5-22 JBoss WebService Service Metrics

Metric	Description
Service - Bind Address	Shows the IP address to which the Web service is bound.
Service - Host	Shows host name on which the Web service is running.
Service - Port	Shows the port on which the Web service is listening.
Service - State	Shows the state of the Web service as a number. Number "3" depicts that the service is up.
Service - State (text)	Shows the state of the Web service.

Resource Usage Metrics

This category provides metrics related to JBoss Application Server resource usage.

Table 5-23 Resource Usage

Metric	Description
Free Memory (%)	Shows the percentage of heap memory that is free and is not used by the Java Virtual Machine (JVM).
Maximum Memory Size (MB)	Provides total heap memory configured for JBoss Application Server.
Memory Usage (MB)	Shows the memory used by JBoss Application Server in MBs.

Response Metrics

This category provides response metrics for JBoss Application Server.

Table 5-24 Response Metrics

Metric	Description
UpDown Status	Shows whether the JBoss Application Server is up or down. If the value is 1, then JBoss is up. If the value is 0, then it is down. The upload frequency is after every sample. If the JBoss Application Server instance is down, then restart it from the scripts that come with JBoss Application Servers.

Metric

Description

UpDown Status

Shows whether the JBoss Application Server is up or down. If the value is 1, then JBoss is up. If the value is 0, then it is down. The upload frequency is after every sample.

If the JBoss Application Server instance is down, then restart it from the scripts that come with JBoss Application Servers.

IBM WebSphere MQ Metrics

2008-09-22T08:34:00.001-07:00

IBM WebSphere MQ Metrics

WebSphere MQ (formerly MQSeries) is IBM's Message Oriented Middleware offering that allows independent and potentially non-concurrent applications on a distributed system to communicate with each other.

This chapter provides descriptions for all IBM WebSphere MQ metric categories, and tables list and describe associated metrics for each category.

Channel Current Status Metrics

This category provides metrics about the current status of the channel.

Default Collection Interval — Every 3 minutes

Table 4-1 Channel Current Status Metrics

Metric	Description
Bytes Received	Shows the number of bytes received.
Bytes Sent	Shows the number of bytes sent
Delta Bytes Received	Shows the number of bytes received since last collection
Delta Bytes Sent	Shows the number of bytes sent since last collection
Delta Messages Sent/Received	Shows the number of messages processed since last collection
Messages Sent/Received	Shows the number of messages processed
Status	Shows the current status.

Channel Saved Status Metrics

This category provides metrics about Channel Saved Status.

Default Collection Interval — Every 2 minutes

Table 4-2 Channel Saved Status Metrics

Metric	Description
Last Seq Number	Shows the sequence number of the last message sent
Status	Shows the status of the channel
Type	Shows the type of the channel
Xmit Queue	Shows the transmission queue used by sender channels

Channels Metrics

This category provides metrics related to the channels.

Default Collection Interval — Every 10 minutes

Table 4-3 Channels Metrics

Metric	Description
Alteration Date	Shows the date on which the definition was last altered
Cluster Name	Shows the name of the IBM WebSphere MQ Cluster to which this channel belongs
Cluster Name list	Shows the cluster name list
Connection Name	Shows the name of the channel connection
Max Msg Length	Shows the maximum length of the message that can be processed by the channel
Type	Shows the type of the channel
Xmit QName	Shows the name of the transmission queue used by the sender channels

DynamicQs Metrics

This category provides metrics related to Dynamic Queues.

Table 4-4 DynamicQs Metrics

Metric	Description
Definition Type	Shows the type of queue definition
Type	Shows the type of the queue
Usage	Shows information about the usage (normal/transmission)

Local Queues Metrics

This category shows metrics related to local queues.

Default Collection Interval — Every 10 minutes

Table 4-5 Local Queues Metrics

Metric	Description
Cluster Name List	Shows the cluster Name List
Definition Type	Shows the type of the queue definition
Depth	Shows the number of messages on the queue
Max Depth	Shows the maximum number of messages on the queue
Max Message Length	Shows the maximum length of the message can be processed
Open Input Count	Shows the number of open input handles, that is the total handles open for input on this queue. This gives you an idean on the number of applications that are currently connected to the queue to put messages on the queue
Open Output Count	Shows the number of open output handles, that is the total handles open for output on this Queue. This gives you an idea on the number of applications that are currently connected to the queue to get messages from the queue
Percent Usage	Shows the space used (in percentage)
Type	Shows the type of the queue
Usage	Shows details about the usage, which can be "Normal" or "Trasmission")
Xmit QName	Shows the name of the transmission queue

QM Cluster Metrics

This category provides metrics related to IBM Websphere MQ Queue Manager Cluster, mainly the details about the channel used, the queue manager within this cluster, and the type of queue manager that is within this cluster.

Default Collection Interval — Every 10 minutes

Table 4-6 QM Cluster Metrics

Metric	Description
Queue Manager Name	Shows the name of the IBM Websphere MQ Queue Manager that is within this IBM Websphere MQ Queue Manager Cluster
Queue Manager Type	Shows the type of the IBM Websphere MQ Queue Manager (full/partial repository)

QM General Metrics

This caterogy provides metrics related to QM General.

Default Collection Interval — Every 2 minutes

Table 4-7 QM General Metrics

Metric	Description
Command QName	Shows the name of the local queue that is used for accepting commands
Dead Letter QName	Shows the name of the local queue that is to be used for undelivered messages
Default Xmit QName	Shows the name of the default transmission queue that is used for the transmitting messages to remote queue managers, if there is no other indication of which transmission queue to use
Max Handles	Shows the maximum number of handles that any one job can have open at a time
Max Message Length	Shows the maximum length of message that can be processed
Platform	Shows the platform on which the queue manager is running
Repository Name List	Shows a list of clusters for which this queue manager provides a repository service

QMLoad Metrics

This category provides metrics about the load on IBM Websphere MQ Queue Manager.

Table 4-8 QMLoad Metrics

Metric	Description
Bytes Received	Shows the bytes received since last collection
Bytes Sent	Shows the bytes sent since last collection
Messages Sent/Received	Shows the messages sent or received since last collection

Queue Status Input Handle Metrics

This category provides metrics related to Queue Status Input Handle.

Default Collection Interval — Every 10 minutes

Table 4-9 Queue Status Input Handle Metrics

Metric	Description
Appl Tag	Shows the name of the application that is using this queue
Appl Type	Shows the type of the application that is using this queue
Channel Name	Shows you the channel used for the message input
Connection Name	Shows the name of the connection used by the channel
Open Options	Shows the open options for the queue
User Identifier	Shows you the user ID of the application

Queue Status Output Handle Metrics

This category provides metrics related to Queue Status Output Handle.

Default Collection Interval — Every 10 minutes

Table 4-10 Queue Status Output Handle Metrics

Metric	Description
Appl Tag	Shows the name of the application that is using this queue
Appl Type	Shows the type of the application that is using this queue
Channel Name	Shows the name of the channel used for the message output
Connection Name	Shows the name of the connection name used by the channel
Open Options	Shows the open options for this queue
User Identifier	Shows the user ID of the application

Queues Metrics

This category provides metrics related to Message Queues.

Default Collection Interval — Every 10 minutes

Table 4-11 Queues Metrics

Metric	Description
Cluster Name List	Shows the list of clusters with which the queue is shared
Depth	Shows the current depth (number of messages) of the queue. For this metric you can set different warning and critical threshold values for each "QName" object. If warning or critical threshold values are currently set for any "QName" object, those thresholds can be viewed on the Metric Detail page for this metric.
Max Depth	Shows the maximum depth (number of messages) of the queue
Max Message Length	Shows the maximum message length allowed on a queue
Open Input Count	Shows the number of open input handles, that is the total handles open for input on this Queue. This gives you an idea on the number of applications that are currently connected to the queue to put messages on the queue
Open Output Count	Shows the number of open output handles, that is the total handles open for output on this Queue. This gives you an idea on the number of applications that are currently connected to the queue to get messages from the queue
Remote QManager	Shows the name of the remote queue manager (only for remote queues)
Remote QName	Shows the remote queues with which this queue interacts
Type	Shows the queue type. It can be one of the following: Local, Remote, Model, Alias Queue, or Read-only
Use	Shows how the queue is being used. The usage types can be "Normal" or "Tramission"
Xmit QName	Shows the transmission queue associated with this queue (only for remote queues)

Response Metrics

This category provides status metrics.

Table 4-12 Response Metrics

Metric	Description
Response	Shows the current status of the Queue Manager. The evaluation and collection frequency is 1 minute. The upload frequency is after every 5 samples.

Sender Channel Qs Metrics

This category provides metrics related to the Sender Channel Queues.

Default Collection Interval — Every 10 minutes

Table 4-13 Sender Channel Qs Metrics

Metric	Description
Xmit QName	Shows the name of the transmission queue