Product Description

Statistics and Performance Data

The following sections describe the statistics and performance data that WebLogic Network Gatekeeper collects:

• Overview
• Usage statistics
• Performance data

 

---

Overview

Both performance data and usage statistics can be retrieved from the WebLogic Network Gatekeeper. The usage statistics makes it possible to retrieve statistics on the usage of service capabilities through the WebLogic Network Gatekeeper. For a specified time period, usage statistics be retrieved based on the following:

• service provider
• application
• SLEE
• all SLEEs

The performance data keeps track on the system load when it come to the SLEE and the JVM.

 

---

Usage statistics

The statistics functions measure the usage of the service capabilities through the WebLogic Network Gatekeeper. A number of statistics types have been defined. One or more types are defined for each service capability, see Table 11-1.

Table 11-1 Statistics types per service capability

Service capability	Statistics types
Call	Call control: Number of network initiated calls Number of application initiated calls Multiparty call control: Number of network initiated call legs Number of network initiated additional call legs Number of application initiated call legs Number of application initiated additional call legs
Charging	Number of immediate charging transactions Number of reservation/payments in parts charging transactions
Messaging	SMS: Number of sent messages Number of received messages MMS: Number of sent messages Number of received messages
Subscriber Profile	Number of set property requests Number of get property requests
User Interaction	Call user interaction: Number of played announcements Number of played voice prompts Number of recorded messages Generic user interaction: Number of sent messages with response request Number of sent messages without response request Number of received messages
User Location	Number of location requests
User Status	Number of status requests

Customized statistics reports can be generated for the system and for individual service providers and/or applications. For statistics generation options, see Table 11-2 on page 4.

Table 11-2 Statistics generation options (one SLEE, all SLEEs, service provider or application)

Statistics Area	Parameter
System statistics	The whole system or for an individual SLEE (The SLEE concept is explained in Software Architecture Overview.) All statistics types or for a single statistics type A specified time period or not
Service provider and/or application statistics	All the service provider's applications or a single application All statistics types or for a single statistics type A specified time period or not

A pre-defined report type is the weekly report. It shows the total service capability usage hour by hour during a specified week. The weekly report also shows total usage for each day and the average transaction rate (transactions/second (tps)) during the busy hour of each day. A busy hour is defined as the 60 minutes during which the largest number of transactions are handled. That is, any 60 minute interval can be the identified as the busy hour. For example: 10:05:00-11:05:00.

The statistics data is stored in the database and can be retrieved and printed to file or viewed using the management tool.

 

---

Performance data

The load is measured separately for each server in the WebLogic Network Gatekeeper system. By monitoring the load on the individual servers and balancing the load among the servers accordingly, system performance is kept at its maximum for every system configuration.

Detailed resource utilization data can be viewed for the whole SLEE, the JVM and the defined load share contexts. (Load share contexts are described in Software Architecture Overview.) The resource utilization data includes:

• current load
• heap used
• heap total
• heap initial
• heap last GC
• And for each load share context:
• task pool size (threads)
• task pool used (threads)
• task queue size (tasks)
• task queue used (tasks)
• orb pool size (threads)
• orb pool used (threads)