# PCC Service Schema Statistics

The PCC Service schema provides operational statistics that can be used for monitoring and troubleshooting the following products from StarOS Release 12.1 onward: IPCF.
This schema provides the following types of statistics:

- Counter: A counter records incremental data cumulatively and rolls over when the counter limit is reached. All counter statistics are cumulative and reset only by one of the following methods: roll-over when limit is reached, after a system restart, or after a clear command is performed. The limit depends upon the data type.
- Gauge: A gauge statistic indicates a single value; a snapshot representation of a single point in time within a defined time frame. The gauge changes to a new value with each snapshot though a value may repeat from one period to the next. The limit depends upon the data type.
- Information: This type of statistic provides information, often intended to differentiate sets of statistics; for example, a VPN name or IP address. The type of information provided depends upon the data type.

The data type defines the format of the data for the value provided by the statistic. The following data types are used in statistics for this schema:

- Int32/Int64: An integer, either 32-bit or 64-bit: For statistics with the Int32 data type, the roll-over to zero limit is 4,294,967,295. For statistics with the Int64 data type, the roll-over to zero limit is 18,446,744,073,709,551,615.
- Float: A numeric value that can be represented fractionally; for example, 1.345.
- String: A series of ASCII alphanumeric characters in a single grouping, usually pre-configured.

IMPORTANT:

Unless otherwise indicated, all statistics are counters and all statistics are standards-based.

Key Variables: Every schema has some variables which are typically referred to as 'key variables'. These key variables provide index markers to identify which object the statistics apply to. For example, in the card schema, the card number (variable %card%) uniquely identifies a card. For an HA service, the keys would be "%vpnname%" plus "%servname%", as the combination uniquely identifies an HA service. So, in a given measurement interval, one row of statistics will be generated per unique key. The schema keys are identified in the Description section of the table.
Table 1. Bulk Statistic Variables in the PCC Service Schema

Variables | Description | Data Type
--- | --- | ---
vpnname | The name of the context in which PCC service is configured. This is a key variable. | String
vpnid | The identity number of the context in which PCC service is configured. This is a key variable. | String
servname | The name of the PCC service for which statistics are collected or displayed. This is a key variable. | String
servid | The identity number of the PCC service for which statistics are collected or displayed. This is a key variable. | String
total-gx-processed | Indicates the total number of Gx request processed by PCC. Trigger: When Gx request is processed by PCC. Availability: Availability: Across all PCC Services. | Unsigned Int32
total-gy-processed | Indicates the total number of Gy request processed by PCC. Trigger: When Gy request is processed by PCC. Availability: Availability: Across all PCC Services. | Unsigned Int32
total-spr-processed | Indicates the total number of SSC request processed by PCC. Trigger: When SPR responsed is processed by PCC. Availability: Availability: Across all PCC Services. | Unsigned Int32
total-unknown-req | Indicates the total number of unknown request received at PCC. Trigger: When sent to PCC is unknown. Availability: Availability: Across all PCC Services. | Unsigned Int32
total-pur-updates | Indicates the total number of profile update request sent by PCC. Trigger: When IPCF wants to update quota on SSC. Availability: Availability: Across all PCC Services. | Unsigned Int32
total-snr-requests | Indicates the total number of subscriber notification request processed by PCC. Trigger: When IPCF wants to ask for Subscriber information from SSC. Availability: Across all PCC Services. | Unsigned Int32
total-pnr-requests | Indicates the total number of profile notification request processed by PCC. Trigger: When subscriber profile is updated at SSC. Availability: Across all PCC Services. | Unsigned Int32
total-profile-match-hits | Indicates the total number profiles matched. Trigger: When profile requested by interfaces is matched. Availability: Across all PCC Services. | Unsigned Int32
total-profile-match-miss | Indicates the total number of profiles that did not match. Trigger: When profile requested by interfaces does not match. Availability: Across all PCC Services. | Unsigned Int32
total-quota-reports | Indicates the total number of quote reports generated by PCC. Trigger: When IPCF processes quota request on Gy interface. Availability: Across all PCC Services. | Unsigned Int32
total-unknown-rt-req | Indicates the total number of unknown rating group requested. Trigger: When an unknown rating group is reported by Gy. Availability: Across all PCC Services. | Unsigned Int32
IMPORTANT: For information on statistics that are common to all schema see the Statistics and Counters Overview chapter.