> ENAPP Schema Statistics
> The Event Notification Application (ENAPP) schema provides the following type of statistics:

> • | Counter: A counter records incremental data cumulatively and rolls over when the counter limit is reached. The limit depends upon the counter data type.

> • | Gauge: A gauge statistics indicates a single value representative of a single instance. This type is often used to track particular events in time.

> • | Fixed Value String: A string statistics indicates the name of a service instance or a node.

> Important: The format string syntax is described by Schema Format String Syntax in the Bulk Statistics Overview chapter.
> Important: Unless otherwise indicated all statistics are of proprietary type based on 3GPP standard.
> Important: Unless otherwise indicated, all statistics are counters. 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. All statistics are cumulative and reset only by one of the following methods: roll-over (as described above), after a system restart, or after a clear command is performed. All statistics are considered standards-based unless otherwise noted.
> The following variables are supported:
> ENAPP Schema Statistics

> Statistic | Description | Data Type
> in_events | Indicates total number of incoming events. Trigger: When an event from IPCF or SSC is received at event notification manager. Availability: Available across event notification application. | Gauge/Int64
> out_events | Indicates total number of out going events. Trigger: When an event is sent out by event notification manager. Availability: Available across event notification application. | Gauge/ Int64
> in_sms_events | Indicates total number of incoming SMS events. Trigger: When an event from IPCF or SSC is received at event notification manager with SMS as notification method. Availability: Available across event notification application. | Gauge/ Int64
> out_sms_events | Indicates total number of out going SMS events. Trigger: When SMS is sent for an event. Availability: Available across event notification application. | Gauge/ Int64
> in_email_events | Indicates total number of incoming e-mail events. Trigger: When an event from IPCF or SSC is received at event notification manager with an e-mail as notification method. Availability: Available across event notification application. | Gauge/ Int64
> out_email_events | Indicates total number of out going e-mail events. Trigger: When an e-mail is sent out for an event. Availability: Available across event notification application. | Gauge/ Int64
> out_email_rate | Indicates rate per second for out going e-mails. Trigger: When an e-mail is sent out for an event. Availability: Available across event notification application. | Gauge/ Int64
> out_sms_rate | Indicates rate per second for out going SMSs. Trigger: When an SMS is sent out for an event. Availability: Available across event notification application. | Gauge/ Int64
> in_sms_rate | Indicates rate per second for in coming SMSs. Trigger: When an event from IPCF or SSC is received at event notification manager with an SMS as notification method. Availability: Available across event notification application. | Gauge/ Int64
> in_email_rate | Indicates rate per second for in coming e-mails. Trigger: When an event from IPCF or SSC is received at event notification manager with an e-mail as notification method. Availability: Available across event notification application. | Gauge/ Int64
> sms_failed | Indicates total number of failed SMS. Trigger: When SMS send operation fails. Availability: Available across event notification application. | Gauge/ Int64
> email_failed | Indicates total number of failed e-mails. Trigger: When an e-mail send operation fails. Availability: Available across event notification application. | Gauge/ Int64

> ‌

Cisco Systems Inc.
Tel: 408-526-4000
Fax: 408-527-0883