9 CNC Policy Metrics
This chapter includes information about Metrics for Oracle Communications Cloud Native Core, Policy (CNC Policy).
- Observability Dashboard:
- This dashboard metadata is stored in the
Policy_Observability_Dashboard.jsonfile. - This dashboard has the panels that monitors the overall health status of the setup & contains details like resource utilization, kmps, latency, etc.
- Customers can use this Dashboard on a regular basis for observing the status of the setup and also for assessing the setup performance with a run.
- Depending upon the applicability of a panel or row, the customers have the flexibility to either remove, update or add content to the Dashboard.
- This dashboard metadata is stored in the
- Debug Dashboard:
- This dashboard metadata is stored in the
Policy_Debug_Dashboard.jsonfile. - This dashboard has the panels that monitor the operational status of the setup and is used for debugging & troubleshooting purposes.
- Customers can use this Dashboard when any issue occur in the NF and also when reporting a probable issue to Oracle Customer Support from the setup.
- Depending upon the applicability of a panel or row, the customers have the flexibility to either remove, update or add content to the Dashboard.
- This dashboard metadata is stored in the
The name of the metrics may contain suffix such as total, seconds, max and so on. It gets added by the Micrometer registry if it is not present in the metrics name. The metric name has the following format for suffix:
The metric name is equal to <Basename of the metric>_<Suffix>
Table 9-1 Metrics type and Suffix
| Metric Type | Suffix |
|---|---|
| Counter | _total |
| Gauge | N/A |
| TimerGauge | _seconds |
| MultiGauge | N/A |
| Timer | _seconds_max or _seconds
Note: There are two types of suffix used for timer metrics. For example, my_timer_seconds_max gauge and my_timer_seconds summary. In summary type, there will be further addition of suffix such as _count or _sum. |
| DistributionSummary | N/A or _max
Note: There are two types of suffix used for DistributionSummary. For example, my_distribution_ratio histogram and my_distribution_ratio_max gauge. In the histogram type there will be further addition of suffix such as bucket, _count, or sum. |
| LongTaskTimer | _seconds_max or _seconds
Note: There are two types of suffix used for LongTaskTimer. For example, long_task_timer_seconds_max gauge and long_task_timer_seconds summary. In summary type there will be further addition of suffix such as _active_count or _duration_sum. |
Note:
Metric names can consist of letters, numbers, underscores, and colons, as defined by the regular expression[a-zA-Z_:][a-zA-Z0-9_:]*.
Table 9-2 Dimension Description
| Dimension | Description | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| operation_type | Type of operation
Values:
|
||||||||||||||||
| dnn | Data Network Name or Access Point Name | ||||||||||||||||
| snssai | Single Network Slice Selection Assistance Information | ||||||||||||||||
| response_code | Response code
HTTP interfaces:
Diameter interfaces:
|
||||||||||||||||
| latency |
The total time in between request and response. If latency between request and response is 203, then bucket number is 4. Max bucket set to 10 (0-9), Range 50ms. |
||||||||||||||||
| old_state | Pod/Resource congestion state before transition. | ||||||||||||||||
| new_state | Pod/Resource congestion state after transition. | ||||||||||||||||
| nf_instance_Id | Unique id of the nf Instance.
HTTP interfaces: Diameter interfaces:
|
||||||||||||||||
| nf_name | This represents the FQDN corresponding to the NF
InstanceID present in the nf_instance_id dimension.
HTTP interface: egress: NF FQDN |
||||||||||||||||
| sbi_priority | Service Based Interface | ||||||||||||||||
| service_version | Service version
Value: [UDR = "v1,v2", CHF = "v1"] |
||||||||||||||||
| service | The complete name of current service.
Value: string |
||||||||||||||||
| namespace | The namespace of current service.
Value: string |
||||||||||||||||
| category | The category of current service.
Value:
|
||||||||||||||||
| destHost | Value of destination Host received or sent in the corresponding request message | ||||||||||||||||
| destRealm | Value of destination Realm received or sent in the corresponding request message | ||||||||||||||||
| origHost | Value of origination Host received or sent in the corresponding request message | ||||||||||||||||
| origRealm | Value of origination Realm received or sent in the corresponding request message | ||||||||||||||||
| reqDestHost | Value of destination Host in corresponding request message of response message. | ||||||||||||||||
| reqDestRealm | Value of destination Realm in corresponding request message of response message. | ||||||||||||||||
| reqOrigHost | Value of origination Host in corresponding request message of response message. | ||||||||||||||||
| reqOrigRealm | Value of origination Realm in corresponding request message of response message. | ||||||||||||||||
| direction | Indicates direction of message flow.
|
||||||||||||||||
| appId | Application ID exchanged in CEX messages or used in the respective message of an application. | ||||||||||||||||
| applicationName | Human readable name of corresponding application ID
16777236 => Rx 16777238 => Gx 16777302 => Sy 0xffffffff => Relay |
||||||||||||||||
| cmdCode | Command code value in the received or sent, request or answer message | ||||||||||||||||
| msgType | Type of the message, for example CCRT-T, CCR-I etc. | ||||||||||||||||
| responseCode | Result code such as 2xx,5xx,4xx in diameter
messages.
It indicates the response received/sent for HTTP messages or exceptions. |
||||||||||||||||
| spendingLimitDataSource | Specifies the source from which PCF fetches policy
counters.
Value: OCS |
||||||||||||||||
| retry | Identify message is a retry message.
Value:
|
||||||||||||||||
| retryAnswer | Reason for the retry message.
Value:
|
||||||||||||||||
| level | Indicates
the current load level or the level of pod congestion.
Value:
|
||||||||||||||||
| type | Resource type
Value:
|
||||||||||||||||
| le | le is abbreviated as "Less than equal to".Value of a defined bucket for a Histogram. | ||||||||||||||||
| sessRuleReports | Indicates that session rule report is received at PCF. | ||||||||||||||||
| policyDecFailureReports | Indicates that Policy decision failure report is received at PCF. | ||||||||||||||||
| isLeaderPod | Indicates if the pod calculating the threshold level is a leader pod. | ||||||||||||||||
| prevLevel | Indicates the previous load level prior to current load level calculation. | ||||||||||||||||
| levelChangeType | Indicates the level change type. The value of this
dimension can be:
|
||||||||||||||||
| servicenameNon3gpp | |||||||||||||||||
| serviceResource | |||||||||||||||||
| params | Lists the API parameters. | ||||||||||||||||
| outcome | Shows the outcome of an operation such as SUCCESS, FAILURE, TIMEOUT. | ||||||||||||||||
| cause | Contains the error cause. | ||||||||||||||||
| sourceUri |
NF Service URI that leads to this service request. Format of this dimension is the same as that of uri attribute. For example: /npcf-smpolicycontrol/v1/sm-policies The value of this dimension is included in the
For locally originated requests such as timer based, value of this dimension can be "" or the timer name. if sourceUri is not received in the header from the core service, the value of this dimension will be same as uri dimension. |
||||||||||||||||
| sourceOperationType |
NF Service HTTP verb or operation type that leads to this service request. Value is included in the oc-x-source-operation header in the incoming request such as CREATE, UPDATE, or DELETE. For locally originated requests such as timer based, value of this dimension can be "" or the timer name. If sourceOperationType is not received in the header from Core service, the value remains the same as operationType dimension. |
||||||||||||||||
| Uri |
Includes the resource URI in generic format. For example: /binding/v1/contextBinding/context-owner/{contextOwner} |
||||||||||||||||
| serviceResource | |||||||||||||||||
| responseCause | In case of responseCode as exception, this dimension
provides additional cause such as Timeout and Server Internal Error.
Note: This dimension is used only for exceptions. In case of successful operation, this dimension value will become empty. |
||||||||||||||||
| Duration | Only applicable to "processing_latency_ms"
metrics.
This is to indicate bucket, that are managed by promclient as "le" dimension. Example: Bucket as 3ms, 5ms, 10ms, 15ms, 20ms, 30ms, 50ms, 100ms |
||||||||||||||||
| Stage | |||||||||||||||||
| result_code | Indicates received LDAP response code.
Example values: 32, 85, 91 |
||||||||||||||||
| destination_host | Indicates the IP address or FQDN of LDAP server. | ||||||||||||||||
| peerHost | Indicates the value of peer host received or sent in corresponding connection request message. | ||||||||||||||||
| peerRealm | Indicates the value of peer realm received or sent in corresponding connection request message. | ||||||||||||||||
|
accessType access_type |
Access Type.
|
||||||||||||||||
| policyControlRequestTrigger | Policy Control Request Trigger can have single value
or comma separated list of values ordered alphabetically.
|
||||||||||||||||
|
rat_type ratType |
Radio Access Type.
|
||||||||||||||||
| sourceAccessType | Previous access type before the update.
|
||||||||||||||||
| sourceRatType | Previous radio access type before the update.
|
||||||||||||||||
| reattempt_timer_expiry_notification | This value in source dimension indicates consolidation done on receiving Timer Expiry Notification from Timer Service. | ||||||||||||||||
| isReattempt | Set to true/false.
|
||||||||||||||||
| isRetryAttempt | Set to true/false based on first or subsequent alternate attempt towards host. | ||||||||||||||||
| reattemptType | Set to String. It tells the type of reattempt requests, whether it is for Subscribe/Transfer/TransferFailureNotification. Its value is the timerName - for which the timer was created and was reattempted . | ||||||||||||||||
| priority |
This dimension indicates message priority, when available. It supports both oc-message-priority and 3gpp-sbi-message-priority. 3gpp-sbi-message-priority must have higher precedence. |
||||||||||||||||
| reason | The values:
|
||||||||||||||||
| sponId | Includes the sponId received through the N5 interface. | ||||||||||||||||
| aspId | Includes the aspId received through the N5 interface. | ||||||||||||||||
| servicename3gpp | The value of this dimension is the service name and
version. For example: npcf-smpolicycontrol.
|
||||||||||||||||
| umcDataIncluded | This dimension reflects whether the sponsored
session contained UMC data, last status received through the N5
interface is reflected for DELETE operation if UMC not received.
Possible values: True, False |
||||||||||||||||
| sponStatus | This dimension indicates the last status received through the N5 interface. Even if the request arrived is Delete, the last sponStatus received is displayed in order to indicate whether it was a sponsored session or not. For example, SPONSOR_ENABLED/SPONSOR_DISABLED. | ||||||||||||||||
| operationTypeN5 | The value in this dimension is the operation type that triggers the update_notify towards the SMF that is received through N5 interface. For example: CREATE, UPDATE, DELETE. | ||||||||||||||||
| application | The name of application from which the metric is triggered. For example: policyds | ||||||||||||||||
| application_exception | The class name of the exception container in which the real exception is wrapped and send to error-handler. For example: HttpException | ||||||||||||||||
| wrapped_exception | The class name of real exception that needs to be
handled by error-handler. This will be wrapped inside the
application exception. For example: ServiceUnavailable,
TimeoutException, HttpClientResponseException
Note: After migrating the framework from Springboot to Micronaut, the WebClientResponseException is changed to HttpClientResponseException. |
||||||||||||||||
| error_type | Type of the error handled. | ||||||||||||||||
| operation | The tagged operation during which the error occurred. | ||||||||||||||||
| origin | The tagged origin of error. | ||||||||||||||||
| rule_name | The name of rule configured and evaluated by error-handler to resolve the issue. | ||||||||||||||||
| source_interface | The name of interface/NF from which the communication started. | ||||||||||||||||
| target_interface | The name of interface/NF to which the communication targeted. | ||||||||||||||||
| error_resolved | Boolean flag which determines if the error is resolved by error-handler. | ||||||||||||||||
| search_key_type | Key used during the search operation. Possible Values: SUPI, PDS_LOCATION, GPSI, SSVID, SUPI/GPSI, PDS_PROFILE_ID, PDS_USER_ID, SY_SESSION_ID, NA (used when operation is not SEARCH) | ||||||||||||||||
| migration_enabled |
Indicates if migration is in progress. Possible values:true, false |
||||||||||||||||
| mode |
Indicates current mode, which includes the selected typeOfSearch
or preferenceKey in the UI.Possible values are listed in below
Mode table:
Table 9-3 Format of different modes
|
||||||||||||||||
| prev_mode | Previous mode, which includes the earlier selected typeOfSearch or preferenceKey in the UI.Possible values are listed in above Mode table. Migration type (single → multi, multi → single, or single → single) is derived by comparing prev_mode and mode. | ||||||||||||||||
| response_content |
Indicates whether the DB query response content is empty or not. Possible values: EMPTY, NON_EMPTY |
9.1 TLS Metrics
The following table describes the TLS metrics and the respective dimensions:
Table 9-4 oc_ingressgateway_incoming_tls_connections
| Field | Details |
|---|---|
| Description | Number of TLS Connections received on the Ingress Gateway and their negotiated TLS versions. The versions can be TLSv1.3 or TLSv1.2 |
| Type | Gauge |
| Dimensions |
|
| Example | - |
Table 9-5 oc_egressgateway_incoming_tls_connections
| Field | Details |
|---|---|
| Description | Number of TLS Connections received on the Egress Gateway and their negotiated TLS versions. The versions can be TLSv1.3 or TLSv1.2 |
| Type | Gauge |
| Dimensions |
|
| Example | - |
Table 9-6 security_cert_x509_expiration_seconds
| Field | Details |
|---|---|
| Description | Indicates the time to certificate expiry in epoch seconds. |
| Type | Histogram |
| Dimensions | serialNumber |
| Example | - |
Table 9-7 diam_conn_network
| Field | Details |
|---|---|
| Description | Indicates the number of TLS connections per TLS version. |
| Type | Gauge |
| Dimensions |
|
| Example | - |
Table 9-8 diam_failed_conn_network
| Field | Details |
|---|---|
| Description | Indicates the number of failed TLS connections.
Note: It is applicable when we configure Initiate Connection to true in peer node configurations in the CNC Console. |
| Type | Gauge |
| Dimensions |
|
| Example | diam_failed_conn_network{peerName="dgw",reason="SSL Handshake Exception",} 1.0 |
Table 9-9 diam_conn_network_responder
| Field | Details |
|---|---|
| Description | Indicates the number of allowed TLS responder connections with or without the peer configuration. |
| Type | Gauge |
| Dimensions |
|
| Example | - |
Table 9-10 dgw_tls_cert_expiration_seconds
| Field | Details |
|---|---|
| Description | Indicates the number of allowed TLS responder connections with or without the peer configuration. |
| Type | Gauge |
| Dimensions |
|
| Example | dgw_tls_cert_expiration_seconds{serialNumber="122859034516052844067924392230910496431389299229",subject="OU=CGIU, O=ORCL, L=BLR, ST=KA, C=IN",} 1.797882352E9 |
9.2 Egress Gateway Metrics for SCP
Note:
Peer health pings happen in Primary pod only and not in secondary pod due to which metrics are getting pegged in Primary pod only.
Table 9-11 oc_egressgateway_peer_health_status
| Field | Details |
|---|---|
| Description |
It defines Egress Gateway peer health status.
|
| Metric Type | Gauge |
| Dimensions |
|
- oc_egressgateway_peer_health_status{"peer":"10.75.213.172:8080"} 1.0
- oc_egressgateway_peer_health_status{"peer":"10.75.213.172:8080"} 0.0
- oc_egressgateway_peer_health_status{"vfqdn":"http://abc.com","peer":"10.75.213.172:8080"} 1.0
- oc_egressgateway_peer_health_status{"vfqdn":"http://abc.com","peer":"10.75.213.172:8080"} 0.0
Table 9-12 oc_egressgateway_peer_health_ping_request_total
| Field | Details |
|---|---|
| Description | This metric is incremented every time a health ping is sent toward a peer. |
| Metric Type | Counter |
| Dimensions |
|
- oc_egressgateway_peer_health_ping_request_total{"peer":"10.75.213.172:8080"} 389.0
- oc_egressgateway_peer_health_ping_request_total{"peer":"10.75.213.172:8080"} 439.0
- oc_egressgateway_peer_health_ping_request_total{"vfqdn":"http://abc.com","peer":"10.75.213.172:8080"} 389.0
- oc_egressgateway_peer_health_ping_request_total{"vfqdn":"http://abc.com","peer":"10.75.213.172:8080"} 439.0
Table 9-13 oc_egressgateway_peer_health_ping_response_total
| Field | Details |
|---|---|
| Description | This metric is incremented every time a health ping response is received from a peer irrespective of success or failure. |
| Metric Type | Counter |
| Dimensions |
|
- oc_egressgateway_peer_health_ping_response_total{"peer":"10.75.213.172:8080","status":"httpstatus","cause":""} 89.0
- oc_egressgateway_peer_health_ping_response_total{"peer":"10.75.213.172:8080","status":"Exception","cause":"exception cause"} 39.0
- oc_egressgateway_peer_health_ping_response_total{"vfqdn":"http://abc.com","status":"httpstatus","cause":""} 89.0
- oc_egressgateway_peer_health_ping_response_total{"vfqdn":"http://abc.com","status":"Exception","cause":"exception cause"} 39.0
Table 9-14 oc_egressgateway_peer_health_status_transitions_total
| Field | Details |
|---|---|
| Description | This metric is incremented every time a peer is transitioned from Available to Unavailable or from Unavailable to Available. |
| Metric Type | Counter |
| Dimensions |
|
- oc_egressgateway_peer_health_status_transitions_total{"identifier":"10.75.213.172:8080","from":"available","to":"unavailable"} 14.0
- oc_egressgateway_peer_health_status_transitions_total{"identifier":"10.75.213.172:8080","from":"unavailable","to":"available"} 34.0
- oc_egressgateway_peer_health_status_transitions_total{"vfqdn":"http://abc.com","peer":"10.75.213.172:8080","from":"unavailable","to":"available"} 34.0
- oc_egressgateway_peer_health_status_transitions_total{"vfqdn":"http://abc.com","peer":"10.75.213.172:8080","from":"available","to":"unavailable"} 14.0
Table 9-15 counterespionage
| Field | Details |
|---|---|
| Description | This metric is incremented every time for the peer count. |
| Metric Type | Gauge |
| Dimensions |
|
- counterespionage{"peerset":"set-0"} 3.0
Table 9-16 oc_egressgateway_peer_available_count
| Field | Details |
|---|---|
| Description | This metric is incremented every time for the available peer count. |
| Metric Type | Gauge |
| Dimensions |
|
Examples:
- oc_egressgateway_peer_available_count{"peerset":"set-0"} 4.0
9.3 Correlation-Info Header Metrics
For every correlation-info header received or newly generated, a metric is pegged. Following are the list of metrics:
Below table lists the metrics that is implemented as part of this feature with the following Dimensions:
- operation_type= {"create","update","delete","subscribe","unsubscribe","terminate","register","deregister"}
- correlation_info_type={"imsi", "msisdn", "imsi,msisdn"}
Table 9-17 occnp_correlation_info_header_received
| Field | Details |
|---|---|
| Description |
PCF reports the total incoming requests that are carrying the correlation-info header. |
| Metric Type | Counter |
| Dimensions |
|
- occnp_correlation_info_header_received_total '{correlation_info_type="imsi", operation_type="create"}',2
- occnp_correlation_info_header_received_total '{correlation_info_type="imsi", operation_type="update"}',1
Table 9-18 occnp_correlation_info_header_forwarded
| Field | Details |
|---|---|
| Description |
PCF reports the total outgoing requests that are carrying the correlation-info header. |
| Metric Type | Counter |
| Dimensions |
|
- occnp_correlation_info_header_forwarded_total '{correlation_info_type="imsi", operation_type="subscribe"}',2
Table 9-19 occnp_correlation_info_header_generated
| Field | Details |
|---|---|
| Description |
PCF reports the total responses that are carrying the correlation-info header. |
| Metric Type | Counter |
| Dimensions |
|
- occnp_correlation_info_header_generated_total '{correlation_info_type="imsi", operation_type="create"}',2
9.4 Config Server Metrics
The following table describes the Config Server metrics and respective dimensions:
Table 9-20 topic_version
| Field | Details |
|---|---|
| Description |
Config-service will have this metrics a database value from each topic version. The Services fetching the configurations from Configuration Server, will have its current topic version till which configurations has been fetched successfully. Note: This counter metric keep updating on every successful iteration. |
| Metric Type | Gauge |
| Dimensions |
|
- topic_version{topicName="pcf.public.sessionrule",} 77.0
- topic_version{topicName="common.logging.diam-connector",} 53.0
- topic_version{topicName="pcf.userservice.cfg",} 35.0
- topic_version{topicName="pcrf.public.networkelement.pgw",} 2.0
- topic_version{topicName="NRF.BSF",} 20.0
- topic_version{topicName="common.bindingservice.cfg",} 6.0
- topic_version{topicName="common.logging.policy-ds",} 21.0
- topic_version{topicName="NRF.UDR",} 22.0
- topic_version{topicName="common.logging.diam-gateway",} 93.0
- topic_version{topicName="common.logging.pcf-user",} 35.0
- topic_version{topicName="common.logging.pcf-sm",} 78.0
- topic_version{topicName="pcrf.coreservice",} 3.0
- topic_version{topicName="public.policy.project",} 148.0
- topic_version{topicName="Subscriptions",} 14.0
- topic_version{topicName="pcf.smservice.cfg",} 126.0
- topic_version{topicName="common.public.feature1",} 10.0
- topic_version{topicName="common.public.diampeernode",} 2.0
- topic_version{topicName="common.logging.pcrf-core",} 2.0
- topic_version{topicName="pcf.public.authorizeddefaultqos",} 77.0
- topic_version{topicName="public.policy.project.content",} 85.0
- topic_version{topicName="pcf.public.pccrule",} 85.0
- topic_version{topicName="NRF.CHF",} 52.0
- topic_version{topicName="config.level",} 1053.0
- topic_version{topicName="pds.public.settings",} 2.0
Table 9-21 occnp_config_server_overall_processing_time_seconds
| Field | Details |
|---|---|
| Description | Configuration server's overall processing time. |
| Type | Summary |
| Dimension |
|
Table 9-22 occnp_config_server_overall_processing_time_seconds_max
| Field | Details |
|---|---|
| Description | Configuration service overall processing time. |
| Type | Gauge |
| Dimension |
|
- occnp_config_server_overall_processing_time_seconds_max{error="none", exception="none", method="POST", outcome="SUCCESS", status="201", uri="/binding/v1/contextBinding/context-owner/{contextOwner}",} 2.595594434
- occnp_config_server_overall_processing_time_seconds_max{error="none", exception="none", method="DELETE", outcome="SUCCESS", status="204", uri="/binding/v1/contextBinding/contextId/{contextId}",} 0.276239293
- occnp_config_server_overall_processing_time_seconds_max{error="ContextBindingNotFound", exception="ContextBindingNotFound", method="DELETE", outcome="CLIENT_ERROR", status="404", uri="/binding/v1/contextBinding/cleanup",} 0.115288423
Table 9-23 occnp_config_server_overall_processing_time_seconds_count
| Field | Details |
|---|---|
| Description | Configuration service overall processing time. |
| Type | Counter |
| Dimension |
|
- occnp_config_server_overall_processing_time_seconds_count{error="none", exception="none", method="POST", outcome="SUCCESS", status="201", uri="/binding/v1/contextBinding/context-owner/{contextOwner}",} 3.0
- occnp_config_server_overall_processing_time_seconds_count{error="none", exception="none", method="DELETE", outcome="SUCCESS", status="204", uri="/binding/v1/contextBinding/contextId/{contextId}",} 3.0
- occnp_config_server_overall_processing_time_seconds_count{error="ContextBindingNotFound", exception="ContextBindingNotFound",method="DELETE",outcome="CLIENT_ERROR",status="404",uri="/binding/v1/contextBinding/cleanup",} 6.0
Table 9-24 occnp_config_server_overall_processing_time_seconds_sum
| Field | Details |
|---|---|
| Description | Configuration service overall processing time. |
| Type | Counter |
| Dimension |
|
- occnp_config_server_overall_processing_time_seconds_sum{error="none",exception="none",method="POST", outcome="SUCCESS", status="201", uri="/binding/v1/contextBinding/context-owner/{contextOwner}",} 5.861114721
- occnp_config_server_overall_processing_time_seconds_sum{error="none", exception="none",method="DELETE",outcome="SUCCESS",status="204",uri="/binding/v1/contextBinding/contextId/{contextId}",} 0.349598291
- occnp_config_server_overall_processing_time_seconds_sum{error="ContextBindingNotFound",exception="ContextBindingNotFound", method="DELETE",outcome="CLIENT_ERROR",status="404", uri="/binding/v1/contextBinding/cleanup",} 0.203103476
Table 9-25 occnp_config_server_db_operation_time_seconds_count
| Field | Details |
|---|---|
| Description | Configuration service overall database processing time. |
| Type | Gauge |
| Dimension |
|
- occnp_config_server_db_operation_time_seconds_count{exception="None",method="findByTopicInfo",repository="ConfigurationItemRepository",state="SUCCESS",} 7721880.0
- occnp_config_server_db_operation_time_seconds_count{exception="None",method="findByName",repository="TopicInfoRepository",state="SUCCESS",} 8190322.0
Table 9-26 occnp_config_server_db_operation_time_seconds_sum
| Field | Details |
|---|---|
| Description | Configuration service overall database processing time. |
| Type | Gauge |
| Dimension |
|
- occnp_config_server_db_operation_time_seconds_sum{exception="None",method="findByTopicInfo",repository="ConfigurationItemRepository",state="SUCCESS",} 4713.01
- occnp_config_server_db_operation_time_seconds_sum{exception="None",method="findByName",repository="TopicInfoRepository",state="SUCCESS",} 6328.74490
Table 9-27 occnp_config_server_db_operation_time_seconds_max
| Field | Details |
|---|---|
| Description | Configuration service overall database processing time. |
| Type | Gauge |
| Dimension |
|
9.5 SM Service Metrics
The following table describes the SM Service metrics and respective dimensions:
Table 9-28 ocpm_ingress_request_total
| Field | Details |
|---|---|
| Description | Total number of ingress requests received. |
| Metric Type | Counter |
| Dimensions |
|
| Examples |
|
Table 9-29 ocpm_ingress_response_total
| Field | Details |
|---|---|
| Description | Total number of ingress responses. |
| Metric Type | Counter |
| Dimensions |
|
| Examples |
|
Table 9-30 ocpm_egress_request_total
| Field | Details |
|---|---|
| Description | Total number of egress requests received. |
| Metric Type | Counter |
| Dimensions |
|
| Examples |
|
Table 9-31 ocpm_egress_response_total
| Field | Details |
|---|---|
| Description | Total number of egress responses. |
| Metric Type | Counter |
| Dimensions |
|
| Examples |
|
Table 9-32 occnp_sm_binding_request_total
| Field | Details |
|---|---|
| Description | Total number of binding requests. |
| Metric Type | Counter |
| Dimensions |
|
- occnp_sm_binding_request_total{application="pcf_smservice",dnn="dnn1",hostname="a-pcf-smservice-fbbfccdf-vvdr6",mode="synchronous",nf_instance_id="fe7d992b-0541-4c7d-ab84-6d70b1babc1",nf_name="bsf.xxxx.com",operation_type="create",snssai="11-abc111",} 1.0; Type-Counter
- occnp_sm_binding_request_total{application="pcf_smservice",dnn="dnn1",hostname="a-pcf-smservice-fbbfccdf-vvdr6",mode="synchronous",nf_instance_id="fe7d992b-0541-4c7d-ab84-6d70b1babc1",nf_name="bsf.xxxx.com",operation_type="update",snssai="11-abc111",} 1.0; Type-Counter
- occnp_sm_binding_request_total{application="pcf_smservice",dnn="dnn1",hostname="a-pcf-smservice-fbbfccdf-vvdr6",mode="synchronous",nf_instance_id="fe7d992b-0541-4c7d-ab84-6d70b1babc1",nf_name="bsf.xxxx.com",operation_type="delete",snssai="11-abc111",} 1.0; Type-Counter
Table 9-33 occnp_sm_binding_response_total
| Field | Details |
|---|---|
| Description | Total number of binding responses. |
| Metric Type | Counter |
| Dimensions |
|
- occnp_sm_binding_response_total{application="pcf_smservice",dnn="dnn1",hostname="a-pcf-smservice-fbbfccdf-vvdr6",mode="synchronous",nf_instance_id="fe7d992b-0541-4c7d-ab84-6d70b1babc1",nf_name="bsf.xxxx.com",operation_type="create",response_code="2xx",snssai="11-abc111",} 1.0; Type-Counter
- occnp_sm_binding_response_total{application="pcf_smservice",dnn="dnn1",hostname="a-pcf-smservice-fbbfccdf-vvdr6",mode="synchronous",nf_instance_id="fe7d992b-0541-4c7d-ab84-6d70b1babc1",nf_name="bsf.xxxx.com",operation_type="update",response_code="2xx",snssai="11-abc111",} 1.0; Type-Counter
- occnp_sm_binding_response_total{application="pcf_smservice",dnn="dnn1",hostname="a-pcf-smservice-fbbfccdf-vvdr6",mode="synchronous",nf_instance_id="fe7d992b-0541-4c7d-ab84-6d70b1babc1",nf_name="bsf.xxxx.com",operation_type="delete",response_code="2xx",snssai="11-abc111",} 1.0; Type-Counter
Table 9-34 occnp_sm_binding_ex_total
| Field | Details |
|---|---|
| Description | The number of binding operations that cannot be performed due to an exception (timeout). |
| Metric Type | Counter |
| Dimensions |
|
- occnp_sm_binding_ex_total{application="pcf_smservice",dnn="dnn1",snssai="1-000001",operation_type="create",mode="asynchronous",} 1.0 ; Type-Counter
- occnp_sm_binding_ex_total{application="pcf_smservice",dnn="dnn1",snssai="1-000001",operation_type="update",mode="asynchronous",} 1.0 ; Type-Counter
- occnp_sm_binding_ex_total{application="pcf_smservice",dnn="dnn1",snssai="1-000001",operation_type="delete",mode="asynchronous",} 1.0 ; Type-Counter
Table 9-35 ocpm_egress_request_timeout_total
| Field | Details |
|---|---|
| Description | Total number of request timeouts from SMF. |
| Metric Type | Counter |
| Dimensions |
|
- ocpm_egress_request_timeout_total{application="pcf_smservice",dnn="dnn1",egress_service="SMF",hostname="pcf_smservice",nf_instance_id="",nf_name="smf-xxxx.com",operation_type="POST",resource_name="SmPolicyNotification",sbi_priority="",service_name="notification",servicename_3gpp="npcf-smpolicycontrol",snssai="11-abc123",} 1.0; Type-Counter
- ocpm_egress_request_timeout_total{application="pcf_smservice",dnn="dnn1",egress_service="SMF",hostname="pcf_smservice",nf_instance_id="",nf_name="smf-xxxx.com",operation_type="POST",resource_name="TerminationNotification",sbi_priority="",service_name="notification",servicename_3gpp="npcf-smpolicycontrol",snssai="11-abc123",} 1.0; Type-Counter
- ocpm_egress_request_timeout_total{application="pcf_smservice",dnn="dnn1",egress_service="BSF",hostname="pcf_smservice",nf_instance_id="fe7d992b-0541-4c7d-ab84-6d70b1babc1",nf_name="bsf-xxxx.com",operation_type="POST",resource_name="PCFSessionBindings",sbi_priority="",service_name="nbsf-management",servicename_3gpp="npcf-smpolicycontrol",snssai="11-abc123",} 1.0; Type-Counter
- ocpm_egress_request_timeout_total{application="pcf_smservice",dnn="dnn1",egress_service="BSF",hostname="pcf_smservice",nf_instance_id="fe7d992b-0541-4c7d-ab84-6d70b1babc1",nf_name="bsf-xxxx.com",operation_type="DELETE",resource_name="IndividualPCFSessionBinding",sbi_priority="",service_name="nbsf-management",servicename_3gpp="npcf-smpolicycontrol",snssai="11-abc123",} 1.0; Type-Counter
- ocpm_egress_request_timeout_total{application="pcf_smservice",dnn="", egress_service="TDF",nf_instance_id="",nf_name="localhost",operation_type="tdf_notify_create_session_request",resource_name="",sbi_priority="",service_name="notification",servicename_3gpp="npcf-smpolicycontrol",snssai="",} 1.0
Table 9-36 remote_delete_notify_total
| Field | Details |
|---|---|
| Description | Total number of notifications for session delete requests at SM service. |
| Metric Type | Counter |
| Dimensions |
|
- remote_delete_notify_total{Code="2xx",Request="DeleteNotify",SessionType="SM",application="pcf_smservice",hostname="4dfc2dfc25da",} 0.0
- remote_delete_notify_total{Code="4xx",Request="DeleteNotify",SessionType="SM",application="pcf_smservice",hostname="4dfc2dfc25da",} 0.0
- remote_delete_notify_total{Code="5xx",Request="DeleteNotify",SessionType="SM",application="pcf_smservice",hostname="4dfc2dfc25da",} 0.0
- remote_delete_notify_total{Code="N/A",Request="EmulateDelete",SessionType="SM",application="pcf_smservice",hostname="4dfc2dfc25da",} 0.0
Table 9-37 audit_notifications_sent_total
| Field | Details |
|---|---|
| Description | Number of audit notifications to SM service that are processed. |
| Metric Type | Counter |
| Dimensions |
|
Table 9-38 audit_update_notify_session_not_found_total
| Field | Details |
|---|---|
| Description | Number of 404 response sent by SMF for the records which are identified as stale by Audit Service. |
| Metric Type | Counter |
| Dimensions |
|
Table 9-39 audit_update_notify_session_found_total
| Field | Details |
|---|---|
| Description | Number of 204 response sent by SMF for the records which are identified as stale by Audit Service. |
| Metric Type | Counter |
| Dimensions |
|
Table 9-40 audit_update_notify_response_error_total
| Field | Details |
|---|---|
| Description | Number of update notify requests sent to SMF by SM service that were responded with an error code (except 404) |
| Metric Type | Counter |
| Dimensions |
|
Table 9-41 audit_update_timestamp_cnt_total
| Field | Details |
|---|---|
| Description | Number of records whose LASTACESSTIME column is updated by SM Service when it receives 204 response from SMF |
| Metric Type | Counter |
| Dimensions |
|
Table 9-42 audit_delete_records_count_total
| Field | Details |
|---|---|
| Description | Number of records deleted by SM Service when it receives 404 response from SMF. |
| Metric Type | Counter |
| Dimensions |
|
Table 9-43 audit_delete_records_max_ttl_count_total
| Field | Details |
|---|---|
| Description | Number of records deleted by SM Service when the max TTL was reached |
| Metric Type | Counter |
| Dimensions |
|
Table 9-44 session_oam_request_total
| Field | Details |
|---|---|
| Description | Number of session requests for SM Service |
| Metric Type | Request |
| Dimensions |
|
| Examples |
|
Table 9-45 session_oam_response_total
| Field | Details |
|---|---|
| Description | Number of session responses for SM Service |
| Metric Type | Response |
| Dimensions |
|
| Examples |
|
Table 9-46 occnp_http_sm_request_total
| Field | Details |
|---|---|
| Description | Total number of http requests. |
| Metric Type | Request |
| Dimensions |
|
| Examples |
|
Table 9-47 occnp_http_sm_response_total
| Field | Details |
|---|---|
| Description | Total number of http responses. |
| Metric Type | Response |
| Dimensions |
|
| Examples |
|
Table 9-48 occnp_http_in_conn_request_total
| Field | Details |
|---|---|
| Description | The requests received by a micro-service from downstream. |
| Metric Type | Counter |
| Dimensions |
|
| Examples |
|
Table 9-49 occnp_http_in_conn_response_total
| Field | Details |
|---|---|
| Description | The response sent for incoming requests to a micro-service. |
| Metric Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-50 http_in_conn_ext_request_total
| Field | Details |
|---|---|
| Description |
The requests received by a micro-service to update the ratType or accessType on receiving policyControlRequestTrigger as "AC_TY_CH", "PRA_CH", "RAT_TY_CH" or multiple values separated by comma. For delete requests policyControlRequestTrigger is not mandatory. This metric will be pegged after we know the source radio access type or the source access type during the update process. Note: This metric is not pegged if any of these values do
not come as part of
policyControlRequestTrigger
dimension:
They can come individually, together, or along other values. When list of values is received, at least one of the previous values must be present; otherwise, the metric is not be pegged. |
| Metric Type | Counter |
| Dimensions |
|
| Examples |
|
Table 9-51 http_in_conn_ext_response_total
| Field | Details |
|---|---|
| Description |
The response sent for incoming requests to a micro-service after update the ratType or when we receive the value of policyControlRequestTrigger as "AC_TY_CH", "PRA_CH", "RAT_TY_CH" or multiple values separated by comma. For delete requests policyControlRequestTrigger is not mandatory. Note: This metric is not pegged if any of these values do
not come as part of
policyControlRequestTrigger
dimension:
They can come individually, together, or along other values. When list of values is received, at least one of the previous values must be present; otherwise, the metric is not be pegged. |
| Metric Type | Counter |
| Dimensions |
|
| Examples |
|
Table 9-52 occnp_http_out_conn_request_total
| Field | Details |
|---|---|
| Description | Total number of http connection requests. |
| Metric Type | Counter |
| Dimensions |
|
| Examples |
|
Table 9-53 occnp_http_out_conn_response_total
| Field | Details |
|---|---|
| Description | Total number of http connection responses. |
| Metric Type | Counter |
| Dimensions |
|
| Examples |
|
Table 9-54 occnp_sm_sess_rule_failure_total
| Field | Details |
|---|---|
| Description | Indicates failure count because of session rule failure |
| Metric Type | Counter |
| Dimensions |
|
Table 9-55 lock_request_total
| Field | Details |
|---|---|
| Description | Number of times the SM Service tries to acquire the lock |
| Metric Type | Counter |
| Dimensions |
|
Table 9-56 lock_response_total
| Field | Details |
|---|---|
| Description | Number of times the Bulwark Service responds to SM Service for the lock request |
| Metric Type | Counter |
| Dimensions |
|
Table 9-57 occnp_http_sm_request_total
| Field | Details |
|---|---|
| Description | Number of times the SM Service sends an update request |
| Metric Type | Counter |
| Dimensions |
|
Table 9-58 occnp_http_sm_response_total
| Field | Details |
|---|---|
| Description | Number of times the SM Service receives a response |
| Metric Type | Counter |
| Dimensions |
|
Table 9-59 occnp_lease_duration_seconds_bucket
| Field | Details |
|---|---|
| Description | Time in seconds for which SM Service holds the lock |
| Metric Type | Histogram |
| Dimensions |
|
Table 9-60 rule_action
| Field | Details |
|---|---|
| Description |
Provides metric for:
|
| Metric Type | - |
| Dimensions |
|
- rule_action_total{action="SUCC_RES_ALLO",application="pcf_smservice",rule_type="pcc",type="request",} 1.0
- rule_action_total{action="SUCC_RES_ALLO",application="pcf_smservice",rule_type="pcc",type="report",} 1.0
Table 9-61 ocpm_timeout_total
| Field | Details |
|---|---|
| Description | Total number of increments whenever a timeout is detected |
| Metric Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-62 topic_version
| Field | Details |
|---|---|
| Description | Describes the current applied version of a given topic (mentioned in dimension topic_name) into the pod. |
| Metric Type | Gauge |
| Dimensions |
|
Table 9-63 occnp_db_overall_processing_time_seconds_max
| Field | Details |
|---|---|
| Description | Overall processing time of a database. |
| Metric Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-64 audit_delete_records_max_ttl_count
| Field | Details |
|---|---|
| Description |
Indicates number of audit notifications sent by Audit service to SM service that are processed with MaxTTL as true (delete Rx Session, NO ASR). |
| Metric Type | Counter |
| Dimensions |
|
Table 9-65 audit_terminate_notify
| Field | Details |
|---|---|
| Description | ASA response code metrics |
| Metric Type | Counter |
| Dimensions |
|
Table 9-66 occnp_internal_delete_request_total
| Field | Details |
|---|---|
| Description | Total number of internal delete request triggered on remote cleanup when forceDeleteOnError is true or forceDeleteOnExpiryOfWaitTimer is true. |
| Metric Type | Counter |
| Dimensions |
|
| Examples |
|
Table 9-67 occnp_internal_delete_response_total
| Field | Details |
|---|---|
| Description | Total number of internal delete response when forceDeleteOnError is true or forceDeleteOnExpiryOfWaitTimer is true. |
| Metric Type | Counter |
| Dimensions |
|
| Examples |
|
Table 9-68 occnp_error_handler_in_total
| Field | Details |
|---|---|
| Description | This metric is incremented on initialization of error handling. |
| Type | Counter |
| Dimension |
|
| Example |
|
Table 9-69 occnp_error_handler_exec_total
| Field | Details |
|---|---|
| Description | This metric is incremented on error handling performed by framework. |
| Type | Counter |
| Dimension |
|
| Example |
|
Table 9-70 occnp_error_handler_out_total
| Field | Details |
|---|---|
| Description | This metric is incremented on completion of error handling. |
| Type | Counter |
| Dimension |
|
| Example |
|
Table 9-71 occnp_pcf_smservice_overall_processing_time_seconds
| Field | Details |
|---|---|
| Description | SM service overall processing time. |
| Type | Summary |
| Dimension |
|
Table 9-72 occnp_pcf_smservice_overall_processing_time_seconds_max
| Field | Details |
|---|---|
| Description | SM service overall processing time. |
| Type | Gauge |
| Dimension |
|
| Example |
|
Table 9-73 occnp_pcf_smservice_overall_processing_time_seconds_count
| Field | Details |
|---|---|
| Description | SM service overall processing time. |
| Type | Counter |
| Dimension |
|
| Example |
|
Table 9-74 occnp_pcf_smservice_overall_processing_time_seconds_sum
| Field | Details |
|---|---|
| Description | SM service overall processing time. |
| Type | Gauge |
| Dimension |
|
| Example |
|
Table 9-75 update_notify_total
| Field | Details |
|---|---|
| Description | This metrics is pegged for to show that there is no notification being sent when there is an AAR message with the flow status as REMOVED and the Message type as either AUDIO, MESSAGE, or OTHER. |
| Type | Counter |
| Dimension |
|
| Example | update_notify_total{application="pcf_smservice",cause="FLOW_STATUS_REMOVED",hostname="gmtommy-pcf-smservice-56cb4584df-clsfd",optimized="Yes",} 2.0 |
Table 9-76 collision_detection_local_delete
| Field | Details |
|---|---|
| Description | Measures number of internal deletes due to duplicate session request. |
| Type | Counter |
| Dimension |
|
| Example | - |
Table 9-77 collision_detection_terminate_notify
| Field | Details |
|---|---|
| Description | Measures number of session terminate request sent due to duplicate session deletion. |
| Type | Counter |
| Dimension |
|
| Example | - |
Table 9-78 audit_max_ttl_terminate_notify
| Field | Details |
|---|---|
| Description | Measures number of session terminate request sent due to Stale Session Deletion Request |
| Type | Counter |
| Dimension |
|
| Example | - |
Table 9-79 occnp_feature_info_received_total
| Field | Details |
|---|---|
| Description | Measures sessRuleReports and policyDecFailureReports in request and response. |
| Type | Counter |
| Dimension |
|
| Example | occnp_feature_info_received_total{application="pcf_smservice",hostname="sky8-pcf-smservice-75df58b555-srm7q",operationType="update",policyDecFailureReports="true",responseCode="",servicename3gpp="npcf-smpolicycontrol",sessRuleReports="false",} 2.0 occnp_feature_info_received_total{application="pcf_smservice",hostname="sky8-pcf-smservice-75df58b555-srm7q",operationType="update_notify",policyDecFailureReports="true",responseCode="200",servicename3gpp="npcf-smpolicycontrol",sessRuleReports="false",} 2.0 |
Table 9-80 error_handler_in_total
| Field | Details |
|---|---|
| Description | This metric is incremented on initialization of error handling. |
| Type | Counter |
| Dimensions |
|
| Example | occnp_error_handler_in_total{application="pcf_smservice",application_exception="HttpException",status="404",wrapped_exception="NotFound",} 18.0 |
Table 9-81 error_handler_exec_total
| Field | Details |
|---|---|
| Description | This metric is incremented on error handling performed by framework. |
| Type | Counter |
| Dimensions |
|
| Example | occnp_error_handler_exec_total{application="pcf_smservice",application_exception="JavaException",error_type="INTERNAL",operation="UPDATE",origin="JAVA",rule_name="REJECT_WITH_ENHANCED_DETAIL",source_interface="SMF",status="404",target_interface="POLICY",wrapped_exception="ServiceException",} 1.0 |
Table 9-82 error_handler_out_total
| Field | Details |
|---|---|
| Description | This metric is incremented on completion of error handling. |
| Type | Counter |
| Dimensions |
|
| Example | occnp_error_handler_out_total{application="pcf_smservice",application_exception="HttpException",error_resolved="false",status="423",wrapped_exception="HttpClientResponseException",} 4.0 |
Table 9-83 occnp_late_processing_rejection_total
| Field | Details |
|---|---|
| Description | This metric is pegged when stale requests cleanup functionality is enabled and the late processing found that a session has become stale. |
| Type | Counter |
| Dimensions |
|
| Example | occnp_late_processing_rejection_total': cause="timed_out_smf_request",servicename_3gpp="npcf-smpolicycontrol", stage="PRE_PDS" operation_type="create" |
Table 9-84 ocpm_late_arrival_rejection_total
| Field | Details |
|---|---|
| Description | This metric provides the number of requests rejected due to late arrival. |
| Type | Counter |
| Dimensions |
|
Table 9-85 jvm_memory_committed_bytes
| Field | Details |
|---|---|
| Description | The amount of memory in bytes that is committed for the Java virtual machine to use. |
| Type | Gauge |
| Dimensions |
|
| Example |
|
Table 9-86 jvm_threads_daemon_threads
| Field | Details |
|---|---|
| Description | The current number of live daemon threads. |
| Type | Gauge |
| Dimensions |
|
| Example | jvm_threads_daemon_threads{application="pcf_smservice",hostname="occnp-pcf-smservice-7d6c7bdcb8-zhxsh",} 14.0 |
Table 9-87 jvm_gc_pause_seconds_max
| Field | Details |
|---|---|
| Description | Time spent in Garbage Collector (GC) pause. |
| Type | Gauge |
| Dimensions |
|
| Example | jvm_gc_pause_seconds_max{action="end of minor GC",application="pcf_smservice",cause="G1 Evacuation Pause",gc="G1 Young Generation",hostname="occnp-pcf-smservice-7d6c7bdcb8-zhxsh",} 0.0 |
Table 9-88 jvm_buffer_count_buffers
| Field | Details |
|---|---|
| Description | An estimate of the number of buffers in the pool. |
| Type | Gauge |
| Dimensions |
|
| Example |
|
Table 9-89 jetty_client_request_size_max
| Field | Details |
|---|---|
| Description | Content sizes for Jetty HTTP client requests. |
| Type | Gauge |
| Dimensions |
|
| Example |
|
Table 9-90 jetty_client_request_size_sum
| Field | Details |
|---|---|
| Description | Content sizes for Jetty HTTP client requests. |
| Type | Summary |
| Dimensions |
|
| Example |
|
Table 9-91 jetty_client_request_size_count
| Field | Details |
|---|---|
| Description | Content sizes for Jetty HTTP client requests. |
| Type | Summary |
| Dimensions |
|
| Example |
|
Table 9-92 jvm_buffer_total_capacity_bytes
| Field | Details |
|---|---|
| Description | An estimate of the total capacity of the buffers in this pool. |
| Type | Gauge |
| Dimensions |
|
| Example |
|
Table 9-93 executor_seconds_max
| Field | Details |
|---|---|
| Description | Maximum executors in seconds. |
| Type | Gauge |
| Dimensions |
|
| Example |
|
Table 9-94 hikaricp_connections_usage_seconds_count
| Field | Details |
|---|---|
| Description | Connection usage time |
| Type | Summary |
| Dimensions |
|
| Example | hikaricp_connections_usage_seconds_count{application="pcf_smservice",hostname="occnp-pcf-smservice-7d6c7bdcb8-zhxsh",pool="HikariPool-1",} 763.0 |
Table 9-95 hikaricp_connections_usage_seconds_sum
| Field | Details |
|---|---|
| Description | Connection usage time |
| Type | Summary |
| Dimensions |
|
| Example | hikaricp_connections_usage_seconds_sum{application="pcf_smservice",hostname="occnp-pcf-smservice-7d6c7bdcb8-zhxsh",pool="HikariPool-1",} 4.867 |
Table 9-96 hikaricp_connections_usage_seconds_max
| Field | Details |
|---|---|
| Description | Connection usage time |
| Type | Gauge |
| Dimensions |
|
| Example | hikaricp_connections_usage_seconds_max{application="pcf_smservice",hostname="occnp-pcf-smservice-7d6c7bdcb8-zhxsh",pool="HikariPool-1",} 0.0 |
Table 9-97 http_server_requests_active_seconds_active_count
| Field | Details |
|---|---|
| Description | Active Server requests |
| Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-98 http_server_requests_active_seconds_duration_sum
| Field | Details |
|---|---|
| Description | Active Server requests |
| Type | Gauge |
| Dimensions |
|
| Example |
|
Table 9-99 system_cpu_count
| Field | Details |
|---|---|
| Description | The number of processors available to the Java virtual machine |
| Type | Gauge |
| Dimensions |
|
| Example | system_cpu_count{application="pcf_smservice",hostname="occnp-pcf-smservice-7d6c7bdcb8-zhxsh",} 2.0 |
Table 9-100 db_operations_total
| Field | Details |
|---|---|
| Description | Total database operations |
| Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-101 process_cpu_usage
| Field | Details |
|---|---|
| Description | The "recent cpu usage" for the Java Virtual Machine process. |
| Type | Gauge |
| Dimensions |
|
| Example | process_cpu_usage{application="pcf_smservice",hostname="occnp-pcf-smservice-7d6c7bdcb8-zhxsh",} 0.0 |
Table 9-102 occnp_suppress_notify_total
| Field | Details |
|---|---|
| Description | To measure the number of ASR not sent, ASR sent, and RAR sent when the feature is enabled. |
| Type | Counter |
| Dimensions |
|
| Example | occnp_suppress_notify_total{Action="deliver",ErrorCode="",ExceptionType="",MsgType="MSGTYPE_CREATE",SuppressionCause="ExceptionMismatch",application="pcf_smservice",hostname="titans-pcf-smservice-c7bc54fc7-xckwn",operationType="terminateNotify",} 1.0 |
Table 9-103 ocpm_handle_update_notify_timeout_as_pending_confirmation_total
| Field | Details |
|---|---|
| Description | This metric is incremented when SYSTEM.RX.UPDATE_NOTIFY.RULES.PENDING_CONFIRMATION.ENABLED flag is enabled enable and the response from SMF to PCF times out during update notify triggered by AAR-I and AAR-U. |
| Type | Counter |
| Dimensions |
|
| Example | {"instant":{"epochSecond":1742514782,"nanoOfSecond":805725000},"thread":"boundedElastic-1","level":"DEBUG","loggerName":"ocpm.pcf.service.sm.domain.component.metrics.SmMetrics","message":"Pegging Handle Update Notify timeout as Success metric, Operation Type: update_notify, Cause: Update Notify Time Out handled as PendingConfirmation","endOfBatch":false,"loggerFqcn":"org.apache.logging.slf4j.Log4jLogger","threadId":77,"threadPriority":5,"messageTimestamp":"2025-03-20T17:53:02.805-0600","ocLogId":"${ctx:ocLogId}"} |
Table 9-104 ocpm_handle_update_notify_error_response_as_pending_confirmation_total
| Field | Details |
|---|---|
| Description | This is incremented when configuration flag
SYSTEM.RX.UPDATE_NOTIFY.RULES.PENDING_CONFIRMATION.ENABLED
is enabled and specific error is added in
SYSTEM.RX.UPDATE_NOTIFY.RULES.PENDING_CONFIRMATION.RESPOMNSE_CODE
and configured response code received during update notify triggered
by AAR-I and AAR-U.
|
| Type | Counter |
| Dimensions |
|
| Example | ocpm_handle_update_notify_error_response_as_pending_confirmation_total{application="pcf_smservice",cause="Update Notify Error Response handled as Pending Confirmation",hostname="my-cnpolicy-pcf-smservice-7f7bcdb89-hhjbr",operationType="update_notify",responseCode="408",servicename3gpp="nf1stub.ch2-ns04.svc",} 4.0 |
Table 9-105 ocpm_process_pending_confirmation_rules_on_pa_update_total
| Field | Details |
|---|---|
| Description | This metric is incremented when rules as processed
during PA update based on pendingConfirmationAction
and flag
SYSTEM.RX.UPDATE_NOTIFY.RULES.PENDING_CONFIRMATION.PROCESS_ON_UPDATE
is enabled.
|
| Type | Counter |
| Dimensions |
|
| Example | ocpm_process_pending_confirmation_rules_on_pa_update_total{application="pcf_smservice",cause="Pending Confirmation rules processed on Pa Update",hostname="my-cnpolicy-pcf-smservice-7f7bcdb89-hhjbr",operationType="update_notify",servicename3gpp="nf1stub.ch2-ns04.svc",} 8.0 |
Table 9-106 ocpm_process_pending_configuration_rules_on_pa_delete_total
| Field | Details |
|---|---|
| Description | This metric is incremented when a rule with
pendingConfirmation flag as
true and pendingConfirmation
rules are sent in update notify triggered by STR.
|
| Type | Counter |
| Dimensions |
|
| Example | ocpm_process_pending_configuration_rules_on_pa_delete_total{application="pcf_smservice",cause="Pending Confirmation rules sent to delete on Pa Delete",hostname="my-cnpolicy-pcf-smservice-7f7bcdb89-hhjbr",operationType="update_notify",servicename3gpp="nf1stub.ch2-ns04.svc",} 16.0 |
Table 9-107 ocpm_rx_update_notify_request_total
| Field | Details |
|---|---|
| Description | This metric is incremented only if the update notify request is triggered by Rx and request is AAR-I or AAR-U. |
| Type | Counter |
| Dimensions |
|
| Example | ocpm_rx_update_notify_request_total{application="pcf_smservice",cause="Update Notify request triggered by Rx",hostname="my-cnpolicy-pcf-smservice-7f7bcdb89-hhjbr",operationType="update_notify",servicename3gpp="nf12stub.ch2-ns04.svc",} 24.0 |
Table 9-108 occnp_pds_location_info_notification_total
| Field | Details |
|---|---|
| Description | This metric gets incremented when SM core service gets notification from PDS to update PDS Location info in case of concurrency. |
| Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-109 occnp_optimized_smpolicyAssociation_lookup_query_total
| Field | Details |
|---|---|
| Description | This metric is incremented only when
ENABLE_N7_SESSION_LOOKUP_COOKIE advanced
settings key is enabled at SM service and Policy receives AAR-I with
custom AVP.
|
| Type | Counter |
| Dimensions |
|
| Examples |
occnp_optimized_smpolicyAssociation_lookup_query_total{MsgType="PA create",application="occnp",cause="IPV4 mismatch",status="failed",} 1.0 occnp_optimized_smpolicyAssociation_lookup_query_total{MsgType="PA create",application="occnp",cause="NA",status="success",} 1.0 |
Table 9-110 jvm_gc_overhead
| Field | Details |
|---|---|
| Description | An approximation of the percent of CPU time used by GC activities over the last lookback period or since monitoring began, whichever is shorter, in the range [0..1]. |
| Type | Gauge |
| Dimensions |
|
| Example | - |
Table 9-111 jvm_memory_usage_after_gc
| Field | Details |
|---|---|
| Description | The percentage of long-lived heap pool used after the last GC event, in the range [0..1]. |
| Type | Gauge |
| Dimensions |
|
| Example | jvm_memory_usage_after_gc{application="occnp",area="heap",pool="long-lived", |
Table 9-112 occnp_usr_loc_ch_supp_feat_in_sm_create_req_total
| Field | Details |
|---|---|
| Description | This metric provides the number of
SM Policy Create requests received from SMF with
AggregatedUELocChanges enabled.
Note: Invalid requests are rejected at the controller level and excluded from this count. This metric is
incremented when a given SM request (CREATE) contains
|
| Type | Counter |
| Dimensions |
|
| Example | occnp_usr_loc_ch_supp_feat_in_sm_create_req_total{application="pcf_smservice",cause="AggregatedUELocChanges",hostname="my-cnpolicy-pcf-smservice-79f9d6f89c-k7cmh",operationType="create",servicename3gpp=""} 8.0 |
Table 9-113 usr_loc_ch_sent_in_response
| Field | Details |
|---|---|
| Description | This metric provides the number of SM Policy Create
or Update responses sent by PCF with
USER_LOCATION_CH event.
This
metric is incremented when the feature
|
| Type | Counter |
| Dimensions |
|
| Example |
occnp_usr_loc_ch_in_update_notify_total{application="pcf_smservice",cause="USER_LOCATION_CH",hostname="my-cnpolicy-pcf-smservice-79f9d6f89c-k7cmh",operationType="update_notify",servicename3gpp=""} 14.0 occnp_usr_loc_ch_sent_in_response_total{application="pcf_smservice",cause="USER_LOCATION_CH",hostname="my-cnpolicy-pcf-smservice-79f9d6f89c-k7cmh",operationType="create",servicename3gpp=""} 3.0 occnp_usr_loc_ch_sent_in_response_total{application="pcf_smservice",cause="USER_LOCATION_CH",hostname="my-cnpolicy-pcf-smservice-79f9d6f89c-k7cmh",operationType="update",servicename3gpp=""} 1.0 |
Table 9-114 usr_loc_ch_in_update_notify
| Field | Details |
|---|---|
| Description | This metric provides the number of SM Policy Update
Notify requests sent by PCF with USER_LOCATION_CH
event.
This metric is incremented when the
feature |
| Type | Counter |
| Dimensions |
|
| Example | occnp_usr_loc_ch_in_update_notify_total{application="pcf_smservice",cause="USER_LOCATION_CH",hostname="my-cnpolicy-pcf-smservice-79f9d6f89c-k7cmh",operationType="update_notify",servicename3gpp=""} 14.0 |
Table 9-115 usr_loc_ch_in_sm_update
| Field | Details |
|---|---|
| Description | This metric provides the number of SM Policy Update
requests received from SMF with USER_LOCATION_CH
event.
This metric is incremented when the
feature |
| Type | Counter |
| Dimensions |
|
| Example | occnp_usr_loc_ch_in_sm_update_total{application="pcf_smservice",cause="USER_LOCATION_CH",hostname="my-cnpolicy-pcf-smservice-79f9d6f89c-k7cmh",operationType="update",servicename3gpp=""} 2.0 |
Table 9-116 occnp_enhanced_overload_reject_total
| Field | Details |
|---|---|
| Description | This metric is used to track reject action in SM
Service for N7, Diameter Rx and BSF Audit Notify Requests.
This is a counter metric which will be pegged when incoming request will be discarded by Overload Load Filter within pcf-sm service. Note: In case
of These dimensions are
populated only if DNN, S-NSSAI, or Service Urn based filtering
is configured, corresponding DNN, S-NSSAI, Service URN Message
Attributes are configured in GUI and matched message attribute
encoded in |
| Type | Counter |
| Dimensions |
|
| Example |
occnp_enhanced_overload_reject_total{application="pcf_smservice",dnn="internet",hostname="pcf-pcf-smservice-787c59b54f-qw7xg",interfaceType="Npcf_SMPolicyControl",loadLevel="1",operationType="Create",serviceUrn="",snssai="1-000007"} 20786.0 |
Table 9-117 occnp_service_load_level
| Field | Details |
|---|---|
| Description | This metric is used to track Load level changes with
in SM Service.
This metric may not be changed for each polling response, If response is from non-leader pod and will be dependent on nonLeaderPodSampleCount. |
| Type | Gauge |
| Dimensions |
|
| Example | occnp_service_load_level{application="pcf_smservice",hostname="pcf-pcf-smservice-787c59b54f-qw7xg"} 1.0 |
Table 9-118 occnp_load_level_polling_request_total
| Field | Details |
|---|---|
| Description | This metric is used to track load level requests.
It provides the count of requests sent to perf-info. |
| Type | Counter |
| Dimensions |
|
| Example | occnp_load_level_polling_request_total{application="pcf_smservice",hostname="pcf-pcf-smservice-787c59b54f-qw7xg"} 264238.0 |
Table 9-119 occnp_load_level_polling_response_total
| Field | Details |
|---|---|
| Description | This metric is used to track load level responses.
It provides the count of responses received from perf-info. |
| Type | Counter |
| Dimensions |
|
| Example |
occnp_load_level_polling_response_total{application="pcf_smservice",hostname="pcf-pcf-smservice-787c59b54f-qw7xg",responseCode="200"} 48822.0 occnp_load_level_polling_response_total{application="pcf_smservice",hostname="pcf-pcf-smservice-787c59b54f-qw7xg",responseCode="500"} 97746.0 occnp_load_level_polling_response_total{application="pcf_smservice",hostname="pcf-pcf-smservice-787c59b54f-qw7xg",responseCode="503"} 117670.0 |
Table 9-120 occnp_load_level_polling_exception_total
| Field | Details |
|---|---|
| Description | This metric is used to track load level polling
exceptions.
It provides the count of exceptions (e.g. TimeoutException) occurred while sending request. |
| Type | Counter |
| Dimensions |
|
| Example | occnp_load_level_polling_exception_total{application="pcf_smservice",hostname="pcf-pcf-smservice-69c7578d6-vrmfb"} 96.0 |
Table 9-121 occnp_polled_load_level_total
| Field | Details |
|---|---|
| Description | This metric is used to track polled load level.
This metric pegged in case of success response with all the details of the response like isLeader, loadLevel, serviceName. |
| Type | Counter |
| Dimensions |
|
| Example |
occnp_polled_load_level_total{application="pcf_smservice",hostname="pcf-pcf-smservice-787c59b54f-qw7xg",isLeader="false",loadLevel="L0",serviceName="pcf-occnp-pcf-sm"} 9501.0 occnp_polled_load_level_total{application="pcf_smservice",hostname="pcf-pcf-smservice-787c59b54f-qw7xg",isLeader="false",loadLevel="L1",serviceName="pcf-occnp-pcf-sm"} 6534.0 occnp_polled_load_level_total{application="pcf_smservice",hostname="pcf-pcf-smservice-787c59b54f-qw7xg",isLeader="false",loadLevel="L2",serviceName="pcf-occnp-pcf-sm"} 1565.0 occnp_polled_load_level_total{application="pcf_smservice",hostname="pcf-pcf-smservice-787c59b54f-qw7xg",isLeader="false",loadLevel="L3",serviceName="pcf-occnp-pcf-sm"} 6796.0 occnp_polled_load_level_total{application="pcf_smservice",hostname="pcf-pcf-smservice-787c59b54f-qw7xg",isLeader="true",loadLevel="L0",serviceName="pcf-occnp-pcf-sm"} 9554.0 occnp_polled_load_level_total{application="pcf_smservice",hostname="pcf-pcf-smservice-787c59b54f-qw7xg",isLeader="true",loadLevel="L1",serviceName="pcf-occnp-pcf-sm"} 6510.0 occnp_polled_load_level_total{application="pcf_smservice",hostname="pcf-pcf-smservice-787c59b54f-qw7xg",isLeader="true",loadLevel="L2",serviceName="pcf-occnp-pcf-sm"} 1551.0 occnp_polled_load_level_total{application="pcf_smservice",hostname="pcf-pcf-smservice-787c59b54f-qw7xg",isLeader="true",loadLevel="L3",serviceName="pcf-occnp-pcf-sm"} 6811.0 |
Table 9-122 occnp_pending_binding_site_takeover
| Field | Details |
|---|---|
| Description | This metric provides the current count of pending site takeover operations. |
| Type | Gauge |
| Dimensions |
|
| Example | occnp_pending_binding_site_takeover_total{application="pcf_smservice",hostname="pcf-pcf-smservice-7fdd6f6797-c4pzd",} 1.0 |
Table 9-123 occnp_enhanced_overload_ssv_update_skipped_total
| Field | Details |
|---|---|
| Description |
This is a counter metric which is pegged when SSV UPDATE operation to PDS is skipped due to applicable Enhanced overload assume positive restriction on User data. |
| Type | Counter |
| Dimensions |
|
| Example | {interfaceType="Npcf_SMPolicyControl",operationType="Create" ,dnn="dnn1",snssai="11-abc123") |
Table 9-124 occnp_enhanced_overload_service_interaction_total
| Field | Details |
|---|---|
| Description |
This metric increments once for each incoming request when an SM-related request is subjected to an Assume Positive restriction by the Overload Load Filter within the pcf-sm service. |
| Type | Counter |
| Dimensions |
Service interaction dimensions mentioned above is an indication of the restriction configured in the mapped overload rule. A value of ‘false’ ensures that no interaction was performed with the respective service (UserData, SpendingLimit, or PolicyEvaluation), while a value of ‘true’ indicates that no restriction was applied due to overload handling. However, a value of ‘true’ does not guarantee that an interaction actually occurred, as other processes or features besides Enhanced Overload may have blocked the interaction. One of the example feature is the 'Exclude DNN' feature which can stop User Data interaction for a particular DNN. |
| Example |
{interfaceType="Npcf_SMPolicyControl",operationType="Create" ,loadLevel="1",dnn="dnn1",snssai="11-abc123",userData=true,spendingLimitData=false,policyEvaluation=true} |
Table 9-125 occnp_sm_qosmon_update_notify_sent_total
| Field | Description |
|---|---|
| Description | This metric is incremented when PCF sends an updateNotify request to SMF with QoS Monitoring subscription. |
| Metric Type | Counter |
| Dimensions |
|
| Examples | occnp_sm_qosmon_update_notify_sent_total(repFreq="EVENT_TRIGGERED", notifTarget="AF_NEF") |
Table 9-126 occnp_sm_qosmon_decs_error_total
| Field | Description |
|---|---|
| Description | This metric is incremented when PCF receives QOS_MON_DECS_ERR as PolicyDecisionFailureCode to the updateNotify requests or when PCF receives a Npcf_SMPolicyControl_Update requests received from SMF with QOS_MON_DECS_ERR as PolicyDecisionFailureCode for Policy decision failures |
| Metric Type | Counter |
| Dimensions |
|
| Examples | occnp_sm_qosmon_decs_error_total{application="pcf_smservice",hostname="my-cnpolicy-pcf-smservice-858595cbdc-t8vgx",operation_type="update",policyDecsFailureCode="QOS_MON_DECS_ERR",response_code=""} 1.0
occnp_sm_qosmon_decs_error_total{application="pcf_smservice",hostname="my-cnpolicy-pcf-smservice-858595cbdc-t8vgx",operation_type="update_notify",policyDecsFailureCode="QOS_MON_DECS_ERR",response_code="200"} 1.0 |
For more information about Dimensions, see CNC Policy Metrics.
9.6 AM Service Metrics
The following table describes the AM Service metrics and respective dimensions:
Table 9-127 ocpm_ingress_request_total
| Field | Details |
|---|---|
| Description | Total number of ingress requests received. |
| Metric Type | Counter |
| Dimensions |
|
| Example |
:
|
Table 9-128 ocpm_ingress_response_total
| Field | Details |
|---|---|
| Description | Total number of ingress responses. |
| Metric Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-129 ocpm_egress_request_total
| Field | Details |
|---|---|
| Description | Total number of egress requests received. |
| Metric Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-130 ocpm_egress_response_total
| Field | Details |
|---|---|
| Description | Total number of egress responses. |
| Metric Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-131 am_audit_update_notify_sent_total
| Field | Details |
|---|---|
| Description | Total number of audit notifications sent. |
| Metric Type | Counter |
| Dimensions |
Request |
| Example |
|
Table 9-132 am_audit_update_notify_session_not_found_total
| Field | Details |
|---|---|
| Description | Total number of 'session not found' notifications. |
| Metric Type | Counter |
| Dimensions |
Request |
| Example |
|
Table 9-133 am_audit_update_notify_session_found_total
| Field | Details |
|---|---|
| Description | Total number of 'session found' notifications. |
| Metric Type | Counter |
| Dimensions |
Request |
| Example |
|
Table 9-134 am_audit_update_timestamp_cnt_total
| Field | Details |
|---|---|
| Description | Total number of timestamp count for audit requests. |
| Metric Type | Counter |
| Dimensions |
Request |
| Example |
|
Table 9-135 am_audit_delete_records_count_total
| Field | Details |
|---|---|
| Description | Total number of delete audit records requests |
| Metric Type | Counter |
| Dimensions |
Request |
| Example |
|
Table 9-136 am_audit_delete_records_max_ttl_count_total
| Field | Details |
|---|---|
| Description | Number of records deleted by AM service when the max TTL was reached. |
| Metric Type | Counter |
| Dimensions |
Request |
| Example |
|
Table 9-137 am_audit_amf_query_total
| Field | Details |
|---|---|
| Description | - |
| Metric Type | Counter |
| Dimensions |
Request |
| Example |
|
Table 9-138 am_audit_update_notify_response_error_total
| Field | Details |
|---|---|
| Description | Number of update notify requests sent to AMF by AM service that were responded with an error code. |
| Metric Type | Counter |
| Dimensions |
Request |
| Example |
|
Table 9-139 session_oam_request_total
| Field | Details |
|---|---|
| Description | Number of session requests for AM Service |
| Metric Type | Request |
| Dimensions |
|
Table 9-140 session_oam_response_total
| Field | Details |
|---|---|
| Description | Number of session responses for AM Service |
| Metric Type | Response |
| Dimensions |
|
Table 9-141 session_info_request_total
| Field | Details |
|---|---|
| Description | Total number of sessions to be deleted as requested by the AM Service |
| Metric Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-142 occnp_lease_duration_seconds_bucket
| Field | Details |
|---|---|
| Description | Time in seconds for which AM Service holds the lock |
| Metric Type | Histogram |
| Dimensions |
|
Table 9-143 session_info_response_total
| Field | Details |
|---|---|
| Description | Total number of sessions deleted as requested by the AM Service |
| Metric Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-144 http_out_conn_request_total
| Field | Details |
|---|---|
| Description | Total number of connection requests received |
| Metric Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-145 http_out_conn_response_total
| Field | Details |
|---|---|
| Description | Total number of connection response sent |
| Metric Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-146 ocpm_ar_request_total
| Field | Details |
|---|---|
| Description | Total number of ar requests received |
| Metric Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-147 ocpm_ar_response_total
| Field | Details |
|---|---|
| Description | Total number of ar response sent |
| Metric Type | Counter |
| Dimensions |
|
Table 9-148 occnp_http_in_conn_response_total
| Field | Details |
|---|---|
| Description | Number of http responses for AM Service |
| Metric Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-149 http_bulwark_lock_request_total
| Field | Details |
|---|---|
| Description | Number of bulwark lock requests |
| Metric Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-150 http_bulwark_unlock_request_total
| Field | Details |
|---|---|
| Description | Number of bulwark unlock requests |
| Metric Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-151 http_bulwark_lock_response_total
| Field | Details |
|---|---|
| Description | Number of bulwark lock responses |
| Metric Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-152 http_bulwark_lock_request_retry_total
| Field | Details |
|---|---|
| Description | Number of bulwark lock request retries |
| Metric Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-153 http_bulwark_unlock_request_retry_total
| Field | Details |
|---|---|
| Description | Number of bulwark unlock request retries |
| Metric Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-154 occnp_http_out_conn_request_total
| Field | Details |
|---|---|
| Description | Number of http requestd for AM Service |
| Metric Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-155 topic_version
| Field | Details |
|---|---|
| Description | Describes the current applied version of a given topic (mentioned in dimension topic_name) into the pod. |
| Metric Type | Gauge |
| Dimensions |
|
Table 9-156 occnp_db_overall_processing_time_seconds_count
| Field | Details |
|---|---|
| Description | This metric is incremented when PCF performs GET, INSERT, UPDATE, and DELETE operation on an Association |
| Metric Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-157 occnp_db_overall_processing_time_seconds_sum
| Field | Details |
|---|---|
| Description | This metric is incremented when PCF performs DELETE operation on an Association |
| Metric Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-158 occnp_db_overall_processing_time_seconds_sum
| Field | Details |
|---|---|
| Description | This metric is incremented when PCF performs DELETE operation on an Association |
| Metric Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-159 occnp_amservice_overall_processing_time_seconds_max
| Field | Details |
|---|---|
| Description |
This metric is incremented for AM service to calculate processing's duration of HTTP request arrived on rest controller. Note: occnp_amservice_overall_processing_time_seconds_max metric replaces http_server_requests_seconds_max. |
| Metric Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-160 occnp_amservice_overall_processing_time_seconds_sum
| Field | Details |
|---|---|
| Description |
This metric is incremented for AM service to calculate processing's duration of HTTP request arrived on rest controller. Note: occnp_amservice_overall_processing_time_seconds_sum metric replaces http_server_requests_seconds_sum. |
| Metric Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-161 occnp_amervice_overall_processing_time_seconds_count
| Field | Details |
|---|---|
| Description |
This metric is incremented for AM service to calculate processing's duration of HTTP request arrived on rest controller. Note: occnp_amservice_overall_processing_time_seconds_count metric replaces http_server_requests_seconds_count. |
| Metric Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-162 error_handler_in_total
| Field | Details |
|---|---|
| Description | This metric is incremented on initialization of error handling. |
| Type | Counter |
| Dimensions |
|
| Example | occnp_error_handler_in_total{application="pcf_amservice",application_exception="HttpException",status="404",wrapped_exception="NotFound",} 1.0 |
Table 9-163 error_handler_exec_total
| Field | Details |
|---|---|
| Description | This metric is incremented on error handling performed by framework. |
| Type | Counter |
| Dimensions |
|
| Example | occnp_error_handler_exec_total{application="pcf_amservice",application_exception="JavaException",error_type="INTERNAL",operation="CREATE",origin="JAVA",rule_name="REJECT_WITH_ENHANCED_DETAIL",source_interface="AMF",status="400",target_interface="POLICY",wrapped_exception="ServiceException",} 2.0 |
Table 9-164 error_handler_out_total
| Field | Details |
|---|---|
| Description | This metric is incremented on completion of error handling. |
| Type | Counter |
| Dimensions |
|
| Example | occnp_error_handler_out_total{application="pcf_amservice",application_exception="HttpException",error_resolved="false",status="404",wrapped_exception="NotFound",} 1.0 |
Table 9-165 occnp_policy_retry_exhausted_total
| Field | Details |
|---|---|
| Description | This metric is incremented when AM service to PRE
service interaction is retried (for resiliency) and exhausted due to
the below factors:
|
| Type | Counter |
| Dimensions |
|
| Example | occnp_policy_retry_exhausted_total {app_kubernetes_io_instance="my-cnpolicy", app_kubernetes_io_managed_by="Helm", app_kubernetes_io_name="am-service", app_kubernetes_io_part_of="occnp", app_kubernetes_io_version="1.0.0", application="occnp", container="am-service", endpoint="cnc-metrics", engVersion="24.2.0-rc.7", exported_application="pcf_amservice", helm_sh_chart="am-service-24.2.0-rc.7", hostname="my-cnpolicy-pcf-amservice-54db5bfdf8-cphjm", instance="10.233.127.9:9000", io_kompose_service="my-cnpolicy-pcf-amservice", job="occne-infra/occne-nf-cnc-podmonitor", microservice="occnp_pcf_am", mktgVersion="1.0.0", namespace="hi-manim", operation_type="create", pod="my-cnpolicy-pcf-amservice-54db5bfdf8-cphjm", pod_template_hash="54db5bfdf8", vendor="Oracle"} |
Table 9-166 occnp_pds_location_info_notification_total
| Field | Details |
|---|---|
| Description | This metric gets incremented when AM core service gets notification from PDS to update PDS Location info in case of concurrency. |
| Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-167 dnn_replacement_total
| Field | Details |
|---|---|
| Description | This metric gets incremented for AM Create and AM Updated when DNN replacement feature is negotiated successfully between the AMF and PCF network functions. |
| Type | Counter |
| Dimensions |
|
| Example |
{application="pcf_amservice",candidate_for_replacement_sent="false",hostname="sm-pcf-amservice-7c8d6c9b44-9lnr8",incoming_dnn="",incoming_snssai="",operation_type="create",smf_select_ch_received="false",unsup p_dnn_sent="false"} {application="pcf_amservice",candidate_for_replacement_sent="false",hostname="sm-pcf-amservice-7c8d6c9b44-9lnr8",incoming_dnn="",incoming_snssai="",operation_type="create",smf_select_ch_received="false",unsup p_dnn_sent="true"} {application="pcf_amservice",candidate_for_replacement_sent="true",hostname="sm-pcf-amservice-7c8d6c9b44-9lnr8",incoming_dnn="",incoming_snssai="",operation_type="create",smf_select_ch_received="false",unsupp _dnn_sent="true"} |
For more information about Dimensions, see CNC Policy Metrics.
9.7 CM Service Metrics
The following table describes the CM Service metrics and respective dimensions:
Table 9-168 system_operational_state
| Field | Details |
|---|---|
| Description | This metric indicates the current operational state |
| Metric Type | Gauge |
| Dimensions |
|
For more information about Dimensions, see CNC Policy Metrics.
Examples
- system_operational_state{application="config-server",eng_version="",microservice="",namespace="",node="",pod="occnp-config-mgmt",vendor="oracle",} 1.0
Table 9-169 data_repository_invocations_seconds_max
| Field | Details |
|---|---|
| Description | This metric is used to track the maximum execution time of Data repository invocations. It is a useful metric for monitoring the performance of data repositories and identifying slow-running queries. |
| Type | Gauge |
| Dimension |
|
| Example | data_repository_invocations_seconds_max{app_kubernetes_io_instance="ocbsf", app_kubernetes_io_managed_by="Helm", app_kubernetes_io_name="audit-service", app_kubernetes_io_part_of="ocbsf", app_kubernetes_io_version="1.0.0.0", application="ocbsf", container="audit-service", endpoint="cnc-metrics", engVersion="24.1.4", exception="None", helm_sh_chart="audit-service-24.1.4", instance="10.233.127.211:9000", io_kompose_service="ocbsf-ocpm-audit-service", job="occne-infra/occne-nf-cnc-podmonitor", method="getQueuedTablesToAudit", microservice="ocbsf-audit", mktgVersion="1.0.0.0", namespace="ocbsf", pod="ocbsf-ocpm-audit-service-6b6f85f7b9-nmzr4", pod_template_hash="6b6f85f7b9", repository="AuditSchedulerRepository", security_istio_io_tlsMode="istio", service_istio_io_canonical_name="audit-service", service_istio_io_canonical_revision="1.0.0.0", state="SUCCESS", vendor="Oracle"} |
Table 9-170 data_repository_invocations_seconds_sum
| Field | Details |
|---|---|
| Description |
The seconds_sum metric for Data repository invocations is a measure of the total time spent executing repository methods. |
| Type | Gauge |
| Dimension |
|
| Example | data_repository_invocations_seconds_sum{app_kubernetes_io_instance="ocbsf", app_kubernetes_io_managed_by="Helm", app_kubernetes_io_name="audit-service", app_kubernetes_io_part_of="ocbsf", app_kubernetes_io_version="1.0.0.0", application="ocbsf", container="audit-service", endpoint="cnc-metrics", engVersion="24.1.4", exception="None", helm_sh_chart="audit-service-24.1.4", instance="10.233.84.88:9000", io_kompose_service="ocbsf-ocpm-audit-service", job="occne-infra/occne-nf-cnc-podmonitor", method="getQueuedTablesToAudit", microservice="ocbsf-audit", mktgVersion="1.0.0.0", namespace="ocbsf", pod="ocbsf-ocpm-audit-service-6b6f85f7b9-nshv9", pod_template_hash="6b6f85f7b9", repository="AuditSchedulerRepository", security_istio_io_tlsMode="istio", service_istio_io_canonical_name="audit-service", service_istio_io_canonical_revision="1.0.0.0", state="SUCCESS", vendor="Oracle"} |
Table 9-171 data_repository_invocations_seconds_count
| Field | Details |
|---|---|
| Description |
This metric measures the total time spent in Data JPA repository invocations. It is a counter metric, which means that it increments each time a repository method is invoked. The metric is reported in seconds. |
| Type | Counter |
| Dimension |
|
| Example | data_repository_invocations_seconds_count{app_kubernetes_io_instance="ocbsf", app_kubernetes_io_managed_by="Helm", app_kubernetes_io_name="audit-service", app_kubernetes_io_part_of="ocbsf", app_kubernetes_io_version="1.0.0.0", application="ocbsf", container="audit-service", endpoint="cnc-metrics", engVersion="24.1.4", exception="None", helm_sh_chart="audit-service-24.1.4", instance="10.233.127.211:9000", io_kompose_service="ocbsf-ocpm-audit-service", job="occne-infra/occne-nf-cnc-podmonitor", method="findAll", microservice="ocbsf-audit", mktgVersion="1.0.0.0", namespace="ocbsf", pod="ocbsf-ocpm-audit-service-6b6f85f7b9-nmzr4", pod_template_hash="6b6f85f7b9", repository="AuditRegistrationsRepository", security_istio_io_tlsMode="istio", service_istio_io_canonical_name="audit-service", service_istio_io_canonical_revision="1.0.0.0", state="SUCCESS", vendor="Oracle"} |
9.8 PA Service Metrics
The following table describes the PA Service metrics and respective dimensions:
Table 9-172 ocpm_ingress_request_total
| Field | Details |
|---|---|
| Description | Total number of ingress requests received. |
| Metric Type | Counter |
| Dimensions |
|
- ocpm_ingress_request_total{application="pcf_smservice",dnn="dnn1",nf_instance_id="",operation_type="create",sbi_priority="",servicename_3gpp="npcf-policyauthorization",snssai="11-abc123",} 1.0 ; Type-Counter
- ocpm_ingress_request_total{application="pcf_smservice",dnn="dnn1",nf_instance_id="",operation_type="update",sbi_priority="",servicename_3gpp="npcf-policyauthorization",snssai="11-abc123",} 1.0 ; Type-Counter
- ocpm_ingress_request_total{application="pcf_smservice",dnn="dnn1",nf_instance_id="",operation_type="delete",sbi_priority="",servicename_3gpp="npcf-policyauthorization",snssai="11-abc123",} 1.0 ; Type-Counter
- ocpm_ingress_request_total{application="pcf_smservice",dnn="dnn1",nf_instance_id="",operation_type="get",sbi_priority="",servicename_3gpp="npcf-policyauthorization",snssai="11-abc123",} 1.0 ; Type-Counter
Table 9-173 ocpm_ingress_response_total
| Field | Details |
|---|---|
| Description | Total number of ingress responses. |
| Metric Type | Counter |
| Dimensions |
|
- ocpm_ingress_response_total{application="pcf_smservice",dnn="dnn1",nf_instance_id="",operation_type="create",response_code="2xx",sbi_priority="",servicename_3gpp="npcf-policyauthorization",snssai="11-abc123",} 1.0 ; Type-Counter
- ocpm_ingress_response_total{application="pcf_smservice",dnn="dnn1",nf_instance_id="",operation_type="update",response_code="2xx",sbi_priority="",servicename_3gpp="npcf-policyauthorization",snssai="11-abc123",binding_level="", binding_id=""} 1.0 ; Type-Counter
- ocpm_ingress_response_total{application="pcf_smservice",dnn="dnn1",nf_instance_id="",operation_type="delete",response_code="4xx",sbi_priority="",servicename_3gpp="npcf-policyauthorization",snssai="11-abc123",binding_level="", binding_id=""} 1.0 ; Type-Counter
- ocpm_ingress_response_total{application="pcf_smservice",dnn="dnn1",nf_instance_id="",operation_type="get",response_code="2xx",sbi_priority="",servicename_3gpp="npcf-policyauthorization",snssai="11-abc123",binding_level="", binding_id=""} 1.0 ; Type-Counter
Table 9-174 remote_delete_notify_total
| Field | Details |
|---|---|
| Description | Total number of delete requests. |
| Metric Type | Counter |
| Dimensions |
|
- remote_delete_notify_total{Code="2xx",Request="DeleteNotify",SessionType="PA",application="pcf_smservice",hostname="4dfc2dfc25da",} 0.0
- remote_delete_notify_total{Code="4xx",Request="DeleteNotify",SessionType="PA",application="pcf_smservice",hostname="4dfc2dfc25da",} 0.0
- remote_delete_notify_total{Code="5xx",Request="DeleteNotify",SessionType="PA",application="pcf_smservice",hostname="4dfc2dfc25da",} 0.0
- remote_delete_notify_total{Code="N/A",Request="EmulateDelete",SessionType="PA",application="pcf_smservice",hostname="4dfc2dfc25da",} 0.0
Table 9-175 session_oam_request_total
| Field | Details |
|---|---|
| Description | Number of session requests for PA Service |
| Metric Type | Request |
| Dimensions |
|
Table 9-176 session_oam_response_total
| Field | Details |
|---|---|
| Description | Number of session responses for PA Service |
| Metric Type | Response |
| Dimensions |
|
Table 9-177 occnp_pa_sponsored_sessions_total
| Field | Details |
|---|---|
| Description |
This metric is incremented when PCF responds to AF for sponsored sessions, irrespective of whether the request is processed successfully or rejected during the request evaluation. The value of the Note: This metric is pegged if a local delete is triggered because the AF does not send PA Delete on receiving terminate_notify from PCF within 3 seconds. |
| Metric Type | Counter |
| Dimensions |
|
| Example |
occnp_pa_sponsored_sessions_total{application="pcf_smservice",aspId="",cause="",hostname="ocpcf-pcf-smservice-5dc7b7dfb5-kzclr",operationType="CREATE",responseCode="201",sponId="",sponStatus="SPONSOR_DISABLED",umcDataIncluded="false"} 1.0 occnp_pa_sponsored_sessions_total{application="pcf_smservice",aspId="",cause="MANDATORY_IE_MISSING",hostname="ocpcf-pcf-smservice-5dc7b7dfb5-kzclr",operationType="CREATE",responseCode="400",sponId="",sponStatus="SPONSOR_DISABLED",umcDataIncluded="false"} 2.0 occnp_pa_sponsored_sessions_total{application="pcf_smservice",aspId="test109test",cause="",hostname="ocpcf-pcf-smservice-5dc7b7dfb5-kzclr",operationType="CREATE",responseCode="201",sponId="test109test",sponStatus="SPONSOR_ENABLED",umcDataIncluded="false"} 20.0 occnp_pa_sponsored_sessions_total{application="pcf_smservice",aspId="test109test",cause="",hostname="ocpcf-pcf-smservice-5dc7b7dfb5-kzclr",operationType="DELETE",responseCode="204",sponId="test109test",sponStatus="SPONSOR_DISABLED",umcDataIncluded="false"} 1.0 occnp_pa_sponsored_sessions_total{application="pcf_smservice",aspId="test109test",cause="",hostname="ocpcf-pcf-smservice-5dc7b7dfb5-kzclr",operationType="DELETE",responseCode="204",sponId="test109test",sponStatus="SPONSOR_ENABLED",umcDataIncluded="false"} 9.0 occnp_pa_sponsored_sessions_total{application="pcf_smservice",aspId="test109test",cause="",hostname="ocpcf-pcf-smservice-5dc7b7dfb5-kzclr",operationType="MODIFY",responseCode="204",sponId="test109test",sponStatus="SPONSOR_DISABLED",umcDataIncluded="true"} 1.0 occnp_pa_sponsored_sessions_total{application="pcf_smservice",aspId="test109test",cause="",hostname="ocpcf-pcf-smservice-5dc7b7dfb5-kzclr",operationType="MODIFY",responseCode="204",sponId="test109test",sponStatus="SPONSOR_ENABLED",umcDataIncluded="true"} 7.0 occnp_pa_sponsored_sessions_total{application="pcf_smservice",aspId="test110R",cause="",hostname="ocpcf-pcf-smservice-5dc7b7dfb5-kzclr",operationType="CREATE",responseCode="201",sponId="test110R",sponStatus="SPONSOR_ENABLED",umcDataIncluded="false"} 3.0 occnp_pa_sponsored_sessions_total{application="pcf_smservice",aspId="test110test",cause="",hostname="ocpcf-pcf-smservice-5dc7b7dfb5-kzclr",operationType="CREATE",responseCode="201",sponId="test110test",sponStatus="SPONSOR_ENABLED",umcDataIncluded="false"} 1.0 occnp_pa_sponsored_sessions_total{application="pcf_smservice",aspId="test110test",cause="",hostname="ocpcf-pcf-smservice-5dc7b7dfb5-kzclr",operationType="DELETE",responseCode="204",sponId="test110test",sponStatus="SPONSOR_DISABLED",umcDataIncluded="false"} 1.0 occnp_pa_sponsored_sessions_total{application="pcf_smservice",aspId="test110test",cause="",hostname="ocpcf-pcf-smservice-5dc7b7dfb5-kzclr",operationType="MODIFY",responseCode="204",sponId="test110test",sponStatus="SPONSOR_DISABLED",umcDataIncluded="true"} 1.0 |
Table 9-178 occnp_pa_sponsored_session_update_notify_total
| Field | Details |
|---|---|
| Description |
This metric is incremented when PCF receives a response from SMF. It is counted exclusively for sponsored sessions. This metric is not counted for update_notify during a normal flow. The value of the Note: terminate_notify will not be considered, since it only goes to AF. |
| Metric Type | Counter |
| Dimensions |
|
| Example |
occnp_pa_sponsored_session_update_notify_total{application="pcf_smservice",aspId="NotSpecified",cause="",hostname="ocpcf-pcf-smservice-844b694f98-9cgh8",operationTypeN5="CREATE",responseCode="204",servicename3gpp="npcf-smpolicycontrol",sponId="NotSpecified",sponStatus="SPONSOR_DISABLED",umcDataIncluded="false"} 7.0 occnp_pa_sponsored_session_update_notify_total{application="pcf_smservice",aspId="NotSpecified",cause="",hostname="ocpcf-pcf-smservice-844b694f98-9cgh8",operationTypeN5="CREATE",responseCode="204",servicename3gpp="npcf-smpolicycontrol",sponId="NotSpecified",sponStatus="SPONSOR_ENABLED",umcDataIncluded="false"} 10.0 occnp_pa_sponsored_session_update_notify_total{application="pcf_smservice",aspId="NotSpecified",cause="",hostname="ocpcf-pcf-smservice-844b694f98-9cgh8",operationTypeN5="CREATE",responseCode="204",servicename3gpp="npcf-smpolicycontrol",sponId="NotSpecified",sponStatus="SPONSOR_ENABLED",umcDataIncluded="true"} 20.0 occnp_pa_sponsored_session_update_notify_total{application="pcf_smservice",aspId="NotSpecified",cause="",hostname="ocpcf-pcf-smservice-844b694f98-9cgh8",operationTypeN5="CREATE",responseCode="500",servicename3gpp="npcf-smpolicycontrol",sponId="NotSpecified",sponStatus="SPONSOR_ENABLED",umcDataIncluded="false"} 2.0 occnp_pa_sponsored_session_update_notify_total{application="pcf_smservice",aspId="NotSpecified",cause="",hostname="ocpcf-pcf-smservice-844b694f98-9cgh8",operationTypeN5="CREATE",responseCode="500",servicename3gpp="npcf-smpolicycontrol",sponId="NotSpecified",sponStatus="SPONSOR_ENABLED",umcDataIncluded="true"} 1.0 occnp_pa_sponsored_session_update_notify_total{application="pcf_smservice",aspId="NotSpecified",cause="",hostname="ocpcf-pcf-smservice-844b694f98-9cgh8",operationTypeN5="DELETE",responseCode="204",servicename3gpp="npcf-smpolicycontrol",sponId="NotSpecified",sponStatus="SPONSOR_DISABLED",umcDataIncluded="false"} 7.0 occnp_pa_sponsored_session_update_notify_total{application="pcf_smservice",aspId="NotSpecified",cause="",hostname="ocpcf-pcf-smservice-844b694f98-9cgh8",operationTypeN5="DELETE",responseCode="204",servicename3gpp="npcf-smpolicycontrol",sponId="NotSpecified",sponStatus="SPONSOR_ENABLED",umcDataIncluded="false"} 30.0 occnp_pa_sponsored_session_update_notify_total{application="pcf_smservice",aspId="NotSpecified",cause="",hostname="ocpcf-pcf-smservice-844b694f98-9cgh8",operationTypeN5="MODIFY",responseCode="204",servicename3gpp="npcf-smpolicycontrol",sponId="NotSpecified",sponStatus="SPONSOR_DISABLED",umcDataIncluded="false"} 5.0 occnp_pa_sponsored_session_update_notify_total{application="pcf_smservice",aspId="NotSpecified",cause="",hostname="ocpcf-pcf-smservice-844b694f98-9cgh8",operationTypeN5="MODIFY",responseCode="204",servicename3gpp="npcf-smpolicycontrol",sponId="NotSpecified",sponStatus="SPONSOR_ENABLED",umcDataIncluded="false"} 27.0 occnp_pa_sponsored_session_update_notify_total{application="pcf_smservice",aspId="NotSpecified",cause="",hostname="ocpcf-pcf-smservice-844b694f98-9cgh8",operationTypeN5="MODIFY",responseCode="500",servicename3gpp="npcf-smpolicycontrol",sponId="NotSpecified",sponStatus="SPONSOR_DISABLED",umcDataIncluded="false"} 2.0 occnp_pa_sponsored_session_update_notify_total{application="pcf_smservice",aspId="NotSpecified",cause="",hostname="ocpcf-pcf-smservice-844b694f98-9cgh8",operationTypeN5="MODIFY",responseCode="500",servicename3gpp="npcf-smpolicycontrol",sponId="NotSpecified",sponStatus="SPONSOR_ENABLED",umcDataIncluded="false"} 1.0 |
Table 9-179 occnp_pa_qosmon_request_total
| Field | Description |
|---|---|
| Description | This metric is incremented when PCF receives requests from AF/NEF with subscription to QoS Monitoring. |
| Metric Type | Counter |
| Dimensions |
|
| Examples | occnp_pa_qosmon_request_total(notificationMethod="EVENT_DETECTION", operationType="CREATE", incompleteQosMonAttr="false") |
Table 9-180 occnp_pa_qosmon_response_total
| Field | Description |
|---|---|
| Description | This metric is incremented when PCF replies to requests from AF/NEF with subscription to Qos Monitoring |
| Metric Type | Counter |
| Dimensions |
|
| Examples | occnp_pa_qosmon_response_total(operation_type="CREATE", response_code="201") |
For more information about Dimensions, see CNC Policy Metrics.
9.9 UE Service Metrics
The following table describes the new UE Service metrics and the respective dimensions:
Table 9-181 ue_n1_ursp_rule_delivery
| Field | Details |
|---|---|
| Description | This metric is incremented when a URSP rule is selected for delivery to UE. |
| Metric Type | Counter |
| Dimensions | ruleName |
Table 9-182 ue_n1_transfer_request_total
| Field | Details |
|---|---|
| Description | This metric shall be incremented when PCF sends an encoded N1 message (fragment) to AMF for delivery to UE. |
| Metric Type | Counter |
| Dimensions |
|
Table 9-183 ue_n1_transfer_response_total
| Field | Details |
|---|---|
| Description | This metric shall be incremented when PCF receives a response from AMF for an N1 message (fragment) delivery to UE. |
| Metric Type | Counter |
| Dimensions |
|
Table 9-184 ue_n1_transfer_exception
| Field | Details |
|---|---|
| Description | This metric shall be incremented when PCF encounters an exception and fails to initiate an N1 message (fragment) delivery. |
| Metric Type | Counter |
| Dimensions |
|
Table 9-185 ue_n1_transfer_retransmit_total
| Field | Details |
|---|---|
| Description | This metric shall be incremented when PCF re-transmits an encoded N1 message (fragment) to AMF for delivery to UE. |
| Metric Type | Counter |
| Dimensions |
|
Table 9-186 ue_n1_transfer_abort
| Field | Details |
|---|---|
| Description | This metric shall be incremented when PCF aborts an N1 message delivery procedure. |
| Metric Type | Counter |
| Dimensions | reason |
Table 9-187 ue_n1_transfer_skip
| Field | Details |
|---|---|
| Description | This metric shall be incremented when PCF skips an N1 message fragment. |
| Metric Type | Counter |
| Dimensions | NA |
Table 9-188 ue_n1_transfer_failure_notification
| Field | Details |
|---|---|
| Description | This metric shall be incremented when PCF receives a transfer failure notification from the AMF. |
| Metric Type | Counter |
| Dimensions | cause |
Table 9-189 ue_n1_transfer_ue_notification_total
| Field | Details |
|---|---|
| Description | This metric shall be incremented when PCF receives an N1 notification from the UE. |
| Metric Type | Counter |
| Dimensions | commandType |
The following table describes the UE Service metrics and respective dimensions:
Table 9-190 ocpm_ingress_request_total
| Field | Details |
|---|---|
| Description | Total number of ingress requests received |
| Metric Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-191 ocpm_ingress_response_total
| Field | Details |
|---|---|
| Description | Total number of ingress responses |
| Metric Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-192 ocpm_egress_request_total
| Field | Details |
|---|---|
| Description | Total number of egress requests received |
| Metric Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-193 ocpm_egress_response_total
| Field | Details |
|---|---|
| Description | Total number of egress responses. |
| Metric Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-194 session_viewer_request_total
| Field | Details |
|---|---|
| Description | This metric shows the total number of query requests made using the Session Viewer. |
| Metric Type | Counter |
| Dimensions |
|
Table 9-195 session_viewer_response_total
| Field | Details |
|---|---|
| Description | This metric shows the total number of responses to query requests made using the Session Viewer. |
| Metric Type | Counter |
| Dimensions | - |
Table 9-196 session_oam_request_total
| Field | Details |
|---|---|
| Description | Number of session requests for UE Service |
| Metric Type | Request |
| Dimensions |
|
Table 9-197 session_oam_response_total
| Field | Details |
|---|---|
| Description | Number of session responses for UE Service |
| Metric Type | Response |
| Dimensions |
|
Table 9-198 occnp_ue_audit_stale_records_count_total
| Field | Details |
|---|---|
| Description | Total number of stale records received from Audit Service in all notifications |
| Metric Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-199 occnp_ue_audit_deleted_records_count_total
| Field | Details |
|---|---|
| Description | Total number of stale records deleted. |
| Metric Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-200 occnp_ue_update_notify_rcvd_error_response_total
| Field | Details |
|---|---|
| Description | Total number of update notify requests that can not be sent to AMF or timed out |
| Metric Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-201 audit_recs_stale_total
| Field | Details |
|---|---|
| Description | Total number of records detected as stale |
| Metric Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-202 occnp_ue_audit_notif_sent_to_amf_count_total
| Field | Details |
|---|---|
| Description | Total number of notifications sent to AMF on receiving stale session notification from audit |
| Metric Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-203 occnp_ue_audit_update_notify_session_found_total
| Field | Details |
|---|---|
| Description | Total number of sessions found at AMF on sending update notify request (that is, when received 204 response from AMF) |
| Metric Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-204 occnp_ue_audit_update_notify_session_not_found_total
| Field | Details |
|---|---|
| Description | Total number of sessions not found at AMF on sending update notify request (that is, received 404 response from AMF) |
| Metric Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-205 occnp_ue_audit_deleted_records_maxttl_reached_count_total
| Field | Details |
|---|---|
| Description | Total number of records deleted as maxTTL expired |
| Metric Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-206 session_info_request_total
| Field | Details |
|---|---|
| Description | Total number of sessions to be deleted as requested by the UE Policy Service |
| Metric Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-207 occnp_lease_duration_seconds_bucket
| Field | Details |
|---|---|
| Description | Time in seconds for which UE Service holds the lock |
| Metric Type | Histogram |
| Dimensions |
|
Table 9-208 session_info_response_total
| Field | Details |
|---|---|
| Description | Total number of sessions deleted as requested by the UE Policy Service |
| Metric Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-209 occnp_ue_discovery_success_count_total
| Field | Details |
|---|---|
| Description | Enables Policy to report how many discoveries based in AMF Region ID and AMF Set ID or GUAMI were successful |
| Metric Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-210 occnp_ue_discovery_failure_count_total
| Field | Details |
|---|---|
| Description | Enables Policy to report how many discoveries based in AMF Region ID and AMF Set ID or GUAMI failed |
| Metric Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-211 occnp_http_ue_request_total
| Field | Details |
|---|---|
| Description | Number of http UE requests |
| Metric Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-212 occnp_http_ue_response_total
| Field | Details |
|---|---|
| Description | Number of http UE responses |
| Metric Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-213 occnp_http_out_conn_request_total
| Field | Details |
|---|---|
| Description | Total number of connection requests received |
| Metric Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-214 occnp_http_out_conn_response_total
| Field | Details |
|---|---|
| Description | Total number of connection response sent |
| Metric Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-215 ocpm_ar_request_total
| Field | Details |
|---|---|
| Description | Total number of ar requests received |
| Metric Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-216 ocpm_ar_response_total
| Field | Details |
|---|---|
| Description | Total number of ar response sent |
| Metric Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-217 topic_version
| Field | Details |
|---|---|
| Description | Describes the current applied version of a given topic (mentioned in dimension topic_name) into the pod. |
| Metric Type | Counter |
| Dimensions |
|
Table 9-218 n1_message_policy_evaluation
| Field | Details |
|---|---|
| Description | Metric that increments each time there was a policy evaluated for skip, abort and retransmit n1 notification message. |
| Metric Type | Counter |
| Dimensions |
|
Table 9-219 occnp_db_overall_processing_time_seconds_sum
| Field | Details |
|---|---|
| Description | This metric is incremented when PCF performs DELETE operation on an Association |
| Metric Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-220 occnp_db_overall_processing_time_seconds_sum
| Field | Details |
|---|---|
| Description | This metric is incremented when PCF performs DELETE operation on an Association |
| Metric Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-221 occnp_ueservice_overall_processing_time_seconds_max
| Field | Details |
|---|---|
| Description |
This metric is incremented for UE service to calculate processing's duration of HTTP request arrived on rest controller. Note: occnp_ueservice_overall_processing_time_seconds_max metric replaces http_server_requests_seconds_max. |
| Metric Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-222 occnp_ueservice_overall_processing_time_seconds_sum
| Field | Details |
|---|---|
| Description |
This metric is incremented for UE service to calculate processing's duration of HTTP request arrived on rest controller. Note: occnp_ueservice_overall_processing_time_seconds_sum metric replaces http_server_requests_seconds_sum. |
| Metric Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-223 occnp_ueservice_overall_processing_time_seconds_count
| Field | Details |
|---|---|
| Description |
This metric is incremented for UE service to calculate processing's duration of HTTP request arrived on rest controller. Note: occnp_ueservice_overall_processing_time_seconds_count metric replaces http_server_requests_seconds_count. |
| Metric Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-224 ue_n1_unsubscribe_request_total
| Field | Details |
|---|---|
| Description | This metric is incremented while UE service sends request to NAS-AMF for N1 UNSUBSCRIBE. |
| Metric Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-225 ue_n1_unsubscribe_response_total
| Field | Details |
|---|---|
| Description | This metric is incremented when NAS-AMF sends back HTTP response to UE service for N1 UNSUBSCRIBE. |
| Metric Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-226 ue_n1_unsubscribe_exception_total
| Field | Details |
|---|---|
| Description | This metric is incremented in case of any exception occurred while sending N1 UNSUBSCRIBE request to NAS-AMF. |
| Metric Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-227 error_handler_in_total
| Field | Details |
|---|---|
| Description | This metric is incremented on initialization of error handling. |
| Type | Counter |
| Dimensions |
|
| Example | occnp_error_handler_in_total{application="pcf_ueservice",application_exception="JavaException",status="400",wrapped_exception="ServiceException",} 6.0 |
Table 9-228 error_handler_exec_total
| Field | Details |
|---|---|
| Description | This metric is incremented on error handling performed by framework. |
| Type | Counter |
| Dimensions |
|
| Example | occnp_error_handler_exec_total{application="pcf_ueservice",application_exception="JavaException",error_type="INTERNAL",operation="UPDATE",origin="JAVA",rule_name="REJECT_WITH_ENHANCED_DETAIL",source_interface="AMF",status="411",target_interface="POLICY",wrapped_exception="ServiceException",} 1.0 |
Table 9-229 error_handler_out_total
| Field | Details |
|---|---|
| Description | This metric is incremented on completion of error handling. |
| Type | Counter |
| Dimensions |
|
| Example | occnp_error_handler_out_total{application="pcf_ueservice",application_exception="JavaException",error_resolved="false",status="500",wrapped_exception="ServiceException",} 11.0 |
Table 9-230 occnp_http_congestion_message_reject_total
| Field | Details |
|---|---|
| Description | Track the count of rejected HTTP messages due to congestion. |
| Type | Counter |
| Dimension |
|
| Example |
|
Table 9-231 occnp_http_congestion_message_reject_total_seconds_bucket
| Field | Details |
|---|---|
| Description | Track the count of rejected HTTP messages due to congestion. |
| Type | Counter |
| Dimension |
|
| Example |
|
Table 9-232 occnp_http_congestion_message_reject_total_seconds_count
| Field | Details |
|---|---|
| Description | Track the count of rejected HTTP messages due to congestion. |
| Type | Counter |
| Dimension |
|
| Example |
|
Table 9-233 occnp_http_congestion_message_reject_total_seconds_sum
| Field | Details |
|---|---|
| Description | Track the count of rejected HTTP messages due to congestion. |
| Type | Histogram |
| Dimension |
|
| Example |
|
Table 9-234 occnp_http_congestion_message_reject_total_seconds_max
| Field | Details |
|---|---|
| Description | Track the count of rejected HTTP messages due to congestion. |
| Type | Histogram |
| Dimension |
|
| Example |
|
Table 9-235 occnp_http_congestion_message_reject_total_second
| Field | Details |
|---|---|
| Description | Track the count of rejected HTTP messages due to congestion. |
| Type | Histogram |
| Dimension |
|
| Example |
|
Table 9-236 occnp_pds_location_info_notification_total
| Field | Details |
|---|---|
| Description | This metric gets incremented when UE core service gets notification from PDS to update PDS Location info in case of concurrency. |
| Type | Counter |
| Dimensions |
|
| Example |
|
Table 9-237 ue_n1_subscribe_request_total
| Field | Details |
|---|---|
| Description | This metric is incremented when PCF sends a request to AMF for N1 subscription. |
| Type | Counter |
| Dimensions | servingPlmn |
| Example | ue_n1_subscribe_request_total{application="pcf_ueservice",hostname="rel-pcf-ueservice-67d4fd6b49-sqz57",servingPlmn="330042",} |
Table 9-238 ue_n1_subscribe_response_total
| Field | Details |
|---|---|
| Description | This metric is incremented when PCF receives a response from AMF for N1 subscription request. |
| Type | Counter |
| Dimensions |
|
| Example | ue_n1_subscribe_response_total{application="pcf_ueservice",hostname="rel-pcf-ueservice-67d4fd6b49-sqz57",latency="5",responseCode="201",servingPlmn="330042",} |
Table 9-239 ue_n1_policy_sequencing
| Field | Details |
|---|---|
| Description | This metric tracks each time a UE policy decision is placed into the pending queue for later delivery. That is, when the system needs to hold the decision for a future N1 transfer. It is recorded whenever a Timer due to RetryAfterIE or Reattempt and Backoff is actively running, even if the consolidation feature flag (Enable Consolidation of UE Policy Decisions field under section AMF on PCF UE Policy for Service Configurations on CNC Console) is on, and only omitted when consolidation is enabled and no timer is running, because the decisions are then sent together in a single batch.
|
| Type | Counter |
| Dimensions |
|
| Example | ue_n1_policy_sequencing_total{app_kubernetes_io_instance="ocpcf", app_kubernetes_io_managed_by="Helm", app_kubernetes_io_name="ue-service", app_kubernetes_io_part_of="occnp", app_kubernetes_io_version="1.0.0", application="occnp", container="ue-service", endpoint="cnc-metrics", engVersion="25.1.0-beta.4", exported_application="pcf_ueservice", helm_sh_chart="ue-service-25.1.0-beta.4", hostname="ocpcf-pcf-ueservice-7f697f6797-f6962", instance="10.233.105.239:9000", io_kompose_service="ocpcf-pcf-ueservice", job="occne-infra/occne-nf-cnc-podmonitor", microservice="pcf_ueservice", mktgVersion="1.0.0", namespace="hi-ns01", pod="ocpcf-pcf-ueservice-7f697f6797-f6962", pod_template_hash="7f697f6797", source="nchf_spendinglimitcontrol_notify", vendor="Oracle"} |
Table 9-240 ue_n1_policy_consolidation_total
| Field | Details |
|---|---|
| Description | This metric tracks the number of consolidated N1N2
transfers performed.
Note: The consolidated N1N2 transfer may not be sent to UE if install optimization is enabled. |
| Type | Counter |
| Dimensions |
|
| Examples | ue_n1_policy_consolidation_total{app_kubernetes_io_instance="ocpcf", app_kubernetes_io_managed_by="Helm", app_kubernetes_io_name="ue-service", app_kubernetes_io_part_of="occnp", app_kubernetes_io_version="1.0.0", application="occnp", container="ue-service", endpoint="cnc-metrics", engVersion="25.1.0-beta.4", exported_application="pcf_ueservice", helm_sh_chart="ue-service-25.1.0-beta.4", hostname="ocpcf-pcf-ueservice-7f697f6797-f6962", instance="10.233.105.239:9000", io_kompose_service="ocpcf-pcf-ueservice", job="occne-infra/occne-nf-cnc-podmonitor", microservice="pcf_ueservice", mktgVersion="1.0.0", namespace="hi-ns01", pod="ocpcf-pcf-ueservice-7f697f6797-f6962", pod_template_hash="7f697f6797", source="t3501_expiry", vendor="Oracle"} |
Table 9-241 ue_n1_policy_backed_off_collation_total
| Field | Details |
|---|---|
| Description | The metrics is pegged when sequenced policy decisions are collated into a single one, either due to an initial request failure followed by subsequent triggers (Update/UDR, CHF Notify) or when subsequent requests also fail and then both Policy decisions are retransmitted during an reattempt after backoff notification. |
| Type | Counter |
| Dimensions |
|
| Example | - |
Table 9-242 ocpm_late_arrival_rejection_total
| Field | Details |
|---|---|
| Description | This metric is pegged whenever UE receives a request, and it is canceled because it is already stale. |
| Type | Counter |
| Dimensions |
|
| Example | - |
Table 9-243 occnp_late_processing_rejection_total
| Field | Details |
|---|---|
| Description | This metric is pegged whenever UE receives a request and it got stale during processing. |
| Type | Counter |
| Dimensions |
|
| Example | - |
Table 9-244 occnp_ue_timer_registration_total
| Field | Details |
|---|---|
| Description | This metric is pegged after sending registration request to timer service. Its state dimension tells whether the request was "SUCCESS" or "FAILURE". |
| Type | Counter |
| Dimensions |
|
| Example | - |
Table 9-245 occnp_ue_timer_create_success_total
| Field | Details |
|---|---|
| Description | This metric is pegged when timer is successfully created in timer service. |
| Type | Counter |
| Dimensions |
|
| Example | - |
Table 9-246 occnp_ue_timer_create_failure_total
| Field | Details |
|---|---|
| Description | This metric is pegged when timer creation fails in timer service. |
| Type | Counter |
| Dimensions |
|
| Example | - |
Table 9-247 occnp_ue_timer_delete_success_total
| Field | Details |
|---|---|
| Description | This metric is pegged when timer deletion request is success in timer service. |
| Type | Counter |
| Dimensions |
|
| Example | - |
Table 9-248 occnp_ue_timer_delete_failure_total
| Field | Details |
|---|---|
| Description | This metric is pegged when timer deletion fails in timer service. |
| Type | Counter |
| Dimensions |
|
| Example | - |
Table 9-249 occnp_ue_nf_discovery_reattempt_request_total
| Field | Details |
|---|---|
| Description | This metric on the request part is pegged only on reattempted request to NRF for AMF discovery. |
| Type | Counter |
| Dimensions |
|
| Example | - |
Table 9-250 occnp_ue_nf_discovery_reattempt_response_total
| Field | Details |
|---|---|
| Description | This metric on response part is pegged only on reattempted request to NRF for AMF discovery. |
| Type | Counter |
| Dimensions |
|
| Example | - |
Table 9-251 ue_rule_size_limit_exceeded
| Field | Details |
|---|---|
| Description | This metric has been pegged when UPSI/URSP has been skipped from N1N2 message transfer due to URSP fragment size greater than configured, or N1 message size is greater than configured. |
| Type | Counter |
| Dimensions | Rule Name, Rule Type |
| Example |
Table 9-252 ue_rule_config_error_total
| Field | Details |
|---|---|
| Description | This metric is incremented when an invalid URSP or UPSI rule is used during N1 transfer. |
| Type | Counter |
| Dimensions | ruleId, ruleType, ruleName |
| Example | ue_rule_config_error_total{ruleType="URSP", ruleId="5d99f63d-5f23-4565-8939-7133c68d437f", ruleName="ursp1"} |
Table 9-253 ue_n1_transfer_t3501_expiry_total
| Field | Details |
|---|---|
| Description | This metric is incremented when the T3501 timer expires. |
| Type | Counter |
| Dimensions |
|
| Example | ue_n1_transfer_t3501_expiry_total{application="pcf_ueservice",fragIdx="0",hostname="ocpcf-pcf-ueservice-864499b66b-smqz5",servingPlmn="311480",}1.0 |
Table 9-254 ue_n1_policy_rule_conflict_total
| Field | Details |
|---|---|
| Description | This metric tracks UE Policy evaluations corresponding to a trigger which results in conflicting UE Policy action. |
| Type | Counter |
| Dimensions | Source
Possible Values:
|
| Example |
ue_n1_policy_rule_conflict_total{app_kubernetes_io_instance="v4", app_kubernetes_io_managed_by="Helm", app_kubernetes_io_name="ue-service", app_kubernetes_io_part_of="occnp", app_kubernetes_io_version="25.2.100-beta.7.0.0", application="occnp", container="ue-service", endpoint="cnc-metrics", engVersion="25.2.100-beta.7", exported_application="pcf_ueservice", helm_sh_chart="ue-service-25.2.100-beta.7", hostname="v4-pcf-ueservice-9d9fff5-cdv6l", instance="10.233.93.187:9000", io_kompose_service="v4-pcf-ueservice", job="occne-infra/occne-nf-cnc-podmonitor", microservice="pcf_ueservice", mktgVersion="25.2.100-beta.7.0.0", namespace="vega-ns4", pod="v4-pcf-ueservice-9d9fff5-cdv6l", pod_template_hash="9d9fff5", source="n1messagenotify_command_complete", vendor="Oracle"} ue_n1_policy_rule_conflict_total{app_kubernetes_io_instance="sm", app_kubernetes_io_managed_by="Helm", app_kubernetes_io_name="ue-service", app_kubernetes_io_part_of="occnp", app_kubernetes_io_version="25.2.100-beta.8.0.0", application="occnp", container="ue-service", endpoint="cnc-metrics", engVersion="25.2.100-beta.8", exported_application="pcf_ueservice", helm_sh_chart="ue-service-25.2.100-beta.8", hostname="sm-pcf-ueservice-6bc64f5798-lw48f", instance="10.233.124.254:9000", io_kompose_service="sm-pcf-ueservice", job="occne-infra/occne-nf-cnc-podmonitor", microservice="pcf_ueservice", mktgVersion="25.2.100-beta.8.0.0", namespace="sky3-ns8", pod="sm-pcf-ueservice-6bc64f5798-lw48f", pod_template_hash="6bc64f5798", source="npcf_uepolicycontrol_update", vendor="Oracle"} |
Table 9-255 occnp_ue_update_guami_change_during_retryafter_cancelled_total
| Field | Details |
|---|---|
| Description | This metric is used to measure the number of updates received with change in GUAMI during the retry-after time period and "retryAfter" is cancelled for the N1N2Transfer to be sent to the new AMF. This metric provides the details of the AMF to which the N1N2Transfer is being sent. |
| Type | Counter |
| Dimensions |
|
| Example |
occnp_ue_update_guami_change_during_retryafter_cancelled_total{amfId="010081",application="pcf_ueservice",hostname="adi-pcf-ueservice-84db8dc45f-j4pvb",mcc="450",mnc="05"} |
Table 9-256 occnp_ue_delete_during_retryafter_total
| Field | Details |
|---|---|
| Description | This metric is used to measure the number of Delete requests received from AMF for the UEPolicyAssociation during the "retryAfter" time period and the session is deleted. |
| Type | Counter |
| Dimensions |
|
| Example |
occnp_ue_delete_during_retryafter_total{amfId="010041",application="pcf_ueservice",hostname="adi-pcf-ueservice-84db8dc45f-j4pvb",mcc="450",mnc="05"} |
Table 9-257 occnp_ue_http_in_request_during_retryafter_total
| Field | Details |
|---|---|
| Description |
This metric is used to measure the number of requests (Update/Delete/UDR/CHF notification) received for the UEPolicyAssociation during the "retryAfter" time period. |
| Type | Counter |
| Dimensions |
|
| Example |
occnp_ue_http_in_request_during_retryafter_total{application="pcf_ueservice",hostname="adi-pcf-ueservice-84db8dc45f-j4pvb",source="nchf_spendinglimitcontrol_notify"} |
Table 9-258 occnp_n1n2transfer_error_with_retryafter_seconds
| Field | Details |
|---|---|
| Description |
This metric is used to measure the number of N1N2Transfer error responses received with "retryAfter" timer with a valid value in payload body. |
| Type | Counter |
| Dimensions |
|
| Example |
occnp_n1n2transfer_error_with_retryafter_seconds_bucket{amfId="0100C1",application="pcf_ueservice",hostname="adi-pcf-ueservice-84db8dc45f-j4pvb",mcc="450",mnc="05",response_code="504",le="600.0"} occnp_n1n2transfer_error_with_retryafter_seconds_bucket{amfId="0100C1",application="pcf_ueservice",hostname="adi-pcf-ueservice-84db8dc45f-j4pvb",mcc="450",mnc="05",response_code="504",le="+Inf"} occnp_n1n2transfer_error_with_retryafter_seconds_count{amfId="0100C1",application="pcf_ueservice",hostname="adi-pcf-ueservice-84db8dc45f-j4pvb",mcc="450",mnc="05",response_code="504"} occnp_n1n2transfer_error_with_retryafter_seconds_sum{amfId="0100C1",application="pcf_ueservice",hostname="adi-pcf-ueservice-84db8dc45f-j4pvb",mcc="450",mnc="05",response_code="504"} |
Table 9-259 occnp_n1n2transfer_error_retryafter_invalid_total
| Field | Details |
|---|---|
| Description |
This metric is used to measure the number of N1N2Transfer error responses received with invalid "retryAfter" value (that is, greater than configured max (configuration is done in advance setting) in the payload body or less than or equal to 0). |
| Type | Counter |
| Dimensions |
|
| Example |
occnp_n1n2transfer_error_retryafter_invalid_total{amfId="010041",application="pcf_ueservice",hostname="adi-pcf-ueservice-84db8dc45f-j4pvb",mcc="450",mnc="05",response_code="504",retry_after_gt_config_max="false",retry_after_le_zero="true"} |
Table 9-260 occnp_ue_update_guami_change_count
| Field | Details |
|---|---|
| Description | This metric is used to measure the number of updates received with change in GUAMI. |
| Type | Counter |
| Dimensions |
|
| Example | - |
Table 9-261 occnp_ue_update_resubscription_condition_change
| Field | Details |
|---|---|
| Description | This metric is used to measure the number of updates received with change in GUAMI, which resulted in discovery and further subscription. |
| Type | Counter |
| Dimensions |
|
| Example | - |
For more information about Dimensions, see CNC Policy Metrics.
9.10 User Service Metrics
The following table describes the User Service (User/UDR/CHF) metrics and respective dimensions:
Table 9-262 ocpm_userservice_inbound_count_total
| Field | Details |
|---|---|
| Description | Total number of inbound request. |
| Metric Type | Counter |
| Dimensions |
|
- ocpm_userservice_inbound_count_total{application="pcf_userservice",operation_type="post",service_resource="udr-service",} 0.0 ; Type-Counter
- ocpm_userservice_inbound_count_total{application="pcf_userservice",operation_type="get",service_resource="chf-service",} 0.0 ; Type-Counter
- ocpm_userservice_inbound_count_total{application="pcf_userservice",operation_type="get",service_resource="udr-service",} 0.0 ; Type-Counter
- ocpm_userservice_inbound_count_total{application="pcf_userservice",operation_type="notify",service_resource="chf-service",} 0.0 ; Type-Counter
- ocpm_userservice_inbound_count_total{application="pcf_userservice",operation_type="delete",service_resource="user-service",} 0.0 ; Type-Counter
- ocpm_userservice_inbound_count_total{application="pcf_userservice",operation_type="get",service_resource="user-service",} 0.0 ; Type-Counter
- ocpm_userservice_inbound_count_total{application="pcf_userservice",operation_type="notify",service_resource="udr-service",} 0.0 ; Type-Counter
- ocpm_userservice_inbound_count_total{application="pcf_userservice",operation_type="delete",service_resource="udr-service",} 0.0 ; Type-Counter
- ocpm_userservice_inbound_count_total{application="pcf_userservice",operation_type="terminate",service_resource="chf-service",} 0.0 ; Type-Counter
- ocpm_userservice_inbound_count_total{application="pcf_userservice",operation_type="delete",service_resource="chf-service",} 0.0 ; Type-Counter
- ocpm_userservice_inbound_count_total{application="pcf_userservice",operation_type="patch",service_resource="udr-service",} 0.0 ; Type-Counter
- ocpm_userservice_inbound_count_total{application="pcf_userservice",operation_type="put",service_resource="udr-service",} 0.0 ; Type-Counter
Table 9-263 ocpm_ar_setup_total
| Field | Details |
|---|---|
| Description | Track number of registration request sent to alternate route service. |
| Metric Type | Counter |
| Dimensions |
|
- ocpm_ar_setup_total{anchorFqdn="chfanchor.allsim.svc",application="pcf_userservice",scheme="http",} 1.0 ; Type-Counter
Table 9-264 ocpm_ar_request_total
| Field | Details |
|---|---|
| Description | Tracks number of alternate routing attempts to producer or consumer on Initial, Subsequent, or Notification messages. |
| Metric Type | Counter |
| Dimensions |
|
- ocpm_ar_request_total{application="pcf_userservice",fqdn="udmanchor.allsim.svc",scheme="http",} 1.0 ; Type-Counter
Table 9-265 ocpm_ar_response_total
| Field | Details |
|---|---|
| Description | Tracks response on number of alternate routing attempts to producer or consumer on Initial, Subsequent, or Notification messages. |
| Metric Type | Counter |
| Dimensions |
|
- ocpm_ar_response_total{application="pcf_userservice",fqdn="udmanchor.allsim.svc",responseCode="2xx",scheme="http",} 1.0 ; Type-Counter
Table 9-266 ocpm_ar_lookup_request_total
| Field | Details |
|---|---|
| Description | Track number of time alternate route lookup was done for a given scheme+FQDN. |
| Metric Type | Counter |
| Dimensions |
|
- ocpm_ar_lookup_request_total{anchorFqdn="udmanchor.allsim.svc",application="pcf_userservice",scheme="http",} 1.0 ; Type-Counter
Table 9-267 ocpm_ar_lookup_response_total
| Field | Details |
|---|---|
| Description | Tracks response codes for request to "alternateRoute" service. |
| Metric Type | Counter |
| Dimensions |
|
- ocpm_ar_lookup_response_total{anchorFqdn="udmanchor.allsim.svc",application="pcf_userservice",responseCode="2xx",scheme="http",} 1.0 ; Type-Counter
Table 9-268 ocpm_udr_tracking_request_total
| Field | Details |
|---|---|
| Description | This metric captures all the requests sent by UDR Connector on it's communication with UDR. |
| Metric Type | Counter |
| Dimensions |
|
| Examples |
ocpm_udr_tracking_request_total{HostName="",application="pcf_userservice",binding_id="",binding_level="",discovery_id="",discovery_parameter="",hostname="my-cnpolicy-occnp-udr-connector-7ddfc965b9-s8nwq",nf_instance_id="fe7d992b-0541-4c7d-ab84-333334444434",nf_name="nf21stub.h3-ns10.svc",operation_type="get",service_resource="policy-data",service_subresource="um-data",service_version="v1",servicename_3gpp="nudr-dr",} 0.0 ocpm_udr_tracking_request_total{HostName="",application="pcf_userservice",binding_id="",binding_level="",discovery_id="",discovery_parameter="",hostname="titans-occnp-udr-connector-694f9795d8-gmdl4",nf_instance_id="fe7d992b-0541-4c7d-ab84-555552222222",nf_name="nf1stub.rigelns6.svc",operation_type="lookup_subscribe",service_resource="subscription-data",service_subresource="subs-to-notify",service_version="v1",servicename_3gpp="nudr-dr",} 1.0 ocpm_udr_tracking_request_total{HostName="",application="pcf_userservice",binding_id="",binding_level="",discovery_id="",discovery_paramete r="",hostname="conv-occnp-udr-connector-797fb77675-dpmtz",nf_instance_id="fe7d992b-0541-4c7d-ab84-555556666655",nf_name="nf11stub.ch2-ns13. svc",operation_type="subscribe",service_resource="policy-data",service_subresource="subs-to-notify",service_version="v1",servicename_3gpp=" nudr-dr",} 3.0 ocpm_udr_tracking_request_total{HostName="",application="pcf_userservice",binding_id="",binding_level="nf-set",discovery_id="",discovery_pa rameter="",hostname="conv-occnp-udr-connector-797fb77675-dpmtz",nf_instance_id="fe7d992b-0541-4c7d-ab84-555553333333",nf_name="nf3stub.ch2- ns13.svc",operation_type="unsubscribe",service_resource="policy-data",service_subresource="subs-to-notify",service_version="v1",servicename _3gpp="nudr-dr",} 1.0 ocpm_udr_tracking_request_total{HostName="",application="pcf_userservice",binding_id="",binding_level="",discovery_id="",discovery_parameter="",hostname="conv-occnp-udr-connector-797fb77675-dpmtz",nf_instance_id="fe7d992b-0541-4c7d-ab84-555550000000",nf_name="nf3stub.ch2-ns13.s vc",operation_type="get",service_resource="policy-data",service_subresource="ue-policy-set",service_version="v1",servicename_3gpp="nudr-dr" ,} 2.0 |
Table 9-269 ocpm_chf_tracking_request_total
| Field | Details |
|---|---|
| Description | Total number of CHF tracking requests. |
| Metric Type | Counter |
| Dimensions |
|
Table 9-270 ocpm_udr_tracking_response_total
| Field | Details |
|---|---|
| Description | This metric captures all the responses received by UDR-conn on it's communication with UDR. |
| Metric Type | Counter |
| Dimensions |
|
| Examples |
ocpm_udr_tracking_response_total{HostName="",application="pcf_userservice",nf_instance_id="fe7d992b-0541-4c7d-ab84-c6d70b1babc1",nf_name="udr.xxxx.com",operation_type="subscribe",response_code="2xx",service_resource="policy-data",service_subresource="",service_version="v1",servicename_3gpp="nudr-dr",} 0.0 ; Type-Counter ocpm_udr_tracking_response_total{HostName="",application="pcf_userservice",hostname="my-cnpolicy-occnp-udr-connector-7ddfc965b9-s8nwq",nf_instance_id="fe7d992b-0541-4c7d-ab84-333334444433",nf_name="nf2stub.h3-ns10.svc",operation_type="put",response_code="3xx",service_resource="policy-data",service_subresource="sm-data",service_version="v1",servicename_3gpp="nudr-dr",} 0.0 ocpm_udr_tracking_response_total{HostName="",application="pcf_userservice",hostname="titans-occnp-udr-connector-694f9795d8-gmdl4",nf_instance_id="fe7d992b-0541-4c7d-ab84-555552222222",nf_name="nf1stub.rigelns6.svc",operation_type="lookup_subscribe",response_code="2xx",service_resource="subscription-data",service_subresource="subs-to-notify",service_version="v1",servicename_3gpp="nudr-dr",} 1.0 ocpm_udr_tracking_response_total{HostName="",application="pcf_userservice",hostname="conv-occnp-udr-connector-797fb77675-dpmtz",nf_instance _id="fe7d992b-0541-4c7d-ab84-555552222222",nf_name="nf2stub.ch2-ns13.svc",operation_type="subscribe",response_code="2xx",service_resource=" policy-data",service_subresource="subs-to-notify",service_version="v1",servicename_3gpp="nudr-dr",} 3.0 ocpm_udr_tracking_response_total{HostName="",application="pcf_userservice",hostname="conv-occnp-udr-connector-797fb77675-dpmtz",nf_instance _id="fe7d992b-0541-4c7d-ab84-555553333333",nf_name="nf3stub.ch2-ns13.svc",operation_type="get",response_code="2xx",service_resource="policy -data",service_subresource="am-data",service_version="v1",servicename_3gpp="nudr-dr",} 2.0 ocpm_udr_tracking_response_total{HostName="",application="pcf_userservice",hostname="conv-occnp-udr-connector-797fb77675-dpmtz",nf_instance _id="fe7d992b-0541-4c7d-ab84-555552222222",nf_name="nf1stub.ch2-ns13.svc",operation_type="unsubscribe",response_code="2xx",service_resource ="policy-data",service_subresource="subs-to-notify",service_version="v1",servicename_3gpp="nudr-dr",} 11.0 |
Table 9-271 ocpm_udr_tracking_request_timeout_total
| Field | Details |
|---|---|
| Description | This metric captures all the requests sent by UDR Connector on it's communication with UDR which ends up with timeout. |
| Metric Type | Counter |
| Dimensions |
|
| Examples |
ocpm_udr_tracking_request_timeout_total{HostName="",application="pcf_userservice",hostname="conv-occnp-udr-connector-66c6f47c4f-45tjf",nf_instance_id="fe7d992b-0541-4c7d-ab84-555553333333",nf_name="nf3stub.ch2-ns13.svc",operation_type="lookup_subscribe",service_resource="subscription-data",service_subresource="subs-to-notify",service_version="v1",servicename_3gpp="nudr-dr",} ocpm_udr_tracking_request_timeout_total{HostName="",application="pcf_userservice",nf_instance_id="fe7d992b-0541-4c7d-ab84-c6d70b1babc1",nf_name="udr.xxxx.com",operation_type="patch",service_resource="policy-data",service_subresource="subs-to-notify",service_version="v1",servicename_3gpp="nudr-dr",} 0.0; Type-Counter |
Table 9-272 ocpm_chf_tracking_response_total
| Field | Details |
|---|---|
| Description | Total number of CHF tracking responses. |
| Metric Type | Counter |
| Dimensions |
|
Table 9-273 ocpm_chf_tracking_request_timeout_total
| Field | Details |
|---|---|
| Description | Total number of CHF request timeouts. |
| Metric Type | - |
| Dimensions |
|
Table 9-274 topic_version
| Field | Details |
|---|---|
| Description | Describes the current applied version of a given topic (mentioned in dimension topic_name) into the pod. |
| Metric Type | Gauge |
| Dimensions |
|
Table 9-275 occnp_policy_userservice_overall_processing_time_seconds
| Field | Details |
|---|---|
| Description | User service overall processing time.
Note: Default name used when there is no custom name available is data_repository_invocations. |
| Type | Summary |
| Dimension |
|
| Example | - |
Table 9-276 occnp_policy_userservice_overall_processing_time_seconds_count
| Field | Details |
|---|---|
| Description | User service overall processing time. |
| Type | Counter |
| Dimension |
|
Table 9-277 occnp_policy_userservice_overall_processing_time_seconds_max
| Field | Details |
|---|---|
| Description | User service overall processing time. |
| Type | Gauge |
| Dimension |
|
Table 9-278 occnp_policy_userservice_overall_processing_time_seconds_sum
| Field | Details |
|---|---|
| Description | User service overall processing time. |
| Type | Counter |
| Dimension |
|
Table 9-279 occnp_udr_nf_profile_cookie_enabled_total
| Field | Details |
|---|---|
| Description | This metric is incremented when cached NF profile is used and the feature is enabled. |
| Metric Type | Counter |
| Dimensions |
|
| Example | occnp_udr_nf_profile_cookie_enabled_total{HostName="",application="pcf_userservice",hostname="pcf-occnp-udr-connector-5dc478c84c-78k9p",nf_instance_id="fe7d992b-0541-4c7d-ab84-555550000000",nf_name="nf1stub.s-galeleo.svc",operation_type="GET",service_resource="policy-data",service_subresource="ue-policy-set",service_version="v1",servicename_3gpp="nudr-dr",} 3.0 |
- occnp_udr_nf_profile_cookie_enabled_total{HostName="",application="pcf_userservice",hostname="pcf-occnp-udr-connector-5dc478c84c-78k9p",nf_instance_id="fe7d992b-0541-4c7d-ab84-555550000000",nf_name="nf1stub.s-galeleo.svc",operation_type="GET",service_resource="policy-data",service_subresource="ue-policy-set",service_version="v1",servicename_3gpp="nudr-dr",} 3.0
Table 9-280 occnp_udr_use_related_resource
| Field | Details |
|---|---|
| Description | This metric is incremented when a related resource is used and feature is enabled. |
| Metric Type | Counter |
| Dimensions |
|
| Example | occnp_udr_use_related_resource_total{HostName="",application="pcf_userservice",hostname="pcf-occnp-udr-connector-5dc478c84c-78k9p",nf_instance_id="fe7d992b-0541-4c7d-ab84-555550000000",nf_name="nf1stub.s-galeleo.svc",operation_type="GET",service_resource="policy-data",service_subresource="ue-policy-set",service_version="v1",servicename_3gpp="NUDR_DR",} 1.0 |
Table 9-281 error_handler_in_total
| Field | Details |
|---|---|
| Description | This metric is incremented on initialization of error handling. |
| Type | Counter |
| Dimensions |
|
| Example | occnp_error_handler_in_total{application="pcf_userservice",application_exception="JavaException",status="502",wrapped_exception="ServiceException",} 4.0 |
Table 9-282 error_handler_exec_total
| Field | Details |
|---|---|
| Description | This metric is incremented on error handling performed by framework. |
| Type | Counter |
| Dimensions |
|
| Example | occnp_error_handler_exec_total{application="pcf_userservice",application_exception="JavaException",error_type="INTERNAL",operation="NOTIFY",origin="JAVA",rule_name="REJECT_WITH_ENHANCED_DETAIL",source_interface="UDR",status="502",target_interface="POLICY",wrapped_exception="ServiceException",} 4.0 |
Table 9-283 error_handler_out_total
| Field | Details |
|---|---|
| Description | This metric is incremented on completion of error handling. |
| Type | Counter |
| Dimensions |
|
| Example | occnp_error_handler_out_total{application="pcf_userservice",application_exception="JavaException",error_resolved="true",status="400",wrapped_exception="ServiceException",} 4.0 |
Table 9-284 occnp_late_arrival_rejection_total
| Field | Details |
|---|---|
| Description | This metric is pegged whenever User Service receives a request, and it is canceled because it is already stale. |
| Type | Counter |
| Dimensions |
|
| Example | - |
Table 9-285 occnp_late_processing_rejection_total
| Field | Details |
|---|---|
| Description | This metric is pegged whenever User Service receives a request, and it is canceled because it has gone stale while processing it. |
| Type | Counter |
| Dimensions |
|
| Example | - |
Table 9-286 occnp_immrep_request_total
| Field | Details |
|---|---|
| Description | This metric is incremented in the following
scenarios related to immediate reporting and fallback procedures
with the UDR:
|
| Type | Counter |
| Dimensions |
|
| Example | occnp_immrep_request_total{app_kubernetes_io_instance="ocpcf", app_kubernetes_io_managed_by="Helm", app_kubernetes_io_name="user-service", app_kubernetes_io_part_of="occnp", app_kubernetes_io_version="25.2.100-ocngf-pre-dev-prodigies.0.0", application="occnp", container="user-service", endpoint="cnc-metrics", engVersion="25.2.100-ocngf-pre-dev-prodigies", exported_application="pcf_userservice", helm_sh_chart="user-service-25.2.100-ocngf-pre-dev-prodigies", hostname="ocpcf-occnp-udr-connector-86c5786fff-dqzfh", instance="10.233.101.111:9000", io_kompose_service="ocpcf-occnp-udr-connector", job="occne-infra/occne-nf-cnc-podmonitor", microservice="occnp_pcf_user", mktgVersion="25.2.100-ocngf-pre-dev-prodigies.0.0", namespace="hi-ns01", nf_name="10.148.211.41", operation_type="post", pod="ocpcf-occnp-udr-connector-86c5786fff-dqzfh", pod_template_hash="86c5786fff", service_subresource="am-data", vendor="Oracle"} |
Table 9-287 occnp_immrep_response_total
| Field | Details |
|---|---|
| Description | This metric shall be incremented after receiving UDR
response for immediate Report.
Note: This metric will only be pegged if the discovered UDR has immediate reporting capability. |
| Type | Counter |
| Dimensions |
|
| Example | occnp_immrep_response_total{app_kubernetes_io_instance="ocpcf", app_kubernetes_io_managed_by="Helm", app_kubernetes_io_name="user-service", app_kubernetes_io_part_of="occnp", app_kubernetes_io_version="25.2.100-ocngf-pre-dev-prodigies.0.0", application="occnp", container="user-service", endpoint="cnc-metrics", engVersion="25.2.100-ocngf-pre-dev-prodigies", exported_application="pcf_userservice", helm_sh_chart="user-service-25.2.100-ocngf-pre-dev-prodigies", hostname="ocpcf-occnp-udr-connector-86c5786fff-dqzfh", imm_reports_present="true", immediate_report_pcc="true", instance="10.233.101.111:9000", io_kompose_service="ocpcf-occnp-udr-connector", job="occne-infra/occne-nf-cnc-podmonitor", microservice="occnp_pcf_user", mktgVersion="25.2.100-ocngf-pre-dev-prodigies.0.0", namespace="hi-ns01", nf_name="10.148.211.41", operation_type="post", pod="ocpcf-occnp-udr-connector-86c5786fff-dqzfh", pod_template_hash="86c5786fff", response_code="2xx", service_subresource="am-data", vendor="Oracle"} |
Table 9-288 occnp_immrep_skipped_total
| Field | Details |
|---|---|
| Description | This metric is incremented when PCF from a prior
transaction with the same UDR for the same subscriber finds out that
the Immediate Report feature is not supported by the UDR and hence
skips the feature during a subsequent session creation.
This functionality is dependent on discovery optimization feature. It can be enabled by setting UDR_GET_USE_RELATED_RESOURCE flag as true. For more information on this flag, see PCF User Connector. |
| Type | Counter |
| Dimensions |
|
| Example | occnp_immrep_skipped_total{app_kubernetes_io_instance="ocpcf", app_kubernetes_io_managed_by="Helm", app_kubernetes_io_name="user-service", app_kubernetes_io_part_of="occnp", app_kubernetes_io_version="25.2.100-ocngf-pre-dev-prodigies.0.0", application="occnp", container="user-service", endpoint="cnc-metrics", engVersion="25.2.100-ocngf-pre-dev-prodigies", exported_application="pcf_userservice", helm_sh_chart="user-service-25.2.100-ocngf-pre-dev-prodigies", hostname="ocpcf-occnp-udr-connector-86c5786fff-dqzfh", instance="10.233.101.111:9000", io_kompose_service="ocpcf-occnp-udr-connector", job="occne-infra/occne-nf-cnc-podmonitor", microservice="occnp_pcf_user", mktgVersion="25.2.100-ocngf-pre-dev-prodigies.0.0", namespace="hi-ns01", nf_name="10.148.211.41", pod="ocpcf-occnp-udr-connector-86c5786fff-dqzfh", pod_template_hash="86c5786fff", service_subresource="ue-policy-set", vendor="Oracle"} |
For more information about Dimensions, see CNC Policy Metrics.
9.11 Diameter Connector Service Metrics
The following table describes the Diameter Connector Service metrics and respective dimensions:
Table 9-289 ocpm_ingress_request_total
| Field | Details |
|---|---|
| Description | Total number of ingress requests received. |
| Metric Type | Counter |
| Dimensions |
|
- ocpm_ingress_request_total{apn="",nf_instance_id="AF.xxx.com",operation_type="create",servicename_3gpp="rx",} 5.0 ; Type-Counter
Table 9-290 ocpm_ingress_response_total
| Field | Details |
|---|---|
| Description | Total number of ingress responses. |
| Metric Type | Counter |
| Dimensions |
|
- ocpm_ingress_response_total{apn="",nf_instance_id="ocpcf",operation_type="create",response_code="2xxx",servicename_3gpp="rx",} 2.0 ; Type-Counter
Table 9-291 ocpm_egress_request_total
| Field | Details |
|---|---|
| Description | Total number of egress requests received. |
| Metric Type | Counter |
| Dimensions |
|
- ocpm_egress_request_total{nf_instance_id="AF.xxx.com",operation_type="update_notify",servicename_3gpp="rx",} 1.0 ; Type-Counter
Table 9-292 ocpm_egress_response_total
| Field | Details |
|---|---|
| Description | Total number of egress responses. |
| Metric Type | Counter |
| Dimensions |
|
- ocpm_egress_response_total{latency="3",nf_instance_id="AF.xxx.com",operation_type="update_notify",response_code="2xxx",servicename_3gpp="rx",} 1.0 ; Type-Counter
Table 9-293 occnp_diam_pending_requests
| Field | Details |
|---|---|
| Description | Track the total pending Diameter messages |
| Type | Gauge |
| Dimension |
|
| Example | - |
Table 9-294 occnp_http_pending_requests
| Field | Details |
|---|---|
| Description | Track the total pending HTTP messages. |
| Type | Gauge |
| Dimension |
|
| Example | - |
Table 9-295 ocpm_egress_response_total
| Field | Details |
|---|---|
| Description | Total number of egress responses. |
| Metric Type | Counter |
| Dimensions |
|
Table 9-296 topic_version
| Field | Details |
|---|---|
| Description | Describes the current applied version of a given topic (mentioned in dimension topic_name) into the pod. |
| Metric Type | Gauge |
| Dimensions |
|
Table 9-297 occnp_diam_connector_overall_processing_time_seconds
| Field | Details |
|---|---|
| Description | Diameter Connector service overall processing time. |
| Type | Summary |
| Dimension |
|
Table 9-298 occnp_diam_connector_overall_processing_time_seconds_max
| Field | Details |
|---|---|
| Description | Diameter Connector service overall processing
time.
Note: Default name used when there is no custom name available is data_repository_invocations. |
| Type | Gauge |
| Dimension |
|
| Example |
|
Table 9-299 occnp_diam_connector_overall_processing_time_seconds_count
| Field | Details |
|---|---|
| Description | Diameter Connector service overall processing time. |
| Type | Counter |
| Dimension |
|
| Examples |
|
Table 9-300 occnp_diam_connector_overall_processing_time_seconds_sum
| Field | Details |
|---|---|
| Description | Diameter Connector service overall processing time. |
| Type | Counter |
| Dimension |
|
| Examples |
|
Table 9-301 occnp_stale_diam_request_cleanup_total
| Field | Details |
|---|---|
| Description | This metric is pegged whenever Diameter Connector receives a Diameter request, and it is canceled either because it is already stale (late arrival request), or it has gone stale while processing it (late processing request). |
| Metric Type | Counter |
| Dimensions |
|
Table 9-302 occnp_stale_http_request_cleanup_total
| Field | Details |
|---|---|
| Description | This metric is pegged whenever Diameter Connector receives a HTTP request, and it is canceled either because it is already stale (late arrival request), or it has gone stale while processing it (late processing request). |
| Metric Type | Counter |
| Dimensions |
|
Table 9-303 diam_avp_dropped
| Field | Details |
|---|---|
| Description |
This metric is incremented when the value of
|
| Metric Type | Counter |
| Dimensions |
|
| Example |
|
For more information about Dimensions, see CNC Policy Metrics.
9.12 Diameter Gateway Metrics
The following table describes the Diameter Gateway metrics and respective dimensions:
Table 9-304 occnp_diam_conn_network
| Field | Details |
|---|---|
| Description | Tracks active diameter connections with network peers. |
| Type | Gauge |
| Dimension |
|
| Example | - |
Table 9-305 occnp_diam_conn_app_network
| Field | Details |
|---|---|
| Description | Tracks active diameter connections with network peers that support given application ID. |
| Type | Gauge |
| Dimension |
|
| Examples | - |
Example:
Table 9-306 occnp_diam_request_network_total
| Field | Details |
|---|---|
| Description | Tracks total number of request messages of given command code to or from network |
| Type | Counter |
| Dimension |
|
| Example |
|
Table 9-307 occnp_diam_response_network_total
| Field | Details |
|---|---|
| Description | Tracks total number of answer messages of given command code to or from network. |
| Type | Counter |
| Dimension |
|
| Example |
|
Table 9-308 occnp_diam_conn_local
| Field | Details |
|---|---|
| Description | Tracks active diameter connections with local services. |
| Type | Gauge |
| Dimension |
|
| Example | - |
Table 9-309 occnp_diam_conn_app_local
| Field | Details |
|---|---|
| Description |
Tracks active diameter connections with local services that support given application id. Increment this metric for each application Id supported over connection, such as intersection of application ID in CER and CEA. |
| Type | Gauge |
| Dimension |
|
| Example |
Table 9-310 occnp_diam_request_local_total
| Field | Details |
|---|---|
| Description | Tracks total number of request messages of given command code to or from local service |
| Type | Counter |
| Dimension |
|
| Examples |
|
Table 9-311 occnp_diam_response_local_total
| Field | Details |
|---|---|
| Description | Tracks total number of answer messages of given command code to or from local service. |
| Type | Counter |
| Dimension |
|
| Examples |
|
Table 9-312 occnp_diam_request_inter_total
| Field | Details |
|---|---|
| Description | Tracks total number of request messages of given command code to or from host services |
| Type | Counter |
| Dimension |
|
Table 9-313 occnp_http_out_conn_request_total
| Field | Details |
|---|---|
| Description | Total number of http connection requests. |
| Type | Counter |
| Dimension |
|
| Example | occnp_http_out_conn_request_total{operationType="read",serviceResource="Binding",service_version="v1",servicename3gpp="DiameterGateway",} 1.0 ; Type-Counter |
Table 9-314 occnp_http_out_conn_response_total
| Field | Details |
|---|---|
| Description | Total number of http connection responses. |
| Type | Counter |
| Dimension |
|
| Example | occnp_http_out_conn_response_total{latency="9",operationType="read",responseCode="2xx",serviceResource="Binding",serviceVersion="v1",servicename3gpp="DiameterGateway",} 1.0 ; Type-Counter |
Table 9-315 diam_overload_msg_reject_total
| Field | Details |
|---|---|
| Description | Total number of messages rejected due to overload control. |
| Type | Counter |
| Dimension |
|
Table 9-316 diam_controlled_shutdown_message_reject_total
| Field | Details |
|---|---|
| Description | Indicates failure count because of forced shutdown feature. |
| Type | Counter |
| Dimension |
|
| Example | diam_controlled_shutdown_message_reject_total{msgType="Gx_CCR_I",appId="16777238",cmdCode="272",destHost="",destRealm="xxxx.com",operationalState="PARTIAL_SHUTDOWN",origHost="pgw.xxxx.com",origRealm="test.example.com",responseCode="5012",} 1.0 |
Table 9-317 occnp_diam_overload_message_reject_total
| Field | Details |
|---|---|
| Description | Indicates the number of messages rejected due to overload. |
| Type | Counter |
| Dimension |
|
| Example | occnp_diam_overload_message_reject_total{appId="16777236",cmdCode="265",destHost="",destRealm="xxxx.com",msgType="request",origHost="diamcliaf.xxxx.com",origRealm="test.example.com",priority="12",responseCode="3004",} 1.0 |
Table 9-318 occnp_diam_congestion_message_reject_total
| Field | Details |
|---|---|
| Description | Indicates the number of messages rejected due to congestion. |
| Type | Counter |
| Dimension |
|
| Examples |
|
Table 9-319 topic_version
| Field | Details |
|---|---|
| Description | Describes the current applied version of a given topic (mentioned in dimension topic_name) into the pod. |
| Type | Gauge |
| Dimension |
|
Table 9-320 occnp_pod_resource_congestion_state
| Field | Details |
|---|---|
| Description | Indicates the pod congestion state. |
| Type | Gauge |
| Dimension | type |
| Examples |
|
Table 9-321 occnp_diameter_outstanding_msg_count
| Field | Details |
|---|---|
| Description | Provides an instantaneous number of outstanding diameter messages in the queue. |
| Type | Gauge |
| Dimension | NA |
| Examples | occnp_diameter_outstanding_msg_count 10.0 |
Table 9-322 occnp_diam_response_latency_seconds_count
| Field | Details |
|---|---|
| Description | Tracks latency of all outgoing requests from Diameter Gateway. This provides information on latency time for any calls made by Diameter Gateway towards any network peers or internal back end services. |
| Type | Histogram |
| Dimension |
|
| Examples |
|
Table 9-323 occnp_diam_response_latency_seconds_bucket
| Field | Details |
|---|---|
| Description | Tracks latency of all outgoing requests from Diameter Gateway. This provides information on latency time for any calls made by Diameter Gateway towards any network peers or internal back end services. |
| Type | Histogram |
| Dimension |
|
| Examples |
|
Table 9-324 occnp_diam_response_latency_seconds_sum
| Field | Details |
|---|---|
| Description | Tracks latency of all incoming requests towards Diameter Gateway. This provides an overall time tracking latency for any request towards Diameter Gateway. |
| Type | Histogram |
| Dimension |
|
| Examples |
|
Table 9-325 occnp_diam_response_latency_seconds_max
| Field | Details |
|---|---|
| Description | Tracks latency of all incoming requests towards Diameter Gateway. This provides an overall time tracking latency for any request towards Diameter Gateway. |
| Type | Histogram |
| Dimension |
|
| Examples |
|
Table 9-326 occnp_diam_service_overall_processing_time_seconds_sum
| Field | Details |
|---|---|
| Description | Tracks latency of all incoming requests towards Diameter Gateway. This provides an overall time tracking latency for any request towards Diameter Gateway. |
| Type | Histogram |
| Dimension |
|
| Examples |
|
Table 9-327 occnp_diam_service_overall_processing_time_seconds_max
| Field | Details |
|---|---|
| Description | Tracks latency of all incoming requests towards Diameter Gateway. This provides an overall time tracking latency for any request towards Diameter Gateway. |
| Type | Histogram |
| Dimension |
|
| Examples |
|
Table 9-328 occnp_diam_service_overall_processing_time_seconds_bucket
| Field | Details |
|---|---|
| Description | Tracks latency of all incoming requests towards Diameter Gateway. This provides an overall time tracking latency for any request towards Diameter Gateway. |
| Type | Histogram |
| Dimension |
|
| Examples |
|
Table 9-329 occnp_diam_service_overall_processing_time_seconds_count
| Field | Details |
|---|---|
| Description | Tracks latency of all incoming requests towards Diameter Gateway. This provides an overall time tracking latency for any request towards Diameter Gateway. |
| Type | Histogram |
| Dimension |
|
| Examples |
|
Table 9-330 occnp_diam_pending_requests
| Field | Details |
|---|---|
| Description | This tracks the total pending diameter requests. |
| Type | Gauge |
| Dimension |
|
| Examples | occnp_diam_pending_requests 1.0 |
Table 9-331 occnp_congestion_DiamMsgBuffer_queue_msg_count
| Field | Details |
|---|---|
| Description | This tracks the congestion control DiamMsgBuffer queue message count. |
| Type | Gauge |
| Dimension |
|
| Examples | occnp_congestion_DiamMsgBuffer_queue_msg_count 1.0 |
Table 9-332 occnp_congestion_diam_pending_request_end_to_end_id_map_size
| Field | Details |
|---|---|
| Description | This tracks the congestion control diameter pending requests end to end id map size. |
| Type | Gauge |
| Dimension |
|
| Examples | occnp_congestion_diam_pending_request_end_to_end_id_map_size 1.0 |
Table 9-333 occnp_congestion_diam_pending_request_active_counter
| Field | Details |
|---|---|
| Description | This tracks the current active counter for calculating pending diameter requests. |
| Type | Gauge |
| Dimension |
|
| Examples | occnp_congestion_diam_pending_request_active_counter 1.0 |
Table 9-334 occnp_ocnf_service_cookie_total
| Field | Details |
|---|---|
| Description |
The metrics with direction "IN" is pegged only when
Also, the metrics with direction "IN" is pegged when
The metrics with direction "OUT" is pegged only when OCNF-Service-Cookie customAVP is present while sending the request to destination peer. |
| Type | Counter |
| Dimension |
|
| Examples |
occnp_ocnf_service_cookie_total{direction="in",source="Binding"} 1.0 occnp_ocnf_service_cookie_total{direction="in",source="network_peer"} 1.0 occnp_ocnf_service_cookie_total{direction="out",source=""} 2.0 |
Table 9-335 occnp_context_owner_source_total
| Field | Details |
|---|---|
| Description |
This metric determines how the context owner is identified, if it is from custom AVP or by querying Binding service. When queried from Binding service, context_owner can be SM service. When context_owner_source is "ocnf-service-cookie", context_owner is SM service. |
| Type | Counter |
| Dimension |
|
| Examples |
occnp_context_owner_source_total {context_owner="PCF-SM",source="Binding"} 4.0 occnp_context_owner_source_total {context_owner="PCRF-CORE",source="Binding"} 4.0 occnp_context_owner_source_total {context_owner="PCF-SM",source="ocnf-service-cookie"} 1.0 |
Table 9-336 diam_repaving_disconnections_total
| Field | Details |
|---|---|
| Description | This metric counts the total number of connections terminated by the "force disconnect" mechanism. |
| Type | Counter |
| Dimension |
|
| Example | diam_repaving_disconnections_total{origHost="pgw.oracle.com",origRealm="oracle.com"} 1.0 |
For more information about Dimensions, seeCNC Policy Metrics.
9.13 Policy DS Metrics
The following table describes the Policy DS Service metrics and respective dimensions:
Table 9-337 client_request_total
| Field | Details |
|---|---|
| Description | Total number of client requests. |
| Type | Counter |
| Dimension |
|
| Example | client_request_total{application="policyds",operation="SEARCH",workflow="LDAP",} 1.0 ; Type-Counter |
Table 9-338 client_response_total
| Field | Details |
|---|---|
| Description | Total number of responses from the client. |
| Type | Counter |
| Dimension |
|
| Example | client_response_total{application="policyds",operation="SEARCH",response="200",workflow="LDAP",} 1.0 ; Type-Counter |
Table 9-339 server_request_total
| Field | Details |
|---|---|
| Description | Metric that increments its value each time a request
is being sent from PDS to another service.
For example: For communication with CHF task dimension is "CHF". |
| Type | Counter |
| Dimension |
|
| Examples |
|
Table 9-340 occnp_http_in_conn_processing_latency_seconds_bucket
| Field | Details |
|---|---|
| Description | This metric is used to measure the overall response time for request received from downstream components to Binding service database. |
| Type | Histogram |
| Dimensions |
|
| Example | - |
Table 9-341 occnp_http_out_conn_processing_latency_seconds_bucket
| Field | Details |
|---|---|
| Description | This metric is used to measure the overall response time for request towards upstream components to Binding service database. |
| Type | Histogram |
| Dimensions |
|
| Example | - |
Table 9-342 server_response_total
| Field | Details |
|---|---|
| Description |
Metric that increments its value each time a response is being received from a request that PDS sent to another service. For example: For communication with CHF task dimension is "CHF". Response dimension specifies the response of the request (200, 500, 400, etc) |
| Type | Counter |
| Dimension |
|
| Example |
|
Table 9-343 revalidation_request_total
| Field | Details |
|---|---|
| Description | This metric is incremented when the revalidation is required for a datasource. It is also incremented when revalidation for a subscription failed with 404 but reattempt is done for the request. |
| Type | Counter |
| Dimension |
|
| Examples |
|
Table 9-344 revalidation_response_total
| Field | Details |
|---|---|
| Description | This metric is incremented when any of the following
responses are received for revalidation request:
Note: You can identify the exact cause
with the |
| Type | Counter |
| Dimension |
|
| Examples |
|
Table 9-345 topic_version
| Field | Details |
|---|---|
| Description | Describes the current applied version of a given topic (mentioned in dimension topic_name) into the pod. |
| Type | Gauge |
| Dimension |
|
Table 9-346 occnp_error_handler_in_total
| Field | Details |
|---|---|
| Description | This metric is incremented on initialization of error handling. |
| Type | Counter |
| Dimension |
|
| Example | occnp_error_handler_in_total{application="policyds",application_exception="HttpException",wrapped_exception="TimeoutException",} 1.0 |
Table 9-347 occnp_error_handler_exec_total
| Field | Details |
|---|---|
| Description | This metric is incremented on error handling performed by framework. |
| Type | Counter |
| Dimension |
|
| Example | occnp_error_handler_exec_total{application="policyds",application_exception="HttpException",error_type="INTERNAL",operation="LOOKUP",origin="HTTP",rule_name="HTTP_REQUEST",source_interface="POLICY",status="502",target_interface="BSF",wrapped_exception="BadGateway",} 1.0 |
Table 9-348 occnp_error_handler_out_total
| Field | Details |
|---|---|
| Description | This metric is incremented on completion of error handling. |
| Type | Counter |
| Dimension |
|
| Example | occnp_error_handler_out_total{application="policyds",application_exception="HttpException",error_resolved="true",wrapped_exception="ServiceUnavailable",} 1.0 |
Table 9-349 occnp_policyds_overall_processing_time_seconds
| Field | Details |
|---|---|
| Description | Policy DS service overall processing
time.
Note: Default name used when there is no custom name available is data_repository_invocations. |
| Type | Summary |
| Dimension |
|
Table 9-350 occnp_policyds_overall_processing_time_seconds_max
| Field | Details |
|---|---|
| Description | Diameter Connector service overall processing time. |
| Type | Gauge |
| Dimension |
|
Table 9-351 occnp_policyds_overall_processing_time_seconds_count
| Field | Details |
|---|---|
| Description | Diameter Connector service overall processing time. |
| Type | Counter |
| Dimension |
|
Table 9-352 occnp_policyds_overall_processing_time_seconds_sum
| Field | Details |
|---|---|
| Description | Diameter Connector service overall processing time. |
| Type | Counter |
| Dimension |
|
| Examples | error_handler_out_total{application="policyds",application_exception="HttpException",error_resolved="true",wrapped_exception="BadRequest",} 1.0 |
Table 9-353 occnp_nf_cookie_forwarded_total
| Field | Details |
|---|---|
| Description | This metric is incremented every time a NF profile cookie is forwarded from PDS. |
| Type | Counter |
| Dimension |
|
| Example | occnp_nf_cookie_forwarded_total{application="policyds,"task="UDR",vendorId="Oracle"} 1.0 ; |
Table 9-354 occnp_nf_cookie_recieved_total
| Field | Details |
|---|---|
| Description | This metric is incremented every time a NF profile cookie is received from PDS. |
| Type | Counter |
| Dimension |
|
| Example | occnp_nf_cookie_recieved_total{application="policyds,task="UDR",vendorId="Oracle"} 1.0 ; |
Table 9-355 data_repository_invocations_seconds_max
| Field | Details |
|---|---|
| Description | This metric is used to track the maximum execution time of Data repository invocations. It is a useful metric for monitoring the performance of data repositories and identifying slow-running queries. |
| Type | Gauge |
| Dimension |
|
| Example | data_repository_invocations_seconds_max{app_kubernetes_io_instance="ocbsf", app_kubernetes_io_managed_by="Helm", app_kubernetes_io_name="audit-service", app_kubernetes_io_part_of="ocbsf", app_kubernetes_io_version="1.0.0.0", application="ocbsf", container="audit-service", endpoint="cnc-metrics", engVersion="24.1.4", exception="None", helm_sh_chart="audit-service-24.1.4", instance="10.233.127.211:9000", io_kompose_service="ocbsf-ocpm-audit-service", job="occne-infra/occne-nf-cnc-podmonitor", method="getQueuedTablesToAudit", microservice="ocbsf-audit", mktgVersion="1.0.0.0", namespace="ocbsf", pod="ocbsf-ocpm-audit-service-6b6f85f7b9-nmzr4", pod_template_hash="6b6f85f7b9", repository="AuditSchedulerRepository", security_istio_io_tlsMode="istio", service_istio_io_canonical_name="audit-service", service_istio_io_canonical_revision="1.0.0.0", state="SUCCESS", vendor="Oracle"} |
Table 9-356 data_repository_invocations_seconds_sum
| Field | Details |
|---|---|
| Description |
The seconds_sum metric for Data repository invocations is a measure of the total time spent executing repository methods. |
| Type | Gauge |
| Dimension |
|
| Example | data_repository_invocations_seconds_sum{app_kubernetes_io_instance="ocbsf", app_kubernetes_io_managed_by="Helm", app_kubernetes_io_name="audit-service", app_kubernetes_io_part_of="ocbsf", app_kubernetes_io_version="1.0.0.0", application="ocbsf", container="audit-service", endpoint="cnc-metrics", engVersion="24.1.4", exception="None", helm_sh_chart="audit-service-24.1.4", instance="10.233.84.88:9000", io_kompose_service="ocbsf-ocpm-audit-service", job="occne-infra/occne-nf-cnc-podmonitor", method="getQueuedTablesToAudit", microservice="ocbsf-audit", mktgVersion="1.0.0.0", namespace="ocbsf", pod="ocbsf-ocpm-audit-service-6b6f85f7b9-nshv9", pod_template_hash="6b6f85f7b9", repository="AuditSchedulerRepository", security_istio_io_tlsMode="istio", service_istio_io_canonical_name="audit-service", service_istio_io_canonical_revision="1.0.0.0", state="SUCCESS", vendor="Oracle"} |
Table 9-357 data_repository_invocations_seconds_count
| Field | Details |
|---|---|
| Description |
This metric measures the total time spent in Data JPA repository invocations. It is a counter metric, which means that it increments each time a repository method is invoked. The metric is reported in seconds. |
| Type | Counter |
| Dimension |
|
| Example | data_repository_invocations_seconds_count{app_kubernetes_io_instance="ocbsf", app_kubernetes_io_managed_by="Helm", app_kubernetes_io_name="audit-service", app_kubernetes_io_part_of="ocbsf", app_kubernetes_io_version="1.0.0.0", application="ocbsf", container="audit-service", endpoint="cnc-metrics", engVersion="24.1.4", exception="None", helm_sh_chart="audit-service-24.1.4", instance="10.233.127.211:9000", io_kompose_service="ocbsf-ocpm-audit-service", job="occne-infra/occne-nf-cnc-podmonitor", method="findAll", microservice="ocbsf-audit", mktgVersion="1.0.0.0", namespace="ocbsf", pod="ocbsf-ocpm-audit-service-6b6f85f7b9-nmzr4", pod_template_hash="6b6f85f7b9", repository="AuditRegistrationsRepository", security_istio_io_tlsMode="istio", service_istio_io_canonical_name="audit-service", service_istio_io_canonical_revision="1.0.0.0", state="SUCCESS", vendor="Oracle"} |
Table 9-358 create_context_on_failure_response
| Field | Details |
|---|---|
| Description | This metrics increments on receiving failure response from its respective data source and that has createContextOnFailure set to true in the request. |
| Metric Type | Counter |
| Dimensions |
|
| Example | - |
Table 9-359 occnp_db_processing_latency_seconds_count
| Field | Details |
|---|---|
| Description | This metric is used to measure the overall response time for requested DB operations. |
| Type | Histogram |
| Dimension |
|
| Example |
occnp_db_processing_latency_seconds_count{application="policyds",inOperationType="SEARCH", inUri="/pds/v2/user-data",method="findSubscriberDataByProfileId", primary_key_combination="NA", responseCause="", responseCode="success", sourceOperationType="", sourceUri="", tableName="pdssubscriber", type_of_search="MULTI_UE_ID_SEARCH",} 2.0 occnp_db_processing_latency_seconds_count{application="policyds",inOperationType="SEARCH", inUri="/pds/v2/user-data", method="deleteSubscribers", primary_key_combination="NA", responseCause="", responseCode="success", sourceOperationType="", sourceUri="", tableName="pdssubscriber", type_of_search="MULTI_UE_ID_SEARCH",} 2.0 |
Table 9-360 pds_location_info_db_search_total
| Field | Details |
|---|---|
| Description | This metric is used to monitor the DB queries using the primary key lookup. The metrics also monitors the queries, doing DB lookup using a index column in case of primary key lookup failure. |
| Type | Counter |
| Dimension |
|
| Example |
|
Table 9-361 task_count_total
| Field | Details |
|---|---|
| Description | This metric is used to monitor the number of times the tasks were executed for a specific workflow. |
| Type | Counter |
| Dimension |
|
| Example |
|
Table 9-362 task_processing_latency_sum_total
| Field | Details |
|---|---|
| Description | This metric is used to monitor the total time spent on executing a task for a given workflow. |
| Type | Gauge |
| Dimension |
|
| Example |
|
Table 9-363 occnp_policy_data_subscription_expiry_status_total
| Field | Details |
|---|---|
| Description | This metric is used to monitor the status of the UDR data subscription. |
| Type | Counter |
| Dimension |
|
| Example | {application="policyds",contextOwner="PCF_SM",expiryStatus="PRE_EXPIRY",hostname="policy-ocpm-policyds-748fbc8d55-gcm4c",sourceType="operatorSpecificData"} 3.0 |
Table 9-364 occnp_policy_data_resubscription_request_total
| Field | Details |
|---|---|
| Description | This metric is used to monitor the resubscription request sent from PDS. |
| Type | Counter |
| Dimension |
|
| Example | {action="RESUBSCRIBE",application="policyds",expiryStatus="PRE_EXPIRY",hostname="policy-ocpm-policyds-748fbc8d55-gcm4c",sourceType="OperatorSpecificData"} 3.0 |
Table 9-365 occnp_policy_data_resubscription_response_total
| Field | Details |
|---|---|
| Description | This metric is used to monitor the resubscription response[success/failure] received at PDS. |
| Type | Counter |
| Dimension |
|
| Example | {action="DELETE",application="policyds",expiryStatus="PRE_EXPIRY",hostname="policy-ocpm-policyds-748fbc8d55-gcm4c",response="404",sourceType="OperatorSpecificData"} 2.0 |
Table 9-366 occnp_audit_notifications_total
| Field | Details |
|---|---|
| Description | This metric is used to retrieve the total number of audit requests received by PDS. |
| Type | Counter |
| Dimension |
|
| Example |
occnp_audit_notifications_total{application="policyds",contextOwner="AUDIT", method="NOTIFY",workflow="AUDIT-SUBSCRIBER-CLEANUP"} 71.0 |
For more information about Dimensions, see CNC Policy Metrics.
9.14 LDAP Gateway
The following table describes the LDAP Gateway Service metrics and respective dimensions:
Table 9-367 ldap_request_total
| Field | Details |
|---|---|
| Description | Indicates the total number of LDAP requests. |
| Type | Counter |
| Dimension |
|
| Example | ldap_request_total{ReqType="GET",application="ldapgateway",hostname="policy-ocpm-ldap-gateway-794f856db6-2w8gr",} 10.0 ; Type-Counter |
Table 9-368 ldap_response_total
| Field | Details |
|---|---|
| Description | Indicates the total number of LDAP responses. |
| Type | Counter |
| Dimension |
|
| Examples |
|
Table 9-369 occnp_ldap_search_request_total
| Field | Details |
|---|---|
| Description | Indicates the total number of LDAP search requests. |
| Type | Counter |
| Dimension |
|
| Example |
|
Table 9-370 occnp_ldap_search_response_total
| Field | Details |
|---|---|
| Description | Indicates the total number of LDAP search responses. |
| Type | Counter |
| Dimension |
|
| Example |
|
Table 9-371 occnp_ldap_conn_total
| Field | Details |
|---|---|
| Description | This metric is used to monitor and track the number of active connections between the LDAP Gateway and its configured LDAP servers. It provides greater visibility into the connectivity status and helps in identifying issues related to LDAP server availability. |
| Type | Gauge |
| Dimension |
|
| Example |
|
Table 9-372 http_server_requests_seconds_count
| Field | Details |
|---|---|
| Description | Number of http request received. |
| Type | Counter |
| Dimension |
|
| Example | http_server_requests_seconds_count{exception="None",method="GET",outcome="SUCCESS",status="200",uri="/pcrfSessionData",} 2.0 |
Table 9-373 http_server_requests_seconds_max
| Field | Details |
|---|---|
| Description | Maximum number of http requests received. |
| Type | Counter |
| Dimension |
|
| Example | http_server_requests_seconds_max{exception="None",method="GET",outcome="SUCCESS",status="200",uri="/pcrfSessionData",} 0.0 |
For more information about Dimensions, see CNC Policy Metrics.
9.15 Binding Service Metrics
The following table describes the Binding Service metrics and respective dimensions:
Table 9-374 ocpm_binding_inbound_request_total
| Field | Details |
|---|---|
| Description | Total number of inbound requests. |
| Type | Counter |
| Dimension |
|
| Examples |
|
Table 9-375 ocpm_egress_request_total
| Field | Details |
|---|---|
| Description | Total number of egress requests. |
| Type | Counter |
| Dimension |
|
| Example | - |
Table 9-376 ocpm_egress_response_total
| Field | Details |
|---|---|
| Description | Total number of egress responses. |
| Type | Counter |
| Dimension |
|
| Example | - |
Table 9-377 ocpm_binding_inbound_response_total
| Field | Details |
|---|---|
| Description | Total number of inbound responses. |
| Type | Counter |
| Dimension |
|
| Examples |
|
Table 9-378 occnp_binding_query_request_count
| Field | Details |
|---|---|
| Description | This metric tracks the total number of Audit Notify requests received from BSF. |
| Type | Counter |
| Dimension |
|
| Example | occnp_binding_query_request_count_total{ingress_service="",operation_type="AuditNotify",servicename_3gpp="binding",} 1.0 |
Table 9-379 occnp_binding_query_response_count
| Field | Details |
|---|---|
| Description | This metric tracks the total number of successful responses sent to BSF for Audit Notify requests. |
| Type | Counter |
| Dimension |
|
| Example | occnp_binding_query_response_count_total{ingress_service="",operation_type="AuditNotify",response_code="2xx",servicename_3gpp="binding",} 1.0 |
Table 9-380 occnp_audit_notif_request_count_total
| Field | Details |
|---|---|
| Description | The total number of audit notification requests received by binding service. |
| Type | Counter |
| Dimension |
|
| Example | occnp_audit_notif_request_count_total{nfInstanceId="fe7d992b-0541-4c7d-ab84-c6d70b1b0123",servicename_3gpp="binding",} 1.0 ; Type-Counter |
Table 9-381 occnp_audit_notif_response_count_total
| Field | Details |
|---|---|
| Description | The total number of responses sent by binding service for audit notifications. |
| Type | Counter |
| Dimension |
|
| Example | occnp_audit_notif_response_count_total{nfInstanceId="fe7d992b-0541-4c7d-ab84-c6d70b1b0123",response_code="2xx",servicename_3gpp="binding",} 1.0 ; Type-Counter |
Table 9-382 occnp_stale_session_cleanup_count_total
| Field | Details |
|---|---|
| Description | Total number of records deleted from the binding database by the stale session clean up process. |
| Type | Counter |
| Dimension |
|
| Example | occnp_stale_session_cleanup_count_total{servicename_3gpp="binding",sessionType="dependentcontextbinding",} 1.0 ; Type-Counter |
Table 9-383 topic_version
| Field | Details |
|---|---|
| Description | Describes the current applied version of a given topic (mentioned in dimension topic_name) into the pod. |
| Type | Gauge |
| Dimension |
|
| Example | - |
Table 9-384 occnp_binding_service_overall_processing_time_seconds
| Field | Details |
|---|---|
| Description | Binding service overall processing time. |
| Type | Summary |
| Dimension |
|
| Example | - |
Table 9-385 occnp_binding_service_overall_processing_time_seconds_max
| Field | Details |
|---|---|
| Description | Binding service overall processing time. |
| Type | Gauge |
| Dimension |
|
| Examples |
|
Table 9-386 occnp_binding_service_overall_processing_time_seconds_count
| Field | Details |
|---|---|
| Description | Binding service overall processing time. |
| Type | Counter |
| Dimension |
|
| Examples |
|
Table 9-387 occnp_binding_service_overall_processing_time_seconds_sum
| Field | Details |
|---|---|
| Description | Binding service overall processing time. |
| Type | Counter |
| Dimension |
|
| Examples |
|
Table 9-388 occnp_bindingservice_db_operation_time_seconds_count
| Field | Details |
|---|---|
| Description | Binding service overall database processing time. |
| Type | Gauge |
| Dimension |
|
| Examples |
|
Table 9-389 occnp_bindingservice_db_operation_time_seconds_sum
| Field | Details |
|---|---|
| Description | Binding service overall database processing time. |
| Type | Gauge |
| Dimension |
|
| Examples |
|
Table 9-390 occnp_bindingservice_db_operation_time_seconds_max
| Field | Details |
|---|---|
| Description | Binding service overall database processing time. |
| Type | Gauge |
| Dimension |
|
Table 9-391 ocpm_egress_request_timeout_total
| Field | Details |
|---|---|
| Description | Binding service overall database processing time. |
| Type | Gauge |
| Dimension |
|
| Examples |
|
Table 9-392 occnp_stale_session_cleanup_internal_queue_size
| Field | Details |
|---|---|
| Description | Binding session stale internal queue size. |
| Type | Gauge |
| Dimension | servicename_3gpp |
| Example | occnp_stale_session_cleanup_internal_queue_size{servicename_3gpp="binding",} 2.0; Type-Gauge |
Table 9-393 occnp_audit_delete_record_count_total
| Field | Details |
|---|---|
| Description | This metric is used to monitor records deleted in binding by Audit Service. |
| Type | Counter |
| Dimension |
|
| Examples |
occnp_audit_delete_record_count{max_ttl_reached="true",nfInstanceId="fe7d992b-0541-4c7d-ab84-c6d70b1b0123",servicename_3gpp="binding",sessionType="contextbinding",}2.0 |
Table 9-394 occnp_error_handler_in_total
| Field | Details |
|---|---|
| Description | This metric is incremented on initialization of error handling. |
| Type | Counter |
| Dimensions |
|
| Example | occnp_error_handler_in_total{application_exception="JavaException",status="500",wrapped_exception="ServiceException",} 1.0 |
Table 9-395 occnp_error_handler_exec_total
| Field | Details |
|---|---|
| Description | This metric is incremented on error handling performed by framework. |
| Type | Counter |
| Dimensions |
|
| Example | occnp_error_handler_exec_total{application_exception="JavaException",error_type="INTERNAL",operation="AUDIT",origin="JAVA",rule_name="REJECT_WITH_ENHANCED_DETAIL",source_interface="BSF",status="404",target_interface="POLICY",wrapped_exception="ServiceException",} 1.0 |
Table 9-396 occnp_error_handler_out_total
| Field | Details |
|---|---|
| Description | This metric is incremented on completion of error handling. |
| Type | Counter |
| Dimensions |
|
| Example | occnp_error_handler_out_total{application_exception="JavaException",error_resolved="true",status="404",wrapped_exception="ServiceException",} 1.0 |
Table 9-397 occnp_late_arrival_rejection_total
| Field | Details |
|---|---|
| Description | This metric is pegged whenever Binding service receives a request and it gets rejected at the moment that the request is received (before doing any time consuming operations) because it is already stale. |
| Type | Counter |
| Dimensions |
|
| Example | - |
Table 9-398 occnp_late_processing_rejection_total
| Field | Details |
|---|---|
| Description | This metric is pegged whenever Binding service receives a request and it gets rejected after doing time consuming operation (DB operations or requests to BSF) because it is already stale. |
| Type | Counter |
| Dimensions |
|
| Example | - |
Table 9-399 occnp_session_binding_revalidation_request_total
| Field | Details |
|---|---|
| Description | During revalidation, when Policy performs audit check of the binding association returns and sends POST request to BSF, Policy increments metrics with details of DNN, snssai, PCF FQDN. |
| Type | Counter |
| Dimensions |
|
| Example | - |
Table 9-400 occnp_session_binding_revalidation_response_total
| Field | Details |
|---|---|
| Description | During revalidation, when Policy receives response from BSF, Policy increments metrics with details of DNN, snssai, PCF FQDN, responseCode, and action. For example: If BSF returns 201, responseCode=201 and if the return binding_id is a the same as it was before the revalidation, then the action= "found". If the return binding_id is a new one, action="restored". |
| Type | Counter |
| Dimensions |
|
| Example | - |
Table 9-401 occnp_db_processing_latency_seconds
| Field | Details |
|---|---|
| Description | This metric is used to measure the overall response time for the requested Binding service database operations. |
| Type | Histogram |
| Dimensions |
|
| Example | - |
Table 9-402 occnp_http_in_conn_processing_latency_seconds_bucket
| Field | Details |
|---|---|
| Description | This metric is used to measure the overall response time for request received from downstream components to Binding service database. |
| Type | Histogram |
| Dimensions |
|
| Example | - |
Table 9-403 occnp_http_out_conn_processing_latency_seconds_bucket
| Field | Details |
|---|---|
| Description | This metric is used to measure the overall response time for request towards upstream components to Binding service database. |
| Type | Histogram |
| Dimensions |
|
| Example | - |
Table 9-404 occnp_binding_index_restore_total
| Field | Details |
|---|---|
| Description |
When data is migrated to the Index restoration applies only to records that are successfully migrated in the |
| Type | Counter |
| Dimensions |
|
| Example |
occnp_binding_index_restore_total{indexed_key="supi"} 1.0 occnp_binding_index_restore_total{indexed_key="gpsi"} 1.0 occnp_binding_index_restore_total{indexed_key="ipv4Addr"} 1.0 occnp_binding_index_restore_total{indexed_key="ipv6Prefix"} 1.0 |
Table 9-405 occnp_binding_index_total
| Field | Details |
|---|---|
| Description | This metric counts the number of times index migration was attempted on audit notification.
Note: Currently this metric is pegged only during audit notification. |
| Type | Counter |
| Dimensions |
|
| Example |
occnp_binding_index_total{error="SQLGrammarException",operation_type="AUDIT"} 1.0 occnp_binding_index_total{error="none",operation_type="AUDIT"} 1.0 |
For more information about Dimensions, see CNC Policy Metrics.
9.16 Audit Service Metrics
The following table describes the Audit Service metrics and respective dimensions:
Table 9-406 audit_recs_stale_total
| Field | Details |
|---|---|
| Description | Number of records detected as stale. |
| Type | Counter |
| Dimension |
|
| Example | audit_recs_stale_total{ServiceName="pcf-ueservice",TableName="UePolicyAssociation",} 1.0 |
Table 9-407 audit_recs_notif_total
| Field | Details |
|---|---|
| Description | Number of stale record notifications sent, applicable for modes: NOTIFY and DELETE_NOTIFY |
| Type | Counter |
| Dimension |
ServiceName |
| Examples |
|
Table 9-408 audit_recs_remv_total
| Field | Details |
|---|---|
| Description | Number of stale records deleted, applicable for modes: DELETE and DELETE_NOTIFY. |
| Type | Counter |
| Dimension |
|
| Example | audit_recs_remv_total{ServiceName="sm-service",TableName="SmPolicyAssociation"} 5.0 ; Type-Counter |
Table 9-409 audit_recs_remv_ex_total
| Field | Details |
|---|---|
| Description | Number of exceptions hit during attempt to delete a stale record. |
| Type | Counter |
| Dimension |
|
| Example | audit_recs_remv_ex_total{ServiceName="sm-service",TableName="SmPolicyAssociation"} 0.0 ; Type-Counter |
Table 9-410 audit_recs_notif_ex_total
| Field | Details |
|---|---|
| Description | Number of exceptions hit during attempt to notify. |
| Type | Counter |
| Dimension |
ServiceName |
| Example | audit_recs_notif_ex_total{ServiceName="sm-service"} 0.0 ; |
Table 9-411 audit_recs_notif_err_total
| Field | Details |
|---|---|
| Description | Number of error responses received for notifications sent. |
| Type | Counter |
| Dimension | ServiceName |
| Example | audit_recs_notif_err_total{ServiceName="sm-service"} 13.0 ; Type-Counter |
Table 9-412 audit_recs_deque_for_notif_total
| Field | Details |
|---|---|
| Description | Number of stale records dequeued to send notification. |
| Type | Counter |
| Dimension | ServiceName |
| Example | audit_recs_deque_for_notif_total{ServiceName="pcf-ueservice",} 1.0 |
Table 9-413 audit_recs_enque_for_notif_total
| Field | Details |
|---|---|
| Description | Number of stale records enqueued from database. |
| Type | Counter |
| Dimension | ServiceName |
| Example | audit_recs_enque_for_notif_total{ServiceName="pcf-ueservice",} 1.0 |
Table 9-414 audit_recs_enque_err_total
| Field | Details |
|---|---|
| Description | Number of stale records failed to enqueue if Queue is full. |
| Type | Counter |
| Dimension | ServiceName |
| Example | audit_recs_enque_err_total{ServiceName="sm-service"} 0.0 ; Type-Counter |
Table 9-415 oc_db_active_session_count
| Field | Details |
|---|---|
| Description | Reports the session for a given service e.g. SM session. |
| Type | Gauge |
| Dimension |
|
| Examples |
|
Table 9-416 occnp_pending_binding_reattempts_total
| Field | Details |
|---|---|
| Description | Indicates when a attempt to recreate has been triggered by PCF. |
| Type | Counter |
| Dimension | Attempt |
Table 9-417 data_repository_invocations_seconds_max
| Field | Details |
|---|---|
| Description | This metric is used to track the maximum execution time of Data repository invocations. It is a useful metric for monitoring the performance of data repositories and identifying slow-running queries. |
| Type | Gauge |
| Dimension |
|
| Example | data_repository_invocations_seconds_max{app_kubernetes_io_instance="ocbsf", app_kubernetes_io_managed_by="Helm", app_kubernetes_io_name="audit-service", app_kubernetes_io_part_of="ocbsf", app_kubernetes_io_version="1.0.0.0", application="ocbsf", container="audit-service", endpoint="cnc-metrics", engVersion="24.1.4", exception="None", helm_sh_chart="audit-service-24.1.4", instance="10.233.127.211:9000", io_kompose_service="ocbsf-ocpm-audit-service", job="occne-infra/occne-nf-cnc-podmonitor", method="getQueuedTablesToAudit", microservice="ocbsf-audit", mktgVersion="1.0.0.0", namespace="ocbsf", pod="ocbsf-ocpm-audit-service-6b6f85f7b9-nmzr4", pod_template_hash="6b6f85f7b9", repository="AuditSchedulerRepository", security_istio_io_tlsMode="istio", service_istio_io_canonical_name="audit-service", service_istio_io_canonical_revision="1.0.0.0", state="SUCCESS", vendor="Oracle"} |
Table 9-418 data_repository_invocations_seconds_sum
| Field | Details |
|---|---|
| Description |
The seconds_sum metric for Data repository invocations is a measure of the total time spent executing repository methods. |
| Type | Gauge |
| Dimension |
|
| Example | data_repository_invocations_seconds_sum{app_kubernetes_io_instance="ocbsf", app_kubernetes_io_managed_by="Helm", app_kubernetes_io_name="audit-service", app_kubernetes_io_part_of="ocbsf", app_kubernetes_io_version="1.0.0.0", application="ocbsf", container="audit-service", endpoint="cnc-metrics", engVersion="24.1.4", exception="None", helm_sh_chart="audit-service-24.1.4", instance="10.233.84.88:9000", io_kompose_service="ocbsf-ocpm-audit-service", job="occne-infra/occne-nf-cnc-podmonitor", method="getQueuedTablesToAudit", microservice="ocbsf-audit", mktgVersion="1.0.0.0", namespace="ocbsf", pod="ocbsf-ocpm-audit-service-6b6f85f7b9-nshv9", pod_template_hash="6b6f85f7b9", repository="AuditSchedulerRepository", security_istio_io_tlsMode="istio", service_istio_io_canonical_name="audit-service", service_istio_io_canonical_revision="1.0.0.0", state="SUCCESS", vendor="Oracle"} |
Table 9-419 data_repository_invocations_seconds_count
| Field | Details |
|---|---|
| Description |
This metric measures the total time spent in Data JPA repository invocations. It is a counter metric, which means that it increments each time a repository method is invoked. The metric is reported in seconds. |
| Type | Counter |
| Dimension |
|
| Example | data_repository_invocations_seconds_count{app_kubernetes_io_instance="ocbsf", app_kubernetes_io_managed_by="Helm", app_kubernetes_io_name="audit-service", app_kubernetes_io_part_of="ocbsf", app_kubernetes_io_version="1.0.0.0", application="ocbsf", container="audit-service", endpoint="cnc-metrics", engVersion="24.1.4", exception="None", helm_sh_chart="audit-service-24.1.4", instance="10.233.127.211:9000", io_kompose_service="ocbsf-ocpm-audit-service", job="occne-infra/occne-nf-cnc-podmonitor", method="findAll", microservice="ocbsf-audit", mktgVersion="1.0.0.0", namespace="ocbsf", pod="ocbsf-ocpm-audit-service-6b6f85f7b9-nmzr4", pod_template_hash="6b6f85f7b9", repository="AuditRegistrationsRepository", security_istio_io_tlsMode="istio", service_istio_io_canonical_name="audit-service", service_istio_io_canonical_revision="1.0.0.0", state="SUCCESS", vendor="Oracle"} |
Table 9-420 occnp_pending_binding_terminate_all_attempts_failed_total
| Field | Details |
|---|---|
| Description | Indicates when session terminate has been triggered when all recreate attempts fail. |
| Type | Counter |
| Dimension |
|
Table 9-421 occnp_pending_binding_reattempt_fail_total
| Field | Details |
|---|---|
| Description | Indicates when each recreate attempt fail. |
| Type | Counter |
| Dimension | NA |
Table 9-422 occnp_pending_operation_threshold_reached_total
| Field | Details |
|---|---|
| Description | Indicates when pending operation table threshold has been reached. |
| Type | Counter |
| Dimension | NA |
Table 9-423 occnp_reject_sm_create_threshold_reached_total
| Field | Details |
|---|---|
| Description | Indicates when SM rejects SM CREATE when pending operation threshold has been reached. |
| Type | Counter |
| Dimension |
|
Table 9-424 occnp_pending_operation_records_count
| Field | Details |
|---|---|
| Description | Indicates the amount of entries in the PendingOperation table. |
| Type | Gauge |
| Dimension | NA |
Table 9-425 topic_version
| Field | Details |
|---|---|
| Description | Describes the current applied version of a given topic (mentioned in dimension topic_name) into the pod. |
| Type | Gauge |
| Dimension |
|
Table 9-426 occnp_timer_count_total
| Field | Details |
|---|---|
| Description | This metrics indicates the number of timers and their states. |
| Type | Counter |
| Dimension |
|
Table 9-427 occnp_timer_capacity
| Field | Details |
|---|---|
| Description | This Gauge metrics tracks the number of metrics for timerName. |
| Type | Gauge |
| Dimension |
|
Table 9-428 occnp_timer_scan_total
| Field | Details |
|---|---|
| Description | This metric tracks timer scan and the state. |
| Type | Counter |
| Dimension |
|
Table 9-429 occnp_timer_registration_total
| Field | Details |
|---|---|
| Description | This metric indicates number of timer registrations. |
| Type | Counter |
| Dimension |
|
Table 9-430 occnp_timer_create_failure_total
| Field | Details |
|---|---|
| Description | This metric tracks timer create failure corresponding
to timerName with error cause and code.
|
| Type | Counter |
| Dimension |
|
Table 9-431 occnp_timer_notify_retry_total
| Field | Details |
|---|---|
| Description | This metric tracks counter metrics to track timer notification retries. |
| Type | Counter |
| Dimension |
|
Table 9-432 occnp_timer_state
| Field | Details |
|---|---|
| Description | This gauge metrics is used to track timer in stuck, stale and scheduled state in each scan. |
| Type | Gauge |
| Dimension |
|
Table 9-433 occnp_timer_scan_activity_total
| Field | Details |
|---|---|
| Description | This metric is incremented each time a particular timer activity runs. |
| Type | Counter |
| Dimension |
|
Table 9-434 audit_schedule_current_status
| Field | Details |
|---|---|
| Description | This metric defines status of the current audit schedule. This metric is set to 1, if the status is the current audit schedule is "CTRL_SHUTDOWN_INTRPT". This metric is reset to 0, if the status is changed. |
| Type | Gauge |
| Dimension |
|
| Example | audit_schedule_current_status{Service="pcrf-core", Status="CTRL_SHUTDOWN_INTRPT", Table="rxsession", app_kubernetes_io_instance="conv", app_kubernetes_io_managed_by="Helm", app_kubernetes_io_name="audit-service", app_kubernetes_io_part_of="occnp", app_kubernetes_io_version="25.2.100-rc.8.0.0", application="occnp", container="audit-service", endpoint="cnc-metrics", engVersion="25.2.100-rc.8", helm_sh_chart="audit-service-25.2.100-rc.8", instance="10.233.97.19:9000", io_kompose_service="conv-ocpm-audit-service", job="occne-infra/occne-nf-cnc-podmonitor", microservice="occnp-audit", mktgVersion="25.2.100-rc.8.0.0", namespace="ch2-ns13", pod="conv-ocpm-audit-service-68999b77f4-2tnxp", pod_template_hash="68999b77f4", vendor="Oracle"} |
Table 9-435 occnp_audit_schedule_status_total
| Field | Details |
|---|---|
| Description | This metric indicated the number of times the audit service has transitioned its status for a specific service and table. |
| Type | Counter |
| Dimension |
|
| Example | occnp_audit_schedule_status_total{Service="pcrf-core", Status="COMPLETED", Table="gxsession", app_kubernetes_io_instance="conv", app_kubernetes_io_managed_by="Helm", app_kubernetes_io_name="audit-service", app_kubernetes_io_part_of="occnp", app_kubernetes_io_version="25.2.100-rc.8.0.0", application="occnp", container="audit-service", endpoint="cnc-metrics", engVersion="25.2.100-rc.8", helm_sh_chart="audit-service-25.2.100-rc.8", instance="10.233.97.19:9000", io_kompose_service="conv-ocpm-audit-service", job="occne-infra/occne-nf-cnc-podmonitor", microservice="occnp-audit", mktgVersion="25.2.100-rc.8.0.0", namespace="ch2-ns13", pod="conv-ocpm-audit-service-68999b77f4-2tnxp", pod_template_hash="68999b77f4", vendor="Oracle"} |
For more information about Dimensions, see CNC Policy Metrics.
9.17 Query Service Metrics
The following table describes the Query Service metrics and respective dimensions:
Table 9-436 queryservice_sessionDelete_request_total
| Field | Details |
|---|---|
| Description | Total number of delete SM service query requests. |
| Type | Counter |
| Dimension |
|
| Examples |
|
Table 9-437 queryservice_sessionDelete_response_total
| Field | Details |
|---|---|
| Description | Total number of responses for delete SM service query. |
| Type | Counter |
| Dimension |
|
| Examples |
|
For more information about Dimensions, see CNC Policy Metrics.
9.18 AppInfo Metrics
This section describes the metrics and examples for AppInfo service.
Table 9-438 appinfo_service_running-
| Field | Details |
|---|---|
| Description | Provides the status of monitored services. |
| Type | Gauge |
| Dimension |
|
| Example | appinfo_service_running{service="xxx",namespace="xxx",category="xxx"} 1 |
Table 9-439 appinfo_category_running
| Field | Details |
|---|---|
| Description | Provides the status of monitored categories |
| Type | Gauge |
| Dimension |
|
| Example | appinfo_category_running{category="xxx",namespace="xxx"} 1 |
Table 9-440 appinfo_category_good
| Field | Details |
|---|---|
| Description | Provides the readiness of monitored categories. |
| Type | Gauge |
| Dimension |
|
| Example | appinfo_category_good{category="xxx",namespace="xxx"} 1 |
Table 9-441 nfscore
| Field | Details |
|---|---|
| Description |
factor:
status:
|
| Type | Gauge |
| Dimension |
|
| Example | nfscore{app="testing-appinfo", app_kubernetes_io_instance="testing", app_kubernetes_io_managed_by="Helm", app_kubernetes_io_name="appinfo", app_kubernetes_io_part_of="ocbsf", app_kubernetes_io_version="1.7.1.0.0", application="ocbsf", calculatedStatus="success", container="appinfo", endpoint="cnc-metrics", engVersion="22.4.0", factor="localityPreference", helm_sh_chart="appinfo-22.4.0", instance="10.233.117.146:9000", job="occne-infra/occne-nf-cnc-podmonitor", microservice="bsf-app-info", mktgVersion="1.7.1.0.0", namespace="biloxi-ns", nfInstanceID="fe7d992b-0541-4c7d-ab84-c6d70b1b0666", pod="testing-appinfo-78dc65865f-hgrhk", pod_template_hash="78dc65865f", vendor="Oracle"} 5 |
Table 9-442 nfScoringFactorActualValue
| Field | Details |
|---|---|
| Description | The factor tag would contain one of the following values: successTPS, serviceHealth, signallingConnections, replicationHealth, localityPreference |
| Type | Gauge |
| Dimension |
|
| Example | nfScoringFactorActualValue{app="testing-appinfo", app_kubernetes_io_instance="testing", app_kubernetes_io_managed_by="Helm", app_kubernetes_io_name="appinfo", app_kubernetes_io_part_of="ocbsf", app_kubernetes_io_version="1.7.1.0.0", application="ocbsf", calculatedStatus="success", container="appinfo", endpoint="cnc-metrics", engVersion="22.4.0", factor="localityPreference", helm_sh_chart="appinfo-22.4.0", instance="10.233.117.146:9000", job="occne-infra/occne-nf-cnc-podmonitor", microservice="bsf-app-info", mktgVersion="1.7.1.0.0", namespace="biloxi-ns", nfInstanceID="fe7d992b-0541-4c7d-ab84-c6d70b1b0666", pod="testing-appinfo-78dc65865f-hgrhk", pod_template_hash="78dc65865f", vendor="Oracle"} 5 |
Table 9-443 appinfo_dbmonitor_request_total
| Field | Details |
|---|---|
| Description | On every call to DB API towards cnDBTier, this metric
tracks the total instances of a last clusterDbState
detected.
|
| Type | Counter |
| Dimension | uri |
| Example | appinfo_dbmonitor_request_total{uri="http://occne-db-monitor-svc.dbtier-namespace:8080/db-tier/cluster/status/events/1"} |
Table 9-444 appinfo_dbmonitorclusterDbState_current
| Field | Details |
|---|---|
| Description | On every call to DB API towards cnDBTier, this metric
tracks the currently known clusterDbState
detected.
|
| Type | Gauge |
| Dimension | state |
| Example | appinfo_dbmonitorclusterDbState_current{state="START"} 0 |
Table 9-445 appinfo_nfDbFunctionalState_change_total
| Field | Details |
|---|---|
| Description | On any change to
runtime_NfDbFunctionalState, this metric tracks
the total change in NF functional state.
|
| Type | Counter |
| Dimension |
|
| Example | appinfo_nfDbFunctionalState_change_total{autoTransitionState="True",previousClusterDbState="None",newClusterDbState="",nfDbFunctionalState=""} 3.0 |
Table 9-446 appinfo_nfDbFunctionalState_current
| Field | Details |
|---|---|
| Description | On any change to
runtime_NfDbFunctionalState, this metric tracks
the current NF functional state with following dimensions.
|
| Type | Gauge |
| Dimension |
|
| Example | appinfo_nfDbFunctionalState_current{autoTransitionState="True",clusterDbState="",nfDbFunctionalState="Running"} 0 |
Table 9-447 appinfo_http_response_total
| Field | Details |
|---|---|
| Description | On every call to
/status/category/dbClusterState API, track the
total response sent with following dimensions.
|
| Type | Counter |
| Dimension |
|
| Example | appinfo_http_response_total{responseCode="200",ClusterState="",NfState=""} 16.0 |
For more information about dimensions, see CNC Policy Metrics.
9.19 PerfInfo Metrics
This section describes the metrics and examples for PerfInfo service.
Table 9-448 nf_load_info
| Field | Details |
|---|---|
| Description | Provides information about service load. |
| Type | Gauge |
| Dimension |
|
| Example | nf_load_info{namespace="xxx",service="xxx"} 0.8486912141984638 |
Table 9-449 jvm_cpu_usage
| Field | Details |
|---|---|
| Description | Per service jvm_cpu_usage. |
| Type | Gauge |
| Dimension |
|
| Example | jvm_cpu_usage{namespace="xxx",service="xxx"} 0.2758240242725142 |
Table 9-450 jvm_memory
| Field | Details |
|---|---|
| Description | Per service jvm_memory |
| Type | Gauge |
| Dimension |
|
| Example | jvm_memory{namespace="ttz",service="xxx"} 18.361382484436035 |
Table 9-451 cgroup_cpu_nanoseconds
| Field | Details |
|---|---|
| Description | Reports the total CPU time (in nanoseconds) on each CPU core for all the tasks in the cgroup. |
| Type | Gauge |
| Dimension | NA |
| Example | cgroup_cpu_nanoseconds 2.1782821080274e+013 |
Table 9-452 cgroup_memory_bytes
| Field | Details |
|---|---|
| Description | Reports the memory usage. |
| Type | Gauge |
| Dimension | NA |
| Example | cgroup_memory_bytes 1.31289088e+08 |
Table 9-453 load_level
| Field | Details |
|---|---|
| Description | This metric provides information about the load level of a service. |
| Type | Gauge |
| Dimension |
|
| Example | load_level{service="xxx"} L1 |
Table 9-454 service_resource_stress
| Field | Details |
|---|---|
| Description |
This metric tracks CPU, memory, failure count, and pending requests on the basis of which the overload level of a service is calculated. PerfInfo reports the
service_resource_stress metric when it
collects data from the Gateway regardless of the presence of
threshold configuration. It is necessary to have the variable
PUBLISH_STRESS_METRIC_WITHOUT_THRESHOLDS_CONFIGURED
as "true" to view this metric without threshold
configurations.
Note: Add the isLeaderPod="True" query criteria for "Svc resource Overload Stress" and "Load Level" Grafana dashboard queries. |
| Type | Gauge |
| Dimension |
|
| Example | service_resource_stress{isLeaderPod="True",service="my-cnpolicy-occnp-pcf-sm",type="svc_pending_count"} |
Table 9-455 service_resource_overload_level
| Field | Details |
|---|---|
| Description | This metric tracks an individual resource's overload
level that is calculated based on the resource usage and configured
threshold.
Note: Add the isLeaderPod="True" query criteria for "Svc resource Overload Stress" and "Load Level" Grafana dashboard queries. |
| Type | Gauge |
| Dimension |
|
| Example | service_resource_overload_level{service="xxx", type="xxx"}2.0 |
Table 9-456 system_overload_threshold_config_mode
| Field | Details |
|---|---|
| Description | Indicates whether the overload level threshold configuration is based on STANDALONE or PROFILE mode. |
| Type | Gauge |
| Dimension |
|
| Example | system_overload_threshold_config_mode 1.0 |
Table 9-457 active_overload_threshold_fetch_failed
| Field | Details |
|---|---|
| Description | Indicates whether the active profile data is fetched successfully or failed to fetch. |
| Type | Gauge |
| Dimension |
|
| Example | active_overload_threshold_fetch_failed 1.0 |
Table 9-458 oc_ingressgateway_route_overloadcontrol_discard_total
| Field | Details |
|---|---|
| Description | This metric is pegged when incoming request is discarded by Overload Filter on priority or percentage basis. |
| Type | Counter |
| Dimension |
|
| Example | - |
Table 9-459 load_level_report_total
| Field | Details |
|---|---|
| Description | This metric is used to track:
|
| Type | Counter |
| Dimension |
|
| Example | load_level_report_total{namespace="hi-riley", service="pcf-occnp-pcrf-core", isLeaderPod="True", level="Normal", levelChangeType="-"} 2.0 |
Table 9-460 service_resource_overload_level_report_total
| Field | Details |
|---|---|
| Description | This metric is used to track:
|
| Type | Counter |
| Dimension |
|
| Example | service_resource_overload_level_report_total{namespace="hi-riley", service="pcf-occnp-pcrf-core", isLeaderPod="True", level="Normal", levelChangeType="-", type="cpu"} 2.0 |
Table 9-461 http_out_conn_request
| Field | Details |
|---|---|
| Description | This counter metric is used to count the number of http API Egress requests. |
| Type | Counter |
| Dimension |
|
| Example | - |
Table 9-462 http_out_conn_response
| Field | Details |
|---|---|
| Description | This counter metric is used to count the number of http API Egress responses. |
| Type | Counter |
| Dimension |
|
| Example | - |
Table 9-463 overload_manager_enabled
| Field | Details |
|---|---|
| Description | This metric indicates whether overload manager is enabled or disabled. |
| Type | Gauge |
| Dimension |
|
| Example | overload_manager_enabled{namespace="hi-riley", source="DIAM_GW"} 1 |
Table 9-464 leader_pod
| Field | Details |
|---|---|
| Description | This metric is used to know the leader pod. |
| Type | Gauge |
| Dimension |
|
| Example | leader_pod{namespace="hi-riley"} 1 |
For more information about dimensions, see CNC Policy Metrics.
9.20 Pod Congestion Metrics
This section describes the metrics and examples for pod congestion control.
Note:
-
Current behavior in Policy services supporting Pod Congestion Observability Gauge Metrics:
In Grafana dashboard, the congestion state metric (occnp_pod_congestion_state, occnp_pod_resource_congestion_state) and rejection state metric (um_http_congestion_message_reject_total) graphs show inconsistent behavior. As in the pod congestion state graph shows to be in normal state while discard graph does not show flat line plot but with discard messages.
This is caused because pods with the CPU usage level on the borderline of DANGER_OF_CONGESTION (DOC) level with sudden CPU spikes, pushes the pod to DANGER_OF_CONGESTION (DOC) state or CONGESTION_L1 state. During this CPU spike, based on the Load Shedding rule configured in CNC Console the specific requests are discarded and rejection counter metric is incremented. After the brief spike interval the congestion state is reported in Grafana dashboard as normal.
Prometheus scrape metrics from its targeted instance periodically based on scrape interval. But the scrape interval is not granular enough to capture the abrupt CPU spikes. um_http_congestion_message_reject_total is visualized by using rate() function over a time duration. Due to the above cause the counter metrics increments and when averaged over a time interval the rejection plot seems to be constant although it was incremented for the requests in a few seconds when pod was in not normal state due to abrupt CPU spikes.
-
Prefix and Suffix support for
pod_cong_state_reportandpod_resource_congestion_state_reportmetricsIn Policy 24.2.x, the
pod_cong_state_reportandpod_resource_congestion_state_reportmetrics supports prefix and suffix. If users have created dashboard in 24.1.x using these metrics, then they should update their dashboards by adding prefix and suffix for these metrics. The default value prefix isoccnpand suffix is empty string.
Table 9-465 occnp_pod_congestion_state
| Field | Details |
|---|---|
| Description | Tracks congestion state of pod |
| Type | Gauge |
| Dimension |
level = 0,1,2 (0 = Normal, 1 = DoC, 2 = Congested) are for Bulwark and Diameter Gateway services. level = 0,1,2,3,4 (0=Normal,1=DoC,2=Congestion_L1,3=Congestion_L2,4=Congested) are for other Policy services. |
| Examples |
|
Table 9-466 occnp_pod_resource_stress
| Field | Details |
|---|---|
| Description | Tracks CPU, memory, queue usage (pending requests) for binding, pds, usage monitoring and SM serivces. |
| Type | Gauge |
| Dimension | type = "Queue","CPU","Memory" |
| Examples |
|
Table 9-467 occnp_pod_resource_congestion_state
| Field | Details |
|---|---|
| Description | Tracks individual resource's congestion state calculated based on the resource usage and configured threshold |
| Type | Gauge |
| Dimension |
|
| Examples |
|
Table 9-468 occnp_pod_cong_state_report_total
| Field | Details |
|---|---|
| Description | Track the total count of change of congestion state. |
| Type | Counter |
| Dimension |
|
| Example | - |
Table 9-469 occnp_pod_resource_congestion_state_report_total
| Field | Details |
|---|---|
| Description | Track the total count of change of resource specific congestion state. |
| Type | Counter |
| Dimension |
|
| Example | occnp_pod_resource_congestion_state_report_total{new_state="0",old_state="4",resource="cpu",} 3.0 |
Table 9-470 occnp_http_congestion_message_reject_total
| Field | Details |
|---|---|
| Description | Tracks the rejected messages due to pod congestion. |
| Type | Counter |
| Dimension |
|
| Example | - |
Table 9-471 um_http_congestion_message_reject_total
| Field | Details |
|---|---|
| Description | Usage Monitoring service tracks the rejected messages due to pod congestion. |
| Type | Counter |
| Dimension |
|
| Examples | - |
Table 9-472 occnp_congestion_http_pending_request_active_counter
| Field | Details |
|---|---|
| Description | Track the current active counter for calculating pending HTTP requests. |
| Type | Gauge |
| Dimension |
|
| Example | - |
Table 9-473 occnp_congestion_diam_pending_request_active_counter
| Field | Details |
|---|---|
| Description | Track the current active counter for calculating pending diameter requests. |
| Type | Gauge |
| Dimension |
|
| Example | - |
Table 9-474 occnp_congestion_diam_pending_request_end_to_end_id_map_size
| Field | Details |
|---|---|
| Description | Track the congestion control diameter pending requests end to end id map size. |
| Type | Gauge |
| Dimension |
|
| Example | - |
Table 9-475 occnp_congestion_DiamMsgBuffer_queue_msg_count
| Field | Details |
|---|---|
| Description | Track the congestion control DiamMsgBuffer queue message count. |
| Type | Gauge |
| Dimension |
|
| Example | - |
For more information about dimensions, see CNC Policy Metrics.
9.21 PCRF Core Metrics
This section describes the metrics and examples for PCRF Core Metrics.
General Metrics
Table 9-476 occnp_pcrf_core_overall_processing_time_sum_total
| Field | Details |
|---|---|
| Description | Sum of pcrf core overall processing time. |
| Type | Counter |
| Dimension |
|
| Example | occnp_pcrf_core_overall_processing_time_sum_total{method="auditNotification",status="200 OK",} 299.0 |
Table 9-477 occnp_pcrf_core_overall_processing_time_count_total
| Field | Details |
|---|---|
| Description | Total number of pcrf core overall processing time. |
| Type | Counter |
| Dimension |
|
| Example | occnp_pcrf_core_overall_processing_time_count_total{method="auditNotification",status="200 OK",} 16.0 |
Table 9-478 http_server_requests_seconds_count
| Field | Details |
|---|---|
| Description | Number of http request received. |
| Type | Counter |
| Dimension |
|
| Example | http_server_requests_seconds_count{exception="None",method="GET",outcome="SUCCESS",status="200",uri="/pcrfSessionData",} 2.0 |
Table 9-479 http_server_requests_seconds_max
| Field | Details |
|---|---|
| Description | Maximum number of http requests received. |
| Type | Counter |
| Dimension |
|
| Example | http_server_requests_seconds_max{exception="None",method="GET",outcome="SUCCESS",status="200",uri="/pcrfSessionData",} 0.0 |
Table 9-480 topic_version
| Field | Details |
|---|---|
| Description | Describes the current applied version of a given topic (mentioned in dimension topic_name) into the pod. |
| Type | Gauge |
| Dimension |
|
Diameter Metrics
Table 9-481 occnp_diam_request_local_total (CCR-I)
| Field | Details |
|---|---|
| Description | Number of , CCA-I initial request sent. |
| Type | Counter |
| Dimension |
|
| Example | occnp_diam_request_local_total{appId="16777238",appType="Gx",cmdCode="272",destHost="",destRealm="oracle.com",direction="in",msgType="CCR-I",origHost="pgw1.oracle.com",origRealm="oracle.com",} 1.0 1633975504473 |
Table 9-482 occnp_app_request_local_process_total
| Field | Details |
|---|---|
| Description | Number of requests sent to PGW during RAR flow along with number of retries sent to PGW. |
| Type | Counter |
| Dimension |
|
| Example | occnp_app_request_local_process_total{appType="Gx",destHost="pgw.oracle.com",destRealm="oracle.com",msgType="RAR",reason="notification",retryAttempts="1",} 1.0 |
Table 9-483 occnp_app_response_local_process_total
| Field | Details |
|---|---|
| Description | Number of response received from PGW during RAR flow with response code and cause. |
| Type | Counter |
| Dimension |
|
| Example | occnp_app_response_local_process_total{appType="Gx",errorType="",msgType="RAA",reason="notification",reqDestHost="pgw.oracle.com",reqDestRealm="oracle.com",responseType="DIAMETER_SUCCESS",retryAttempts="1",} 1.0 |
Table 9-484 occnp_diam_response_local_total (CCA-I)
| Field | Details |
|---|---|
| Description | Number of CCA initial response received. |
| Type | Counter |
| Dimension |
|
| Example | occnp_diam_response_local_total{appId="16777238",appType="Gx",cmdCode="272",destHost="",destRealm="",direction="out",msgType="CCA-I",origHost="XYZ-IN.us.oracle.com",origRealm="oracle.com",reqDestHost="",reqDestRealm="oracle.com",reqOrigHost="pgw1.oracle.com",reqOrigRealm="oracle.com",responseCode="2001",} 1.0 1633975504473 |
Table 9-485 occnp_diam_request_local_total (CCR-U)
| Field | Details |
|---|---|
| Description | Number of CCR update request sent. |
| Type | Counter |
| Dimension |
|
| Example | occnp_diam_request_local_total{appId="16777238",appType="Gx",cmdCode="272",destHost="XYZ-IN.us.oracle.com",destRealm="oracle.com",direction="in",msgType="CCR-U",origHost="pgw1.oracle.com",origRealm="oracle.com",} 1.0 1633975504473 |
Table 9-486 occnp_diam_response_local_total (CCA-U)
| Field | Details |
|---|---|
| Description | Number of CCA update response received. |
| Type | Counter |
| Dimension |
|
| Example | occnp_diam_response_local_total{appId="16777238",appType="Gx",cmdCode="272",destHost="",destRealm="",direction="out",msgType="CCA-U",origHost="XYZ-IN.us.oracle.com",origRealm="oracle.com",reqDestHost="XYZ-IN.us.oracle.com",reqDestRealm="oracle.com",reqOrigHost="pgw1.oracle.com",reqOrigRealm="oracle.com",responseCode="2001",} 1.0 1633975504473 |
Table 9-487 occnp_diam_request_local_total (CCR-T)
| Field | Details |
|---|---|
| Description | Number of CCR terminate request sent. |
| Type | Counter |
| Dimension |
|
| Example |
|
Table 9-488 occnp_diam_response_local_total (CCA-T)
| Field | Details |
|---|---|
| Description | Number of CCA terminate response received. |
| Type | Counter |
| Dimension |
|
| Example |
|
Table 9-489 occnp_diam_request_local_total (AAR-I)
| Field | Details |
|---|---|
| Description | Number of AAR initial request sent. |
| Type | Counter |
| Dimension |
|
| Example | occnp_diam_request_local_total{appId="16777236",appType="Rx",cmdCode="265",destHost="",destRealm="oracle.com",direction="in",msgType="AAR-I",origHost="af.oracle.com", origRealm="oracle.com",} 1.0 1634756738735 |
Table 9-490 occnp_diam_response_local_total (AAA-I)
| Field | Details |
|---|---|
| Description | Number of AAA initial response received. |
| Type | Counter |
| Dimension |
|
| Example | occnp_diam_response_local_total{appId="16777236",appType="Rx",cmdCode="265",destHost="",destRealm="",direction="out",msgType="AAA-I",origHost="XYZ-IN.us.oracle.com", origRealm="oracle.com",reqDestHost="",reqDestRealm="oracle.com",reqOrigHost="af.oracle.com",reqOrigRealm="oracle.com",responseCode="5065",} 2.0 1634756738735 |
Table 9-491 occnp_diam_request_local_total (AAR-U)
| Field | Details |
|---|---|
| Description | Number of AAR modify requests sent. |
| Type | Counter |
| Dimension |
|
| Example | occnp_diam_request_local_total{appId="16777236",appType="Rx",cmdCode="265",destHost="pcrf-core",destRealm="oracle.com",direction="in",msgType="AAR-U",origHost="af.oracle.com", origRealm="oracle.com",} 1.0 1635332966264 |
Table 9-492 occnp_diam_response_local_total (AAA-U)
| Field | Details |
|---|---|
| Description | Number of AAA modify responses received. |
| Type | Counter |
| Dimension |
|
| Example | occnp_diam_response_local_total{appId="16777236",appType="Rx",cmdCode="265",destHost="",destRealm="",direction="out",msgType="AAA-U",origHost="pcrf-core", origRealm="oracle.com",reqDestHost="pcrf-core",reqDestRealm="oracle.com",reqOrigHost="af.oracle.com",reqOrigRealm="oracle.com",responseCode="2001",} 1.0 1635332966264 |
Table 9-493 occnp_diam_request_local_total (RAR Gx)
| Field | Details |
|---|---|
| Description | Number of RAR Gx request received. |
| Type | Counter |
| Dimension |
|
Table 9-494 occnp_diam_response_local_total (RAA Gx)
| Field | Details |
|---|---|
| Description | Number of RAR Gx response received. |
| Type | Counter |
| Dimension |
|
Table 9-495 occnp_diam_request_local_total (RAR Rx)
| Field | Details |
|---|---|
| Description | Number of RAR Rx request sent. |
| Type | Counter |
| Dimension |
|
Table 9-496 occnp_diam_response_local_total (RAA Rx)
| Field | Details |
|---|---|
| Description | Number of RAA Rx response received. |
| Type | Counter |
| Dimension |
|
Table 9-497 occnp_diam_request_local_total (STR)
| Field | Details |
|---|---|
| Description | Number of STR request sent. |
| Type | Counter |
| Dimension |
|
| Example | occnp_diam_request_local_total{appId="16777236",appType="Rx",cmdCode="275",destHost="XYZ-IN.us.oracle.com",destRealm="oracle.com",direction="in", msgType="STR",origHost="app.oracle.com",origRealm="oracle.com",} 2.0 1635332966264 |
Table 9-498 occnp_diam_response_local_total (STA)
| Field | Details |
|---|---|
| Description | Number of STA response received. |
| Type | Counter |
| Dimension |
|
| Example |
|
Table 9-499 occnp_diam_request_local_total (ASR)
| Field | Details |
|---|---|
| Description | Number of ASR request sent. |
| Type | Counter |
| Dimension |
|
| Example | occnp_diam_request_local_total{appId="16777236",appType="Rx",cmdCode="274",destHost="af.oracle.com",destRealm="oracle.com",direction="out",msgType="ASR",origHost="XYZ-IN.us.oracle.com",origRealm="oracle.com",} 1.0 1638875554937 |
Table 9-500 occnp_diam_response_local_total (ASA)
| Field | Details |
|---|---|
| Description | Number of ASA response received. |
| Type | Counter |
| Dimension |
|
| Example |
|
Table 9-501 occnp_diam_request_local_total (CER)
| Field | Details |
|---|---|
| Description | Number of CER request sent. |
| Type | Counter |
| Dimension |
|
| Example | occnp_diam_request_local_total{appId="0",appType="",cmdCode="257",destHost="",destRealm="",direction="in",msgType="CER",origHost="app.oracle.com", origRealm="oracle.com",} 1.0 1638278712308 |
Table 9-502 occnp_diam_response_local_total (CEA)
| Field | Details |
|---|---|
| Description | Number of CEA response received. |
| Type | Counter |
| Dimension |
|
| Example | occnp_diam_response_local_total{appId="0",appType="",cmdCode="257",destHost="",destRealm="",direction="out",msgType="CEA",origHost="XYZ-IN.us.oracle.com", origRealm="oracle.com",reqDestHost="",reqDestRealm="",reqOrigHost="pgw1.oracle.com",reqOrigRealm="oracle.com",responseCode="2001",} 3.0 1638278712308 |
Table 9-503 occnp_diam_request_local_total (DWR)
| Field | Details |
|---|---|
| Description | Number of DWR request sent. |
| Type | Counter |
| Dimension |
|
| Examples |
|
Table 9-504 occnp_diam_response_local_total (DWA)
| Field | Details |
|---|---|
| Description | Number of DWA response received. |
| Type | Counter |
| Dimension |
|
| Example |
|
Table 9-505 occnp_diam_request_local_total (DPR)
| Field | Details |
|---|---|
| Description | Number of DPR request sent. |
| Type | Counter |
| Dimension |
|
| Example | occnp_diam_request_local_total{appId="0",appType="",cmdCode="282",destHost="",destRealm="",direction="in",msgType="DPR",origHost="pgw1.oracle.com", origRealm="oracle.com",} 1.0 1638278712308 |
Table 9-506 occnp_diam_response_local_total (DPA)
| Field | Details |
|---|---|
| Description | Number of DPA response received. |
| Type | Counter |
| Dimension |
|
| Example | occnp_diam_response_local_total{appId="0",appType="",cmdCode="282",destHost="",destRealm="",direction="out",msgType="DPA",origHost="XYZ-IN.us.oracle.com", origRealm="oracle.com",reqDestHost="",reqDestRealm="",reqOrigHost="pgw1.oracle.com",reqOrigRealm="oracle.com",responseCode="2001",} 1.0 1638278712308 |
Table 9-507 occnp_diam_request_local_total (Timeout Metric RAR)
| Field | Details |
|---|---|
| Description | Number of timeout RAR request sent. |
| Type | Counter |
| Dimension |
|
| Examples |
|
Table 9-508 occnp_diam_response_local_total (Timeout Metric RAA)
| Field | Details |
|---|---|
| Description | Number of timeout RAA response received. |
| Type | Counter |
| Dimension |
|
| Examples |
|
Table 9-509 occnp_diam_request_local_total (Timeout Metric ASR)
| Field | Details |
|---|---|
| Description | Number of timeout ASR request sent. |
| Type | Counter |
| Dimension |
|
Table 9-510 occnp_diam_response_local_total (Timeout Metric ASA)
| Field | Details |
|---|---|
| Description | Number of timeout ASA response received. |
| Type | Counter |
| Dimension |
|
Bulwark Metrics
Table 9-511 occnp_http_bulwark_lock_request_total
| Field | Details |
|---|---|
| Description | Number of bulwark lock requests sent. |
| Type | Counter |
| Dimension |
|
| Example | occnp_http_bulwark_lock_request_total{application="occnp-pcrf-core",instanceId="fe7d992b-0541-4c7d-ab84-c6d70b1b0123",msgType="create",operationType="bulwark_lock",} 2.0 |
Table 9-512 occnp_http_bulwark_lock_response_total
| Field | Details |
|---|---|
| Description | Number of bulwark lock response received. |
| Type | Counter |
| Dimension |
|
| Example | occnp_http_bulwark_lock_response_total{application="occnp-pcrf-core",instanceId="fe7d992b-0541-4c7d-ab84-c6d70b1b0123",msgType="create",operationType="bulwark_lock",responseCode="201",} 2.0 |
Table 9-513 occnp_http_bulwark_unlock_request_total
| Field | Details |
|---|---|
| Description | Number of bulwark unlock requests sent. |
| Type | Counter |
| Dimension |
|
| Example | occnp_http_bulwark_unlock_request_total{application="occnp-pcrf-core",instanceId="fe7d992b-0541-4c7d-ab84-c6d70b1b0123",msgType="create",operationType="bulwark_unlock",} 2.0 |
Table 9-514 occnp_http_bulwark_unlock_response_total
| Field | Details |
|---|---|
| Description | Number of bulwark unlock response received. |
| Type | Counter |
| Dimension |
|
| Example | occnp_http_bulwark_unlock_response_total{application="occnp-pcrf-core",instanceId="fe7d992b-0541-4c7d-ab84-c6d70b1b0123",msgType="create",operationType="bulwark_unlock",responseCode="204",} 2.0 |
Binding and PRE Metrics
Table 9-515 http_out_conn_request_total
| Field | Details |
|---|---|
| Description | Number of connection requests sent. |
| Type | Counter |
| Dimension |
|
| Example | http_out_conn_request_total{application="pcrf-core",operationType="DELETE",serviceResource="Binding",} 28.0 |
Table 9-516 http_out_conn_response_total
| Field | Details |
|---|---|
| Description | Number of connection response received. |
| Type | Counter |
| Dimension |
|
| Example | http_out_conn_response_total{application="pcrf-core",operationType="POST",responseCode="201",serviceResource="Binding",} 33.0 |
Table 9-517 pcrf_core_binding_ex_total
| Field | Details |
|---|---|
| Description | Accounts for any exceptions that occurred during API calls toward Binding service. |
| Type | Counter |
| Dimension |
|
| Example |
General Metrics pcrf_core_binding_ex_total{application="occnp-pcrf-core",exception_type="java.util.concurrent.TimeoutException",operationType="POST",} 2.0 dimensions: Binding and Pre Metrics pcrf_core_binding_ex_total{application="occnp-pcrf-core",exception_type="java.util.concurrent.TimeoutException",operationType="POST",} 2.0 |
Webclient Metrics
Table 9-518 occnp_webclient_sum_total
| Field | Details |
|---|---|
| Description | Sum of webclient requests. |
| Type | Counter |
| Dimension |
|
| Example | occnp_webclient_sum_total{method="POST",status_code="201",url="/binding/v1/dependentContextBinding/context-owner/PCRF-CORE",} 201.0 |
Table 9-519 occnp_webclient_count_total
| Field | Details |
|---|---|
| Description | Number of webclient requests. |
| Type | Counter |
| Dimension |
|
| Example | occnp_webclient_count_total{method="POST",status_code="201",url="/binding/v1/dependentContextBinding/context-owner/PCRF-CORE",} 6.0 |
JDBC Metrics
Table 9-520 occnp_jdbc_operation_count_total
| Field | Details |
|---|---|
| Description | Number of jdbc operations. |
| Type | Counter |
| Dimension |
|
| Example | occnp_jdbc_operation_count_total{method="removeSQL",state="SUCCESS",table="rxsession",} 6.0 |
Table 9-521 occnp_jdbc_operation_sum_total
| Field | Details |
|---|---|
| Description | Sum of jdbc operations. |
| Type | Counter |
| Dimension |
|
| Example | occnp_jdbc_operation_sum_total{method="removeSQL",state="SUCCESS",table="rxsession",} 25.0 |
Session Viewer Metrics
Table 9-522 session_oam_request_total
| Field | Details |
|---|---|
| Description | Total number of oam requests sent. |
| Type | Counter |
| Dimension |
|
| Example | session_oam_request_total{application="pcf_smservice",operationType="terminate",sessionType="SM"} 2.0 |
Table 9-523 session_oam_response_total
| Field | Details |
|---|---|
| Description | Total number of oam response received. |
| Type | Counter |
| Dimension |
|
| Example | session_oam_response_total{application="pcf_smservice",operationType="terminate",responseCode="5xx",sessionType="SM"} 1.0 |
Jetty HTTP client request timing Metrics
Table 9-524 jetty_client_requests_seconds_max
| Field | Details |
|---|---|
| Description | Number of jetty client requests. |
| Type | Counter |
| Dimension |
|
| Example | jetty_client_requests_seconds_max{exception="None",host="pdincredpolicy-occnp-binding",method="DELETE",outcome="SUCCESS",status="204",uri="",} 0.0 |
Table 9-525 jetty_client_requests_seconds_sum
| Field | Details |
|---|---|
| Description | Measures the total time spent processing client requests. |
| Type | Counter |
| Dimension |
|
| Example | jetty_client_requests_seconds_sum{exception="None",host="pdincredpolicy-occnp-binding",method="DELETE",outcome="SUCCESS",status="204",uri="",} 0.831213657 |
Table 9-526 jetty_client_requests_sum_total
| Field | Details |
|---|---|
| Description | measures the total count of client requests. |
| Type | Counter |
| Dimension |
|
| Example | jetty_client_requests_sum_total{method="POST",status_code="201",url="/binding/v1/dependentContextBinding/context-owner/PCRF-CORE",} 199.0 |
Table 9-527 jetty_client_request_size_sum_total
| Field | Details |
|---|---|
| Description | Sum of jetty client request size. |
| Type | Counter |
| Dimension |
|
| Example | jetty_client_request_size_sum_total{method="DELETE",status_code="204",url="/binding/v1/dependentContextBinding/dependentContextId",} 0.0 |
Table 9-528 jetty_client_requests_count_total
| Field | Details |
|---|---|
| Description | Number of jetty client requests. |
| Type | Counter |
| Dimension |
|
| Example | jetty_client_requests_count_total{method="POST",status_code="201",url="/binding/v1/dependentContextBinding/context-owner/PCRF-CORE",} 6.0 |
Cgroup Metrics
Table 9-529 cgroup_cpu_nanoseconds
| Field | Details |
|---|---|
| Description | Reports the total CPU time (in nanoseconds) on each CPU core for all the tasks in the cgroup. |
| Type | Gauge |
| Dimension | NA |
| Example | cgroup_cpu_nanoseconds 2.1782821080274e+013 |
Table 9-530 cgroup_memory_bytes
| Field | Details |
|---|---|
| Description | Reports the memory usage. |
| Type | Gauge |
| Dimension | NA |
| Example | cgroup_memory_bytes 1.31289088e+08 |
Startup Probe Metrics
Table 9-531 config_client_audit_complete
| Field | Details |
|---|---|
| Description | Reports the audit completion of config client. |
| Type | Gauge |
| Dimension | auditor |
| Example | config_client_audit_complete_total{auditor="configClientAuditor",} 7768.0 |
Database Data Encoding Metrics
Table 9-532 occnp_data_encoding_total
| Field | Details |
|---|---|
| Description | PCRF Core gxsession, rxsession and sdsession total of encoded data. |
| Type | Counter |
| Dimension |
|
| Example |
Table 9-533 occnp_data_decoding_total
| Field | Details |
|---|---|
| Description | PCRF Core gxsession, rxsession and sdsession total of decoded data. |
| Type | Counter |
| Dimension |
|
| Example |
Table 9-534 occnp_data_decoding_fail_total
| Field | Details |
|---|---|
| Description | PCRF Core gxsession, rxsession and sdsession total of decoding failures |
| Type | Counter |
| Dimension |
|
| Example |
Table 9-535 occnp_data_encoding_size_before_total
| Field | Details |
|---|---|
| Description | PCRF Core gxsession, rxsession and sdsession total size before encoding. |
| Type | Counter |
| Dimension |
|
| Example |
Table 9-536 occnp_data_encoding_size_after_total
| Field | Details |
|---|---|
| Description | PCRF Core gxsession, rxsession and sdsession total size after encoding. |
| Type | Counter |
| Dimension |
|
| Example |
9.22 Late Arrival Requests and Collision Detection Metrics
The following table describes the late arrival requests and collision detection metrics and their respective dimensions:
Table 9-537 ocpm_late_arrival_rejection_total
| Field | Details |
|---|---|
| Description | Metric that increments when AM, UE, or SM Policy Association late arriving requests are detected and rejected. |
| Type | Counter |
| Dimensions |
|
Table 9-538 ocpm_collision_detection_total
| Field | Details |
|---|---|
| Description | Metric that increments when AM, UE, or SM Policy Association duplicate records are detected and deleted or rejected. |
| Type | Counter |
| Dimensions |
|
For more information about Dimensions, see CNC Policy Metrics.
9.23 Notifier Metrics
The following table describes the Notifier service metrics and their respective dimensions:
Table 9-539 http_notification_request_total
| Field | Details |
|---|---|
| Description | This metric tracks the total number of requests towards a given destination. |
| Type | Counter |
| Dimensions |
notificationEndpoint = IP or FQDN of endpoint version: http1 or http2 https = true or false contentType = <From Content-type header> method = <HTTP method for notification> |
Table 9-540 http_notification_response_total
| Field | Details |
|---|---|
| Description | This metric tracks the total number of responses from a given destination. |
| Type | Counter |
| Dimensions |
notificationEndpoint = IP or FQDN of endpoint version: http1 or http2 https = true or false contentType = <From Content-type header> method = <HTTP method for notification> responseCode = Response code |
Table 9-541 http_notification_request_timeout_total
| Field | Details |
|---|---|
| Description | This metric indicates the request timeout period. That is, the maximum time for which the request can last, after which it is considered as timeout. |
| Type | Counter |
| Dimensions |
notificationEndpoint = IP or FQDN of endpoint version: http11 https = false contentType = <From Content-type header> method = <HTTP method for notification> |
Table 9-542 http_in_conn_request_total
| Field | Details |
|---|---|
| Description | This metric indicates the request coming from PRE |
| Type | Counter |
| Dimensions |
|
| Example | occnp_http_in_conn_request_total{operationType="NOTIFY",servicenameNon3gpp="notifier",} 1.0 |
Table 9-543 http_in_conn_response_total
| Field | Details |
|---|---|
| Description | This metric indicates the response sent to PRE |
| Type | Counter |
| Dimensions |
|
| Example | occnp_http_in_conn_response_total{operationType="NOTIFY",responseCode="204 NO_CONTENT",servicenameNon3gpp="notifier",} 1.0 |
Table 9-544 smpp_request_total
| Field | Details |
|---|---|
| Description | This metric indicates the requests sent towards external endpoint such as SMS Gateway and the delivery receipts received. |
| Type | Counter |
| Dimensions |
|
| Examples |
|
Table 9-545 smpp_response_total
| Field | Details |
|---|---|
| Description | Indicates the number of respoinses received from an external endpoint |
| Type | Counter |
| Dimensions |
|
| Examples |
|
Table 9-546 active_smsc_conn_count
| Field | Details |
|---|---|
| Description | captures total number of active connection with smsc hosts. |
| Type | Gauge |
| Dimensions |
smscName: name |
| Example | occnp_active_smsc_conn_count{smscName="host3",} 1.0 |
Table 9-547 topic_version
| Field | Details |
|---|---|
| Description | Describes the current applied version of a given topic (mentioned in dimension topic_name) into the pod. |
| Type | Gauge |
| Dimensions |
|
Histograms
# HELP occnp_smpp_message_processing_latency_seconds
# TYPE occnp_smpp_message_processing_latency_seconds histogram
occnp_smpp_message_processing_latency_seconds{requestType="bind",quantile="0.5",} 1.207959552
occnp_smpp_message_processing_latency_seconds{requestType="bind",quantile="0.9",} 2.483027968
occnp_smpp_message_processing_latency_seconds{requestType="bind",quantile="0.95",} 2.483027968
occnp_smpp_message_processing_latency_seconds{requestType="bind",quantile="0.99",} 2.483027968
occnp_smpp_message_processing_latency_seconds_bucket{requestType="bind",le="0.01",} 0.0
occnp_smpp_message_processing_latency_seconds_bucket{requestType="bind",le="0.02",} 0.0
occnp_smpp_message_processing_latency_seconds_bucket{requestType="bind",le="0.04",} 0.0
occnp_smpp_message_processing_latency_seconds_bucket{requestType="bind",le="0.08",} 2.0
occnp_smpp_message_processing_latency_seconds_bucket{requestType="bind",le="0.1",} 2.0
occnp_smpp_message_processing_latency_seconds_bucket{requestType="bind",le="0.2",} 2.0
occnp_smpp_message_processing_latency_seconds_bucket{requestType="bind",le="0.5",} 2.0
occnp_smpp_message_processing_latency_seconds_bucket{requestType="bind",le="1.0",} 70.0
occnp_smpp_message_processing_latency_seconds_bucket{requestType="bind",le="5.0",} 73.0
occnp_smpp_message_processing_latency_seconds_bucket{requestType="bind",le="+Inf",} 73.0
occnp_smpp_message_processing_latency_seconds_count{requestType="bind",} 73.0
occnp_smpp_message_processing_latency_seconds_sum{requestType="bind",} 55.069
occnp_smpp_message_processing_latency_seconds{requestType="submit_sm",quantile="0.5",} 0.014680064
occnp_smpp_message_processing_latency_seconds{requestType="submit_sm",quantile="0.9",} 0.01835008
occnp_smpp_message_processing_latency_seconds{requestType="submit_sm",quantile="0.95",} 0.01835008
occnp_smpp_message_processing_latency_seconds{requestType="submit_sm",quantile="0.99",} 0.01835008
occnp_smpp_message_processing_latency_seconds_bucket{requestType="submit_sm",le="0.01",} 3.0
occnp_smpp_message_processing_latency_seconds_bucket{requestType="submit_sm",le="0.02",} 6.0
occnp_smpp_message_processing_latency_seconds_bucket{requestType="submit_sm",le="0.04",} 6.0
occnp_smpp_message_processing_latency_seconds_bucket{requestType="submit_sm",le="0.08",} 7.0
occnp_smpp_message_processing_latency_seconds_bucket{requestType="submit_sm",le="0.1",} 7.0
occnp_smpp_message_processing_latency_seconds_bucket{requestType="submit_sm",le="0.2",} 7.0
occnp_smpp_message_processing_latency_seconds_bucket{requestType="submit_sm",le="0.5",} 7.0
occnp_smpp_message_processing_latency_seconds_bucket{requestType="submit_sm",le="1.0",} 7.0
occnp_smpp_message_processing_latency_seconds_bucket{requestType="submit_sm",le="5.0",} 7.0
occnp_smpp_message_processing_latency_seconds_bucket{requestType="submit_sm",le="+Inf",} 8.0
occnp_smpp_message_processing_latency_seconds_count{requestType="submit_sm",} 8.0
occnp_smpp_message_processing_latency_seconds_sum{requestType="submit_sm",} 6.084
occnp_smpp_message_processing_latency_seconds{requestType="unbind",quantile="0.5",} 0.017825792
occnp_smpp_message_processing_latency_seconds{requestType="unbind",quantile="0.9",} 0.017825792
occnp_smpp_message_processing_latency_seconds{requestType="unbind",quantile="0.95",} 0.017825792
occnp_smpp_message_processing_latency_seconds{requestType="unbind",quantile="0.99",} 0.017825792
occnp_smpp_message_processing_latency_seconds_bucket{requestType="unbind",le="0.01",} 0.0
occnp_smpp_message_processing_latency_seconds_bucket{requestType="unbind",le="0.02",} 1.0
occnp_smpp_message_processing_latency_seconds_bucket{requestType="unbind",le="0.04",} 1.0
occnp_smpp_message_processing_latency_seconds_bucket{requestType="unbind",le="0.08",} 1.0
occnp_smpp_message_processing_latency_seconds_bucket{requestType="unbind",le="0.1",} 1.0
occnp_smpp_message_processing_latency_seconds_bucket{requestType="unbind",le="0.2",} 1.0
occnp_smpp_message_processing_latency_seconds_bucket{requestType="unbind",le="0.5",} 1.0
occnp_smpp_message_processing_latency_seconds_bucket{requestType="unbind",le="1.0",} 1.0
occnp_smpp_message_processing_latency_seconds_bucket{requestType="unbind",le="5.0",} 1.0
occnp_smpp_message_processing_latency_seconds_bucket{requestType="unbind",le="+Inf",} 1.0
occnp_smpp_message_processing_latency_seconds_count{requestType="unbind",} 1.0
occnp_smpp_message_processing_latency_seconds_sum{requestType="unbind",} 0.018
occnp_smpp_message_processing_latency_seconds{requestType="deliver_sm",quantile="0.5",} 0.009404416
occnp_smpp_message_processing_latency_seconds{requestType="deliver_sm",quantile="0.9",} 0.015171584
occnp_smpp_message_processing_latency_seconds{requestType="deliver_sm",quantile="0.95",} 0.015171584
occnp_smpp_message_processing_latency_seconds{requestType="deliver_sm",quantile="0.99",} 0.015171584
occnp_smpp_message_processing_latency_seconds_bucket{requestType="deliver_sm",le="0.01",} 3.0
occnp_smpp_message_processing_latency_seconds_bucket{requestType="deliver_sm",le="0.02",} 4.0
occnp_smpp_message_processing_latency_seconds_bucket{requestType="deliver_sm",le="0.04",} 4.0
occnp_smpp_message_processing_latency_seconds_bucket{requestType="deliver_sm",le="0.08",} 4.0
occnp_smpp_message_processing_latency_seconds_bucket{requestType="deliver_sm",le="0.1",} 4.0
occnp_smpp_message_processing_latency_seconds_bucket{requestType="deliver_sm",le="0.2",} 4.0
occnp_smpp_message_processing_latency_seconds_bucket{requestType="deliver_sm",le="0.5",} 4.0
occnp_smpp_message_processing_latency_seconds_bucket{requestType="deliver_sm",le="1.0",} 4.0
occnp_smpp_message_processing_latency_seconds_bucket{requestType="deliver_sm",le="5.0",} 4.0
occnp_smpp_message_processing_latency_seconds_bucket{requestType="deliver_sm",le="+Inf",} 4.0
occnp_smpp_message_processing_latency_seconds_count{requestType="deliver_sm",} 4.0
occnp_smpp_message_processing_latency_seconds_sum{requestType="deliver_sm",} 0.035
# HELP occnp_smpp_message_processing_latency_seconds_max
# TYPE occnp_smpp_message_processing_latency_seconds_max gauge
occnp_smpp_message_processing_latency_seconds_max{requestType="bind",} 0.803
occnp_smpp_message_processing_latency_seconds_max{requestType="unbind",} 0.018
occnp_smpp_message_processing_latency_seconds_max{requestType="submit_sm",} 0.025
occnp_smpp_message_processing_latency_seconds_max{requestType="deliver_sm",} 0.015
9.24 Usage Monitoring Metrics
The following table describes the Usage Monitoring service metrics and their respective dimensions:
Table 9-548 usage_mon_ingress_request_total
| Field | Details |
|---|---|
| Description | This metric is incremented when Usage Monitoring service receives an incoming HTTP request message. |
| Type | Counter |
| Dimensions |
|
| Example | - |
Table 9-549 usage_mon_ingress_response_total
| Field | Details |
|---|---|
| Description | This metric is incremented when Usage Monitoring service responds to an incoming HTTP request message. |
| Type | Counter |
| Dimensions |
|
| Example | - |
Table 9-550 usage_mon_profile_activated_total
| Field | Details |
|---|---|
| Description | This metric is incremented when UM Data Limit Profile is activated. |
| Type | Counter |
| Dimensions |
|
| Example | usage_mon_profile_activated_total {hostname="ocpcf-usage-mon-b564d6cf8-shzhg",limit_id="mk1",} 3.0 |
Table 9-551 occnp_usage_mon_profile_selected_total
| Field | Details |
|---|---|
| Description | This metric is incremented when UM Data Limit Profile is selected. |
| Type | Counter |
| Dimensions |
|
| Example | usage_mon_profile_selected_total{hostname="ocpcf-usage-mon-b564d6cf8-shzhg",limit_id="mk1",} 7.0 |
Note:
When the Data Limit Profile is received from UDR, occnp_usage_mon_limit_selected metric is pegged and when Data Limit Profile is received through CNC Console, occnp_usage_mon_profile_selected metric is pegged.
Table 9-552 usage_mon_grant_success_total
| Field | Details |
|---|---|
| Description | This metric is incremented when a grant is successfully allocated from a given UM Data Limit Profile. |
| Type | Counter |
| Dimensions |
|
| Example | - |
Table 9-553 usage_mon_grant_failure_total
| Field | Details |
|---|---|
| Description | This metric is incremented when a grant could not be allocated from a given UM Data Limit Profile. |
| Type | Counter |
| Dimensions |
|
| Example | - |
Table 9-554 usage_mon_usage_reported_total
| Field | Details |
|---|---|
| Description | This metric is incremented when usage report is processed for a given UM Data Limit Profile. |
| Type | Counter |
| Dimensions |
|
| Example | usage_mon_usage_reported_total {hostname="ocpcf-usage-mon-b564d6cf8-shzhg",limit_id="mk1",} 9.0 |
Table 9-555 usage_mon_usage_threshold_total
| Field | Details |
|---|---|
| Description | This metric is incremented when usage usage crosses a particular threshold level. |
| Type | Counter |
| Dimensions |
|
| Example | - |
Table 9-556 usage_mon_usage_reset_total
| Field | Details |
|---|---|
| Description | This metric is incremented when usage is reset according to the reset time in a given UM Data Limit Profile. |
| Type | Counter |
| Dimensions |
|
| Example | - |
Table 9-557 usage_mon_egress_pds_request_total
| Field | Details |
|---|---|
| Description | This metric is incremented when Usage Monitoring service sends a request to PDS service. |
| Type | Counter |
| Dimensions |
|
| Example | - |
Table 9-558 usage_mon_egress_pds_response_total
| Field | Details |
|---|---|
| Description | This metric is incremented when Usage Monitoring service receives a response from PDS service. |
| Type | Counter |
| Dimensions |
|
| Example | - |
Table 9-559 session_oam_request_total
| Field | Details |
|---|---|
| Description | This metric is pegged when Session Viewer API is called to get the number of session requests. |
| Type | Request |
| Dimensions |
|
| Example | session_oam_request_total {hostname="ocpcf-usage-mon-b564d6cf8-shzhg",operation_type="get",session_type="um_session",}1.0 |
Table 9-560 session_oam_response_total
| Field | Details |
|---|---|
| Description | This metric is pegged when Session Viewer API is called to get the number of session responses. |
| Type | Response |
| Dimensions |
|
| Example | session_oam_response_total {hostname="ocpcf-usage-mon-b564d6cf8-shzhg",operation_type="get",response_code="2xx",session_type="um_session",}1.0 |
Table 9-561 topic_version
| Field | Details |
|---|---|
| Description | Describes the current applied version of a given topic (mentioned in dimension topic_name) into the pod. |
| Type | Gauge |
| Dimensions |
|
| Example | - |
Table 9-562 occnp_db_overall_processing_time_seconds_count
| Field | Details |
|---|---|
| Description | Indicates the count of the overall processing time on UmDataContext table for Usage Monitoring. |
| Type | Gauge |
| Dimensions |
|
| Example |
occnp_db_overall_processing_time_seconds_count {Method="get",Status="Success",Table="UmContext",compressionScheme="DISABLED",hostname="ocpcf-usage-mon-b564d6cf8-shzhg",} 30.0 occnp_db_overall_processing_time_seconds_count{Method="put",Status="Success",Table="UmContext",compressionScheme="DISABLED",hostname="ocpcf-usage-mon-b564d6cf8-shzhg",} 29.0 occnp_db_overall_processing_time_seconds_count{Method="delete",Status="Success",Table="UmContext",compressionScheme="",hostname="ocpcf-usage-mon-b564d6cf8-shzhg",} 6.0 |
Table 9-563 occnp_db_overall_processing_time_seconds_sum
| Field | Details |
|---|---|
| Description | Indicates the sum of the overall processing time on UmDataContext table for Usage Monitoring. |
| Type | Gauge |
| Dimensions |
|
| Example |
occnp_db_overall_processing_time_seconds_sum{Method="get",Status="Success",Table="UmContext",compressionScheme="DISABLED",hostname="ocpcf-usage-mon-b564d6cf8-shzhg",}0.110589513 occnp_db_overall_processing_time_seconds_sum{Method="put",Status="Success",Table="UmContext",compressionScheme="DISABLED",hostname="ocpcf-usage-mon-b564d6cf8-shzhg",}0.139773756 occnp_db_overall_processing_time_seconds_sum{Method="delete",Status="Success",Table="UmContext",compressionScheme="",hostname="ocpcf-usage-mon-b564d6cf8-shzhg",}0.012469739 |
Table 9-564 usage_mon_context_found_total
| Field | Details |
|---|---|
| Description | This metric is incremented when session lookup happens on the main table or sliced tables for old sessions of the subscribers when table slicing is enabled. |
| Type | Counter |
| Dimensions |
|
| Example | - |
Table 9-565 occnp_um_audit_deleted_maxttl
| Field | Details |
|---|---|
| Description | This metric is incremented when MaxTTL is reached for a enforcement session. |
| Type | Counter |
| Dimensions |
|
| Example | - |
Table 9-566 occnp_um_audit_query_sent_total
| Field | Details |
|---|---|
| Description | This metric is incremented when the Usage Monitoring service sends a query to PCRF Core to check session staleness. |
| Type | Counter |
| Dimensions |
|
| Example | - |
Table 9-567 occnp_um_audit_session_found_total
| Field | Details |
|---|---|
| Description | This metric is incremented when Usage Monitoring receives 2xx response code from PCRF Core for a session GET request. |
| Type | Counter |
| Dimensions |
|
| Example | - |
Table 9-568 occnp_um_audit_session_not_found_total
| Field | Details |
|---|---|
| Description | This metric is incremented when Usage Monitoring receives 404 response code from PCRF Core for session GET request. |
| Type | Counter |
| Dimensions |
|
| Example | - |
Table 9-569 occnp_um_audit_query_error_response_total
| Field | Details |
|---|---|
| Description | This metric is incremented when Usage Monitoring receives 3xx, 4xx (except 404) and 5xx response code from PCRF Core for a session GET request. |
| Type | Counter |
| Dimensions |
|
| Example | - |
Table 9-570 occnp_um_audit_query_exception_total
| Field | Details |
|---|---|
| Description | This metric is incremented when Usage Monitoring service ends up with an exception while sending GET request to PCRF Core service. |
| Type | Counter |
| Dimensions |
|
| Example | - |
Table 9-571 occnp_usage_mon_plan_exhausted_total
| Field | Details |
|---|---|
| Description | This metric is incremented when the allowed usage is exhausted. |
| Type | Counter |
| Dimensions |
|
| Example |
occnp_usage_mon_plan_exhausted_total {hostname="ocpcf-usage-mon-b564d6cf8-d5d79",limit_id="mk1",type="base",}14.0 |
Table 9-572 occnp_usage_mon_limit_selected_total
| Field | Details |
|---|---|
| Description | This metric is incremented when a UM Data Limit Profile is selected. |
| Type | Counter |
| Dimensions |
|
| Example |
occnp_usage_mon_limit_selected_total {hostname="ocpcf-usage-mon-b564d6cf8-shzhg",limit_id="mk1",type="base",} 7.0 occnp_usage_mon_limit_selected_total {hostname="ocpcf-usage-mon-b564d6cf8-d5d79",limit_id="mk1-roll-over-def-9f51e",type="roll-over-def",}1.0 occnp_usage_mon_limit_selected_total{hostname="ocpcf-usage-mon-b564d6cf8-d5d79",limit_id="mk1-roll-over-def-640e7",type="roll-over-def",}1.0 occnp_usage_mon_limit_selected_total{hostname="ocpcf-usage-mon-b564d6cf8-d5d79",limit_id="mk1-roll-over-def-8b066",type="roll-over-def",}1.0 occnp_usage_mon_limit_selected_total{hostname="ocpcf-usage-mon-b564d6cf8-d5d79",limit_id="mk1-roll-over-def-9161c",type="roll-over-def",}1.0 |
Note:
When the Data Limit Profile is received from UDR, occnp_usage_mon_limit_selected metric is pegged and when Data Limit Profile is received through CNC Console, occnp_usage_mon_profile_selected metric is pegged.
Table 9-573 usage_mon_rollover_def_create
| Field | Details |
|---|---|
| Description | This metric is increment when current rollover def created using current rollover usage. |
| Type | Counter |
| Dimensions |
|
| Example |
usage_mon_rollover_def_create{hostname="ocpcf-usage-mon-b564d6cf8-d5d79",limit_id="mk1-roll-over-def-56937",rollover_count="1",}1.0 usage_mon_rollover_def_create{hostname="ocpcf-usage-mon-b564d6cf8-d5d79",limit_id="mk1-roll-over-def-33423",rollover_count="1",}1.0 usage_mon_rollover_def_create{hostname="ocpcf-usage-mon-b564d6cf8-d5d79",limit_id="mk2-roll-over-def-71740",rollover_count="1",}1.0 |
Table 9-574 occnp_usage_mon_rollover_capped_total
| Field | Details |
|---|---|
| Description | This metric is incremented when rollover reaches maximum data limit cap. |
| Type | String |
| Dimensions |
|
| Example |
occnp_usage_mon_rollover_capped_total{hostname="my-cnpolicy-usage-mon-6ff7947d8f-rcrxs",limit_id="mk1-roll-over-def-fa74b",} 1.0 occnp_usage_mon_rollover_capped_total {hostname="ocpcf-usage-mon-b564d6cf8-d5d79",limit_id="mk1-roll-over-def-18e63",}1.0 occnp_usage_mon_rollover_capped_total{hostname="ocpcf-usage-mon-b564d6cf8-d5d79",limit_id="mk1-roll-over-def-ef270",}1.0 occnp_usage_mon_rollover_capped_total{hostname="ocpcf-usage-mon-b564d6cf8-d5d79",limit_id="mk1-roll-over-def-63e0c",}1.0 occnp_usage_mon_rollover_capped_total{hostname="ocpcf-usage-mon-b564d6cf8-d5d79",limit_id="mk1-roll-over-def-10685",}1.0 |
Table 9-575 ocpm_udr_tracking_exception_total
| Field | Details |
|---|---|
| Description | ocpm_udr_tracking_exception_total metric is incremented for a successful operation_type="subscribe" response if the apiroot in the Location header is invalid. |
| Type | Counter |
| Dimensions |
|
| Example | ocpm_udr_tracking_exception_total{HostName="",application="pcf_userservice",hostname="policy-occnp-udr-connector-68f57cc698-rx28l",nf_instance_id="fe7d992b-0541-4c7d-ab84-111112222211",nf_name="nf2stub.altair-ns10.svc",operration_type="get",service_resource="policy-data",service_subresource="sm-data",service_version="v1",servicename_3gpp="nudr-dr"} |
9.25 Bulwark Metrics
The following table describes the Bulwark service metrics and their respective dimensions:
Table 9-576 Dimension Glossary
| Dimension | Possible values from your Queries | Explanation |
|---|---|---|
| namespace | $namespace, or real values like dev, qa, prod | Kubernetes namespace where Bulwark is running. |
| exported_application | bulwark | Logical application name attached to exported metrics. |
| requestType | acquireLock, releaseLock | Type of lock operation being processed. |
| pod | values like bulwark-6d7b8c9f4f-xyz12 | Individual Kubernetes pod name, used for per-pod breakdown. |
| container | bulwark | Container name inside the pod that exposes the metric. |
| uri | /v1/locks, /v1/locks/{lockID} | HTTP endpoint path being called. |
| status | 200, 201, 204, 400, 404, 409, 500 | HTTP response status code returned by the API. Exact values depend on runtime behavior. |
| le | 0.005, 0.01, 0.025, 0.05, 0.075, 0.1, 0.25, 0.5, 0.75, 1, 2.5, 5, 10, inf | Histogram bucket upper bound. For example, 0.005 usually means <= 5ms, and inf means everything above the last bucket. |
| name | Task Dispatcher Engine Fixed Thread Pool | Executor or thread-pool name for executor-related metrics. |
| totalLockAttempts | 1, 2, 3, 4, ... | Number of attempts needed before the lock request produced a final response. |
Table 9-577 lock_request_total
| Field | Details |
|---|---|
| Description | Total number of lock requests received at Bulwark per service or pod. |
| Type | Counter |
| Dimensions |
|
| Examples |
|
Table 9-578 http_server_requests_seconds_count
| Field | Details |
|---|---|
| Description | Total number of HTTP requests served by Bulwark. Useful for request rate and response-code distribution for lock or unlock APIs. |
| Type | Counter |
| Dimensions |
|
| Examples |
|
Table 9-579 lockAcquisitionResponseWaitingLatency_seconds_bucket
| Field | Details |
|---|---|
| Description | Distribution of lock-acquisition response latency, showing how long to wait for lock responses across latency buckets. |
| Type | Histogram bucket |
| Dimensions |
|
| Examples |
|
Table 9-580 unlockResponseWaitingLatency_bucket
| Field | Details |
|---|---|
| Description | Distribution of unlock-response latency, showing how long unlock requests take across latency buckets. |
| Type | Histogram bucket |
| Dimensions |
|
| Examples |
|
Table 9-581 coherenceLockProcessingMs_bucket
| Field | Details |
|---|---|
| Description | Distribution of time spent in coherence/backend processing during lock requests. |
| Type | Histogram bucket |
| Dimensions |
|
| Examples |
|
Table 9-582 coherenceUnlockProcessingMs_bucket
| Field | Details |
|---|---|
| Description | Distribution of time spent in coherence/backend processing during unlock requests. |
| Type | Histogram bucket |
| Dimensions |
|
| Examples |
|
Table 9-583 internal_pending_lock_req_ctx_storage_map_size
| Field | Details |
|---|---|
| Description | Current number of pending lock request contexts stored internally by Bulwark. |
| Type | Gauge |
| Dimensions |
|
| Examples |
|
Table 9-584 executor_queued_tasks
| Field | Details |
|---|---|
| Description | Current number of tasks waiting in the executor queue for the Bulwark thread pool. |
| Type | Gauge |
| Dimensions |
|
| Examples |
|
Table 9-585 executor_active_threads
| Field | Details |
|---|---|
| Description | Current number of active executor threads processing work. |
| Type | Gauge |
| Dimensions |
|
| Examples |
|
Table 9-586 coherenceLockInvokeTimeout_total
| Field | Details |
|---|---|
| Description | Total number of coherence invocation timeouts seen during lock processing. |
| Type | Counter |
| Dimensions |
|
| Examples |
|
Table 9-587 lock_response_total
| Field | Details |
|---|---|
| Description | Total number of lock responses sent by Bulwark per service or pod. |
| Type | Counter |
| Dimensions |
|
| Examples |
|
Table 9-588 lock_collision_total
| Field | Details |
|---|---|
| Description | Tracks the total count of all the collisions occurred for single/multi lock request failure. |
| Type | Counter |
| Dimensions |
|
| Examples |
lock_collision_total{application="bulwark",noOfKeysPerRequest="1",podName="pcf-bulwark-776df8bb5c-6g2f6",serviceName="policyds",} 80.0 lock_collision_total{application="bulwark",noOfKeysPerRequest="2",podName="pcf-bulwark-776df8bb5c-6g2f6",serviceName="occnp_pcf_sm",} 8.0 lock_collision_total{application="bulwark",noOfKeysPerRequest="1",podName="pcf-bulwark-776df8bb5c-6g2f6",serviceName="occnp_pcf_sm",} 92.0 |
Table 9-589 coherence_callback_operation_total
| Field | Details |
|---|---|
| Description | Tracks the total count all the register/deregister requests towards coherence. |
| Type | Counter |
| Dimensions |
|
| Examples |
coherence_callback_operation_total{application="bulwark",opStatus="success",opType="Deregistration",podName="test-bulwark-5f44788c69-qjdhd",} 0 coherence_callback_operation_total{application="bulwark",opStatus="success",opType="Registration",podName="test-bulwark-5f44788c69-qjdhd",} 0 |
Table 9-590 coherence_callback_response_total
| Field | Details |
|---|---|
| Description | Tracks the total coherence callback responses from coherence to bulwark |
| Type | Counter |
| Dimensions | bulwarkPodName |
| Examples | coherence_callback_response_total{application="bulwark",podName="test-bulwark-8f8b9bc67-dpf85",} 0 |
For more information about Dimensions, see CNC Policy Metrics.
9.26 CHF Metrics
The following table describes the CHF service metrics and their respective dimensions:
Table 9-591 ocpm_chf_tracking_request_total
| Field | Details |
|---|---|
| Description | Total number of CHF tracking requests. |
| Type | Counter |
| Dimensions |
|
| Examples |
|
Table 9-592 ocpm_chf_tracking_response_total
| Field | Details |
|---|---|
| Description | Total number of CHF tracking response. |
| Type | Counter |
| Dimensions |
|
| Examples |
|
9.27 UDR Metrics
The following table describes the UDR service metrics and their respective dimensions:
Table 9-593 ocpm_udr_tracking_request_total
| Field | Details |
|---|---|
| Description | Total number of UDR tracking request. |
| Type | Counter |
| Dimensions |
|
| Examples |
|
Table 9-594 ocpm_udr_tracking_response_total
| Field | Details |
|---|---|
| Description | This metric captures all the responses recieved by UDR Connector on it is communication with UDR. |
| Type | Counter |
| Dimensions |
|
| Examples |
|
Table 9-595 ocpm_nfDiscovery_request_total
| Field | Details |
|---|---|
| Description | PCF measures the total number of successful/failed discovery query of UDR using "group-id-list". |
| Type | Counter |
| Dimensions | queryParameters="service-names,group-id-list,target-nf-type |
| Example | ocpm_nfDiscovery_request_total{app_kubernetes_io_instance="test", app_kubernetes_io_managed_by="Helm", app_kubernetes_io_name="user-service", app_kubernetes_io_part_of="occnp", app_kubernetes_io_version="1.0.0", application="occnp", container="user-service", endpoint="cnc-metrics", engVersion="23.4.0-ocngf-incredibles", exported_application="pcf_userservice", helm_sh_chart="user-service-23.4.0-ocngf-incredibles", hostname="test-occnp-udr-connector-868c766947-fr7zx", instance="10.233.93.4:9000", io_kompose_service="test-occnp-udr-connector", job="occne-infra/occne-nf-cnc-podmonitor", microservice="occnp_pcf_user", mktgVersion="1.0.0", namespace="s-euler", pod="test-occnp-udr-connector-868c766947-fr7zx", pod_template_hash="868c766947", queryParameters="service-names,group-id-list,target-nf-type,requester-nf-type", targetNfType="UDR", vendor="Oracle"} |
Table 9-596 ocpm_nfDiscovery_response_total
| Field | Details |
|---|---|
| Description | PCF measures the total number of successful/failed discovery query of UDR using "group-id-list". |
| Type | Counter |
| Dimensions |
|
| Example | ocpm_nfDiscovery_response_total{app_kubernetes_io_instance="test", app_kubernetes_io_managed_by="Helm", app_kubernetes_io_name="user-service", app_kubernetes_io_part_of="occnp", app_kubernetes_io_version="1.0.0", application="occnp", container="user-service", endpoint="cnc-metrics", engVersion="23.4.0-ocngf-incredibles", exported_application="pcf_userservice", helm_sh_chart="user-service-23.4.0-ocngf-incredibles", hostname="test-occnp-udr-connector-868c766947-fr7zx", instance="10.233.93.4:9000", io_kompose_service="test-occnp-udr-connector", job="occne-infra/occne-nf-cnc-podmonitor", microservice="occnp_pcf_user", mktgVersion="1.0.0", namespace="s-euler", pod="test-occnp-udr-connector-868c766947-fr7zx", pod_template_hash="868c766947", queryParameters="service-names,group-id-list,target-nf-type,requester-nf-type", responseCode="424", targetNfType="UDR", vendor="Oracle"} |
Table 9-597 occnp_group_id_list_discovery_header_sent_total
| Field | Details |
|---|---|
| Description | PCF measures the number of GET or POST request sent to UDR with 3gpp-Sbi-Discovery-group-Id-list for delegated discovery of UDR toward SCP. |
| Type | Counter |
| Dimensions |
|
| Example | occnp_group_id_list_discovery_header_sent_total{app_kubernetes_io_instance="test", app_kubernetes_io_managed_by="Helm", app_kubernetes_io_name="user-service", app_kubernetes_io_part_of="occnp", app_kubernetes_io_version="1.0.0", application="occnp", container="user-service", endpoint="cnc-metrics", engVersion="23.4.0-ocngf-incredibles", exported_application="pcf_userservice", helm_sh_chart="user-service-23.4.0-ocngf-incredibles", hostname="test-occnp-udr-connector-79df49b796-gc77c", instance="10.233.72.203:9000", io_kompose_service="test-occnp-udr-connector", job="occne-infra/occne-nf-cnc-podmonitor", microservice="occnp_pcf_user", mktgVersion="1.0.0", namespace="s-euler", operation_type="get", pod="test-occnp-udr-connector-79df49b796-gc77c", pod_template_hash="79df49b796", vendor="Oracle"} |
9.28 User-Agent Header Metrics
Table 9-598 oc.ingressgateway.http.requests
| Field | Details |
|---|---|
| Description |
This metric is pegged for every incoming request on Ingress
Gateway. This will be independent of User Agent validation
feature at ingress gateway. If the User-Agent header is not
present, then UNKNOWN will be pegged only for the following
dimensions:
If User-Agent header is present then respective dimensions are pegged as per user-agent header. Note: Only dimensions are part of the User-Agent. |
| Type | Counter |
| Dimensions |
|
| Examples |
Example when User-agent is not present: {ClientCertIdentity="N/A",ConsumerFqdn="UNKNOWN",DestinationHost="UNKNOWN",Host="ocpcf-occnp-ingress-gateway.ss-gate-beta-b-16965005-gate-pcf.svc.cosmos.lab.us.oracle.com",HttpVersion="HTTP/2.0",InstanceIdentifier="UNKNOWN_ingressgateway",Method="POST",NFServiceType="nnrf-client",NFType="NRF",Route_path="/nnrf-client/**",Scheme="HTTP",consumerInstanceId="UNKNOWN",consumerNfType="UNKNOWN",oAuthTokenPresent="false",}38.0 Example when User-agent not present: occnp_oc_ingressgateway_http_requests_total{ClientCertIdentity="N/A",ConsumerFqdn="nsmf-consp-001.bltnmn86.mw.smf.5gc.vzims.com",DestinationHost="UNKNOWN",Host="ocpcf-occnp-ingress-gateway.ss-gate-beta-b-16965005-gate-pcf.svc", HttpVersion="HTTP/2.0", InstanceIdentifier="UNKNOWN_ingressgateway",Method="POST",NFServiceType="npcf-smpolicycontrol",NFType="PCF",Route_path="/npcf-smpolicycontrol/*/sm-policies/ {policy-id}/update",Scheme="HTTP",consumerInstanceId="52304af4-1111-45f1-9025-555552222222", consumerNfType="SMF",oAuthTokenPresent="false",} 61.0 |
9.29 NWDAF Agent Metrics
The following table describes the NWDAF Agent metrics and their respective dimensions:
Table 9-599 subscription_failure
| Field | Details |
|---|---|
| Description | Gauge of failures for configured slice load levels doing autonomous subscription during configuration changes. |
| Type | Gauge |
| Dimensions |
|
| Example | subscription_failure{operationType="POST",requestType="autonomous",responseCode="500",serviceResource="SLICE_LOAD_LEVEL",snssai="14-aaaa14",} 1.0 |
Table 9-600 http_backend_request_total
| Field | Details |
|---|---|
| Description | Counter for backend requests |
| Type | Counter |
| Dimensions |
|
| Example | http_backend_request_total{operationType="POST",serviceNameNon3gpp="autonomous",serviceResource="SLICE_LOAD_LEVEL",} 26.0 |
Table 9-601 http_backend_response_total
| Field | Details |
|---|---|
| Description | Counter for responses to backend requests |
| Type | Counter |
| Dimensions |
|
| Example | http_backend_response_total{operationType="POST",responseCode="201",serviceNameNon3gpp="autonomous",serviceResource="SLICE_LOAD_LEVEL",} 25.0 |
Table 9-602 http_in_conn_request_total
| Field | Details |
|---|---|
| Description | Counter for NWDAF notification requests |
| Type | Counter |
| Dimensions |
|
| Example | http_in_conn_request_total{operationType="POST",serviceName3gpp="NWDAF",serviceResource="NF_LOAD",serviceVersion="v1",} 1.0 |
Table 9-603 http_in_conn_response_total
| Field | Details |
|---|---|
| Description | Counter for responses to NWDAF notification requests |
| Type | Counter |
| Dimensions |
|
| Example | http_in_conn_response_total{operationType="POST",responseCode="204",serviceName3gpp="NWDAF",serviceResource="NF_LOAD",serviceVersion="v1",} 1.0 |
Table 9-604 http_out_conn_request_total
| Field | Details |
|---|---|
| Description | Counter for requests sent from nwdaf-agent to NWDAF |
| Type | Counter |
| Dimensions |
|
| Example | http_out_conn_request_total{host="floki-occnp-egress-gateway/nnwdaf-eventssubscription/v1",instanceId="fe7d992b-0541-4c7d-ab84-c6d70b1b0621",isAlternateRoute="",isRetryAttempt="",operationType="POST",serviceName3gpp="NWDAF",serviceResource="SLICE_LOAD_LEVEL",serviceVersion="v1",} 26.0 |
Table 9-605 http_out_conn_response_total
| Field | Details |
|---|---|
| Description | Counter for responses from NWDAF |
| Type | Counter |
| Dimensions |
|
| Example | http_out_conn_response_total{host="floki-occnp-egress-gateway/nnwdaf-eventssubscription/v1",instanceId="fe7d992b-0541-4c7d-ab84-c6d70b1b0621",isAlternateRoute="",isRetryAttempt="",operationType="POST",responseCode="500",serviceName3gpp="NWDAF",serviceResource="SLICE_LOAD_LEVEL",serviceVersion="v1",} 1.0 |
Table 9-606 topic_version
| Field | Details |
|---|---|
| Description | Describes the current applied version of a given topic (mentioned in dimension topic_name) into the pod. |
| Type | Gauge |
| Dimensions |
|
Table 9-607 data_repository_invocations_seconds_max
| Field | Details |
|---|---|
| Description | This metric is used to track the maximum execution time of Data repository invocations. It is a useful metric for monitoring the performance of Data repositories and identifying slow-running queries. |
| Type | Gauge |
| Dimension |
|
| Example | data_repository_invocations_seconds_max{app_kubernetes_io_instance="ocbsf", app_kubernetes_io_managed_by="Helm", app_kubernetes_io_name="audit-service", app_kubernetes_io_part_of="ocbsf", app_kubernetes_io_version="1.0.0.0", application="ocbsf", container="audit-service", endpoint="cnc-metrics", engVersion="24.1.4", exception="None", helm_sh_chart="audit-service-24.1.4", instance="10.233.127.211:9000", io_kompose_service="ocbsf-ocpm-audit-service", job="occne-infra/occne-nf-cnc-podmonitor", method="getQueuedTablesToAudit", microservice="ocbsf-audit", mktgVersion="1.0.0.0", namespace="ocbsf", pod="ocbsf-ocpm-audit-service-6b6f85f7b9-nmzr4", pod_template_hash="6b6f85f7b9", repository="AuditSchedulerRepository", security_istio_io_tlsMode="istio", service_istio_io_canonical_name="audit-service", service_istio_io_canonical_revision="1.0.0.0", state="SUCCESS", vendor="Oracle"} |
Table 9-608 data_repository_invocations_seconds_sum
| Field | Details |
|---|---|
| Description |
The seconds_sum metric for Data repository invocations is a measure of the total time spent executing repository methods. |
| Type | Gauge |
| Dimension |
|
| Example | data_repository_invocations_seconds_sum{app_kubernetes_io_instance="ocbsf", app_kubernetes_io_managed_by="Helm", app_kubernetes_io_name="audit-service", app_kubernetes_io_part_of="ocbsf", app_kubernetes_io_version="1.0.0.0", application="ocbsf", container="audit-service", endpoint="cnc-metrics", engVersion="24.1.4", exception="None", helm_sh_chart="audit-service-24.1.4", instance="10.233.84.88:9000", io_kompose_service="ocbsf-ocpm-audit-service", job="occne-infra/occne-nf-cnc-podmonitor", method="getQueuedTablesToAudit", microservice="ocbsf-audit", mktgVersion="1.0.0.0", namespace="ocbsf", pod="ocbsf-ocpm-audit-service-6b6f85f7b9-nshv9", pod_template_hash="6b6f85f7b9", repository="AuditSchedulerRepository", security_istio_io_tlsMode="istio", service_istio_io_canonical_name="audit-service", service_istio_io_canonical_revision="1.0.0.0", state="SUCCESS", vendor="Oracle"} |
Table 9-609 data_repository_invocations_seconds_count
| Field | Details |
|---|---|
| Description |
This metric measures the total time spent in Data JPA repository invocations. It is a counter metric, which means that it increments each time a repository method is invoked. The metric is reported in seconds. |
| Type | Counter |
| Dimension |
|
| Example | data_repository_invocations_seconds_count{app_kubernetes_io_instance="ocbsf", app_kubernetes_io_managed_by="Helm", app_kubernetes_io_name="audit-service", app_kubernetes_io_part_of="ocbsf", app_kubernetes_io_version="1.0.0.0", application="ocbsf", container="audit-service", endpoint="cnc-metrics", engVersion="24.1.4", exception="None", helm_sh_chart="audit-service-24.1.4", instance="10.233.127.211:9000", io_kompose_service="ocbsf-ocpm-audit-service", job="occne-infra/occne-nf-cnc-podmonitor", method="findAll", microservice="ocbsf-audit", mktgVersion="1.0.0.0", namespace="ocbsf", pod="ocbsf-ocpm-audit-service-6b6f85f7b9-nmzr4", pod_template_hash="6b6f85f7b9", repository="AuditRegistrationsRepository", security_istio_io_tlsMode="istio", service_istio_io_canonical_name="audit-service", service_istio_io_canonical_revision="1.0.0.0", state="SUCCESS", vendor="Oracle"} |
9.30 PRE Metrics
The following table describes the PRE Service metrics and respective dimensions:
Table 9-610 http_in_conn_request_total
| Field | Details |
|---|---|
| Description | The requests received by a Microservice from the downstream application. |
| Type | Counter |
| Dimensions |
|
| Example | http_in_conn_request_total{operationType="post",servicenameNon3gpp="pcf-sm",workerId="1"}1 |
Table 9-611 http_in_conn_response_total
| Field | Details |
|---|---|
| Description | The response sent for incoming requests to a micro-service. |
| Type | Counter |
| Dimensions |
|
| Example | http_in_conn_response_total{operationType="post",servicenameNon3gpp="pcf-sm",responseCode="200",workerId="1"}1 |
Table 9-612 http_in_conn_processing_latency_ms
| Field | Details |
|---|---|
| Description | The overall response time for request, received from the downstream application. |
| Type | Histogram |
| Dimensions |
|
| Examples |
|
Table 9-613 http_out_conn_request_total
| Field | Details |
|---|---|
| Description | The requests sent by a micro-service to upstream. |
| Type | Counter |
| Dimensions |
|
| Example | http_out_conn_request_total{operationType="POST",host="localhost:8080",httpVersion="1",isRetryAttempt="false",servicenameNon3gpp="PER",workerId="1"}1 |
Table 9-614 http_out_conn_response_total
| Field | Details |
|---|---|
| Description | The response received for upstream requests to a micro-service. |
| Type | Counter |
| Dimensions |
|
| Example | http_out_conn_response_total{operationType="POST",responseCode="502",host="localhost:8080",httpVersion="1",isRetryAttempt="false",servicenameNon3gpp="PER",workerId="1"}1 |
Table 9-615 http_out_conn_processing_latency_ms
| Field | Details |
|---|---|
| Description | The overall response time for request towards upstream. |
| Type | Histogram |
| Dimensions |
|
| Examples |
|
Table 9-616 occnp_policy_processing_latency_ms
| Field | Details |
|---|---|
| Description | Overall response time for request received from
downstream when executing Policy.
Note: This metric is associated only with 'Call Policy' block. For more information, see "Public Category" section in Oracle Communications Cloud Native Core, Converged Policy Design Guide. |
| Type | Histogram |
| Dimensions |
|
| Examples |
Note: This metric is associated with 'Call Policy' block. For more information, see "Public Category" section in Oracle Communications Cloud Native Core, Converged Policy Design Guide. |
Table 9-617 occnp_block_counter_label
| Field | Details |
|---|---|
| Description | Tracks total number of given custom block is invoked for
corresponding label.
Note: This metric is associated with 'Increment Counter Label' block. For more information, see "Public Category" section in Oracle Communications Cloud Native Core, Converged Policy Design Guide. |
| Type | Counter |
| Dimensions |
|
| Example | occnp_block_counter_label{serviceType="pcf-sm",operationType="post",workerId="2",label="lml",subLabel=""}1 |
Table 9-618 occnp_block_exec_time_ns
| Field | Details |
|---|---|
| Description | Tracks overall time taken by all the blocks captured as
part of this block.
Since this metric is in nanoseconds, execution time below 0 are not recorded. It will be visible with traffic around 10k TPS. Note: This metric is associated with 'Time' block. For more information, see "Public Category" section in Oracle Communications Cloud Native Core, Converged Policy Design Guide. |
| Type | Histogram |
| Dimensions |
|
| Example |
|
Table 9-619 occnp_policy_project_state_change_total
| Field | Details |
|---|---|
| Description |
Tracks the total number of policy project state changes for each service whenever a project transitions between dev and prod states (or vice versa). It is designed to provide a way to identify and increment policy project state counters across various policy execution legs. The metric is pegged at the worker level, providing an aggregated count across all active workers. For example, if there are 4 workers running in production, each state transition between dev and prod (or vice versa) will increment the counter by 4. A successful state transition is indicated when the metric increases by the full number of active workers (e.g., an increment of 4 for 4 workers). Any value less than the total number of workers suggests a failure, indicating that one or more workers may not have successfully applied the updated configuration. Metric Calculation: The total possible combinations of records for this metric are calculated using the formula: Total Combinations = (Number of Services) × (Maximum Number of Projects per Service) × (Number of States) Where:
|
| Type | Counter |
| Dimensions |
|
| Examples |
occnp_policy_project_state_change_total{serviceType="pcf-ue",projectName="PCFUE",state="dev"} 2 occnp_policy_project_state_change_total{serviceType="pcf-sm",projectName="PcfSMClone",state="dev"} 2 occnp_policy_project_state_change_total{serviceType="pcf-sm",projectName="PCFSM",state="dev"} 4 occnp_policy_project_state_change_total{serviceType="pcf-sm",projectName="PCFSM",state="prod"} 2 occnp_policy_project_state_change_total{serviceType="pcf-ue",projectName="PCFUE",state="prod"} 2 occnp_policy_project_state_change_total{serviceType="pcf-sm",projectName="PcfSMClone",state="prod"} 2 |
Table 9-620 occnp_policy_project_current_state
| Field | Details |
|---|---|
| Description |
Provides a real-time, numerical representation of the current deployment state for each unique policy project within the system. It reflects whether a policy project is in a development (dev) or production (prod) state. The metric is pegged at the master level to provide current state of projects. Possible Values and Interpretation:
|
| Type | Gauge |
| Dimensions |
|
| Example |
|
For more information about Dimensions, see CNC Policy Metrics.
9.31 NRF Client Metrics
Table 9-621 nrfclient_perf_info_nf_profile_load
| Field | Details |
|---|---|
| Description | The current Load of the NF. |
| Type | Gauge |
| Dimensions | - |
Table 9-622 nrfclient_current_nf_status
| Field | Details |
|---|---|
| Description | The current operative status of the NF. The gauge
shall be indicate the status as below:
|
| Type | Gauge |
| Dimensions |
|
Table 9-623 nrfclient_nf_status_with_nrf
| Field | Details |
|---|---|
| Description | The operative status of the NF communicated to the
NRF. The gauge shall be indicate the status as below:
|
| Type | Gauge |
| Dimensions |
|
Table 9-624 nrfclient_nrf_operative_status
| Field | Details |
|---|---|
| Description | The current operative status of the NRF Instance. If
the metric has value
|
| Type | Gauge |
| Dimensions | NrfUri - URI of the NRF Instance |
Table 9-625 nrfclient_nrf_status_total
| Field | Details |
|---|---|
| Description | Total number of times an NRF instance is marked as
healthy or unhealthy. The apiRoot is specified in the format
'scheme'://'fqdn':'port'.
Note: If health check procedure is disabled, all NRF instances are marked as HEALTHY after successful NF registration. |
| Type | Counter |
| Dimensions | NrfUri- URI of the NRF InstanceHealthStatus FailureReason - Reason for the status |
Table 9-626 nrfclient_nrf_successive_healthy_count
| Field | Details |
|---|---|
| Description | The metric shows the consecutive number of times the NRF is considered as healthy. The metric has a minimum value of 0 and maximum value of healthCheckCount. |
| Type | Counter |
| Dimensions | NrfUri- URI of the NRF Instance |
Table 9-627 nrfclient_nrf_successive_unhealthy_count
| Field | Details |
|---|---|
| Description | The metric shows the consecutive number of times the NRF is considered as unhealthy |
| Type | Counter |
| Dimensions | NrfUri- URI of the NRF Instance |
Table 9-628 nrfclient_on_demand_conn_in_request_total
| Field | Details |
|---|---|
| Description | Total number of on-demand requests received from the backend NF to NRF Client. |
| Type | Counter |
| Dimensions |
|
Table 9-629 nrfclient_on_demand_conn_out_response_total
| Field | Details |
|---|---|
| Description | Total number of on-demand responses sent to the backend NF to NRF Client. |
| Type | Counter |
| Dimensions |
|
Table 9-630 nrfclient_on_demand_processing_latency_seconds_bucket
| Field | Details |
|---|---|
| Description | Total message processing time duration in seconds. |
| Type | Histogram |
| Dimensions |
|
Table 9-631 ocpm_nrf_tracing_request_timeout_total
| Field | Details |
|---|---|
| Description | Total number of requests timeout sent to the backend NF from NRF Client. |
| Type | Counter |
| Dimensions |
|
Table 9-632 nrfclient_dns_lookup_request_total
| Field | Details |
|---|---|
| Description | Total number of times a DNS lookup request is sent to
the alternate route service.
Note: The metric is pegged
only if |
| Type | Counter |
| Dimensions |
|
Table 9-633 nrfclient_dns_lookup_response_total
| Field | Details |
|---|---|
| Description | Total number of times a DNS lookup response is
received from the alternate route service.
Note: The
metric is pegged only if
|
| Type | Counter |
| Dimensions |
|
Table 9-634 nrfclient_dns_register_request_total
| Field | Details |
|---|---|
| Description | Total number of times a DNS register request is sent
to the alternate route service.
Note: The metric is pegged
only if |
| Type | Counter |
| Dimensions |
|
Table 9-635 nrfclient_nw_conn_out_request_total
| Field | Details |
|---|---|
| Description | Total number of times NRF-client has sent a request to NRF. This includes autonomous requests as well as on-demand requests. |
| Type | Counter |
| Dimensions |
|
| Example | nrfclient_nw_conn_out_request_total {MessageType="AutonomousNfRegistration",NfFqdn="ocpcf-occnp-ingress-gateway.gate-beta-b-25671603-gate-pcf.svc.cluster.local",NfInstanceID="fe7d992b-0541-4c7d-ab84-c6d70b1b0420",NfType="PCF",NrfURI="ocnrf-ingressgateway.gate-beta-b-25671603-gate-nrf.svc.cluster.local:80",OutgoingPriorityHeader="UNKNOWN",Priority="UNKNOWN",TargetNfType="UNKNOWN"} 2.0
nrfclient_nw_conn_out_request_total {MessageType="NfHeartBeat",NfFqdn="ocpcf-occnp-ingress-gateway.gate-beta-b-25671603-gate-pcf.svc.cluster.local",NfInstanceID="fe7d992b-0541-4c7d-ab84-c6d70b1b0420",NfType="PCF",NrfURI="ocnrf-ingressgateway.gate-beta-b-25671603-gate-nrf.svc.cluster.local:80",OutgoingPriorityHeader="UNKNOWN",Priority="UNKNOWN",TargetNfType="UNKNOWN"} 11000.0 |
Table 9-636 nrfclient_nw_conn_in_response_total
| Field | Details |
|---|---|
| Description | Total number of times NRF-client has received a response from NRF. |
| Type | Counter |
| Dimensions |
|
| Example | occnp_nrfclient_nw_conn_in_response_total{ApplicationError="INVALID_API",MessageType="NfDiscovery",NfFqdn="occnp-ocpm-ingress-gateway.ocpcf.svc",NfInstanceID="fe7d992b-0541-4c7d-ab84-c6d70b1b0123",NfType="PCF",StatusCode="400",} 2.0 |
Table 9-637 nrfclient_nw_conn_in_notify_request_total
| Field | Details |
|---|---|
| Description | Total number of nfStatusNotify requests received from NRF. |
| Type | Counter |
| Dimensions |
|
Table 9-638 nrfclient_nw_conn_out_notify_response_total
| Field | Details |
|---|---|
| Description | Total number of nfStatusNotify responses sent to NRF. |
| Type | Counter |
| Dimensions |
|
| Example | occnp_nrfclient_nw_conn_out_notify_response_total # TYPE occnp_nrfclient_nw_conn_out_notify_response_total counter occnp_nrfclient_nw_conn_out_notify_response_total{EventType="NF_REGISTERED",HttpStatusCode="400",NfInstanceID="4947a69a-f61b-4bc1-b9da-47c9c5d14b64",} 1.0 |
Table 9-639 nrfclient_network_message_processing_latency
| Field | Details |
|---|---|
| Description | Total message processing time duration. |
| Type | Histogram |
| Dimensions |
|
Table 9-640 occnp_nrfclient_discovery_cache_support_force_discovery_total
| Field | Details |
|---|---|
| Description | Indicates the total number of requests received from backend services with header OC-Force-Rediscovery is enabled, and response is retrieved from NRF. |
| Type | Counter |
| Dimensions |
|
Table 9-641 occnp_nrfclient_discovery_cache_support_cache_hit_total
| Field | Details |
|---|---|
| Description | Indicates the total number of requests for which discovery response is returned from the cache. |
| Type | Counter |
| Dimensions |
|
Table 9-642 occnp_nrfclient_discovery_cache_support_about_to_expire_total
| Field | Details |
|---|---|
| Description | Indicates the total number of cache records identified as about to be expired. This metric counts cases when a cached discovery response is eligible to be returned but also triggers a background request to get an updated response.
Note: This metrics is incremented when a valid cached discovery response is found and its remaining lifetime is within refreshBeforeExpiryTime, and not immediately when the threshold condition is reached. |
| Type | Counter |
| Dimensions |
|
Table 9-643 occnp_nrfclient_discovery_cache_support_expired_total
| Field | Details |
|---|---|
| Description | Metric for expired cache record scenario. This metric counts cases when a cached discovery response is not eligible to be returned due to expiration and a new response must be retrieved again from NRF. |
| Type | Counter |
| Dimensions |
|
Table 9-644 occnp_nrfclient_discovery_cache_support_failover
| Field | Details |
|---|---|
| Description | Metric for cache fail over scenario. This metric counts cases when the response was returned by the cache fail over logic. |
| Type | Counter |
| Dimensions |
|
Table 9-645 occnp_nrfclient_discovery_cache_support_cache_non_cache_total
| Field | Details |
|---|---|
| Description | Metric for non-cache scenario. This metrics counts cases when the discovery request parameters do not fully match with the configuration parameters. |
| Type | Counter |
| Dimensions |
|
Table 9-646 occnp_nrfclient_discovery_cache_support_empty_response_total
| Field | Details |
|---|---|
| Description | Metric for empty response scenario. This metric will count cases when an empty response was returned to NF from Cache or NRF. |
| Type | Counter |
| Dimensions |
|
Table 9-647 occnp_nrfclient_discovery_cache_support_cache_lookup_seconds
| Field | Details |
|---|---|
| Description | Metric for cache lookups. This metric measures time taken to perform cache lookups from cache or DB without considering the complete request flow. |
| Type | Histogram |
| Dimensions |
|
Table 9-648 occnp_nrfclient_discovery_cache_support_backend_response_seconds
| Field | Details |
|---|---|
| Description |
Metric for cached and non-cached responses returned to backend NF. This metric measures the time taken to perform the complete request flow when response was taken from cache or DB or NRF. |
| Type | Histogram |
| Dimensions |
|
Table 9-649 occnp_nrfclient_discovery_cache_support_cache_lookup_seconds_bucket
| Field | Details |
|---|---|
| Description | This metric is used to perform the cache lookup. |
| Type | Histogram |
| Dimensions |
|
| Examples | occnp_nrfclient_discovery_cache_support_cache_lookup_seconds_bucket{NfFqdn="occnp-ocpm-ingress-gateway.ocpcf.svc",NfInstanceID="fe7d992b-0541-4c7d-ab84-c6d70b1b0123",NfType="PCF",le="0.01",} 19.0 |
Table 9-650 occnp_nrfclient_discovery_cache_support_cache_lookup_seconds_count
| Field | Details |
|---|---|
| Description | This metric is used to get a count of cache lookup requests. |
| Type | Histogram |
| Dimensions |
|
| Examples | occnp_nrfclient_discovery_cache_support_cache_lookup_seconds_count{NfFqdn="occnp-ocpm-ingress-gateway.ocpcf.svc",NfInstanceID="fe7d992b-0541-4c7d-ab84-c6d70b1b0123",NfType="PCF",} 19.0 |
Table 9-651 occnp_nrfclient_discovery_cache_support_cache_lookup_seconds_max
| Field | Details |
|---|---|
| Description | This metric provides the maximum value of cache lookup. |
| Type | Gauge |
| Dimensions |
|
| Examples | occnp_nrfclient_discovery_cache_support_cache_lookup_seconds_max{NfFqdn="occnp-ocpm-ingress-gateway.ocpcf.svc",NfInstanceID="fe7d992b-0541-4c7d-ab84-c6d70b1b0123",NfType="PCF",} 1.7408E-5 |
Table 9-652 occnp_nrfclient_discovery_cache_support_cache_lookup_seconds_sum
| Field | Details |
|---|---|
| Description | This metric provides the sum of cache lookup. |
| Type | Histogram |
| Dimensions |
|
| Examples | occnp_nrfclient_discovery_cache_support_cache_lookup_seconds_sum{NfFqdn="occnp-ocpm-ingress-gateway.ocpcf.svc",NfInstanceID="fe7d992b-0541-4c7d-ab84-c6d70b1b0123",NfType="PCF",} 0.001040425 |
Table 9-653 occnp_nrfclient_discovery_cache_support_backend_response_seconds_bucket
| Field | Details |
|---|---|
| Description | This metric is used to peg the backend response time for cached and non-cached responses |
| Type | Histogram |
| Dimensions |
|
| Examples | occnp_nrfclient_discovery_cache_support_backend_response_seconds_bucket{NfFqdn="occnp-ocpm-ingress-gateway.ocpcf.svc",NfInstanceID="fe7d992b-0541-4c7d-ab84-c6d70b1b0123",NfType="PCF",SourceType="Cache",le="0.01",} 19.0 |
Table 9-654 occnp_nrfclient_discovery_cache_support_backend_response_seconds_count
| Field | Details |
|---|---|
| Description | This metric provides the count of cached responses. |
| Type | Histogram |
| Dimensions |
|
| Examples | occnp_nrfclient_discovery_cache_support_backend_response_seconds_count{NfFqdn="occnp-ocpm-ingress-gateway.ocpcf.svc",NfInstanceID="fe7d992b-0541-4c7d-ab84-c6d70b1b0123",NfType="PCF",SourceType="Cache",} 19.0 |
Table 9-655 occnp_nrfclient_discovery_cache_support_backend_response_seconds_max
| Field | Details |
|---|---|
| Description | This metric provides maximum backend response time for cached responses. |
| Type | Gauge |
| Dimensions |
|
| Examples | occnp_nrfclient_discovery_cache_support_backend_response_seconds_max{NfFqdn="occnp-ocpm-ingress-gateway.ocpcf.svc",NfInstanceID="fe7d992b-0541-4c7d-ab84-c6d70b1b0123",NfType="PCF",SourceType="Cache",} 3.2963E-5 |
Table 9-656 occnp_nrfclient_discovery_cache_support_backend_response_seconds_sum
| Field | Details |
|---|---|
| Description | This metric provides the sum of backend response time for cached responses. |
| Type | Histogram |
| Dimensions |
|
| Examples | occnp_nrfclient_discovery_cache_support_backend_response_seconds_sum{NfFqdn="occnp-ocpm-ingress-gateway.ocpcf.svc",NfInstanceID="fe7d992b-0541-4c7d-ab84-c6d70b1b0123",NfType="PCF",SourceType="Cache",} 0.001164615 |
Table 9-657 occnp_nrfclient_discovery_cache_support_profiles_per_response_bucket
| Field | Details |
|---|---|
| Description |
This metric is used to measure the number of producer profiles returned to backend NF. |
| Type | Histogram |
| Dimensions |
|
| Examples | occnp_nrfclient_discovery_cache_support_profiles_per_response_bucket{NfFqdn="occnp-ocpm-ingress-gateway.ocpcf.svc",NfInstanceID="fe7d992b-0541-4c7d-ab84-c6d70b1b0123",NfType="PCF",SourceType="Cache",le="1.0",} 1.0 |
Table 9-658 occnp_nrfclient_discovery_cache_support_profiles_per_response_count
| Field | Details |
|---|---|
| Description | This metric provides the count of number of producer profiles returned to backend NF for all responses. |
| Type | Histogram |
| Dimensions |
|
| Examples | occnp_nrfclient_discovery_cache_support_profiles_per_response_count{NfFqdn="occnp-ocpm-ingress-gateway.ocpcf.svc",NfInstanceID="fe7d992b-0541-4c7d-ab84-c6d70b1b0123",NfType="PCF",SourceType="Cache",} 19.0 |
Table 9-659 occnp_nrfclient_discovery_cache_support_profiles_per_response_max
| Field | Details |
|---|---|
| Description | This metric provides the maximum number of producer profiles returned to backend NF in particular response. |
| Type | Gauge |
| Dimensions |
|
| Examples | occnp_nrfclient_discovery_cache_support_profiles_per_response_max{NfFqdn="occnp-ocpm-ingress-gateway.ocpcf.svc",NfInstanceID="fe7d992b-0541-4c7d-ab84-c6d70b1b0123",NfType="PCF",SourceType="Cache",} 5.0 |
Table 9-660 occnp_nrfclient_discovery_cache_support_profiles_per_response_sum
| Field | Details |
|---|---|
| Description | This metric provides the sum of producer profiles returned to backend NF in all responses. |
| Type | Histogram |
| Dimensions |
|
| Examples | occnp_nrfclient_discovery_cache_support_profiles_per_response_sum{NfFqdn="occnp-ocpm-ingress-gateway.ocpcf.svc",NfInstanceID="fe7d992b-0541-4c7d-ab84-c6d70b1b0123",NfType="PCF",SourceType="NRF",} 420.0 |
Table 9-661 occnp_nrfclient_nfUpdate_status
| Field | Details |
|---|---|
| Description | This metric marks the status of the NfUpdate Service Operation. |
| Type | Gauge |
| Dimensions |
|
| Examples | occnp_nrfclient_nfUpdate_status{NfFqdn="occnp-occnp-ingress-gateway.occnp", NfInstanceID="fe7d992b-0541-4c7d-ab84-c6d2410a2410", NfType="PCF", app_kubernetes_io_instance="occnp", app_kubernetes_io_managed_by="Helm", app_kubernetes_io_name="nrf-client-nfmanagement", app_kubernetes_io_part_of="nrf-client", app_kubernetes_io_version="24.1.5.0.0", application="occnp", container="nrf-client-nfmanagement", endpoint="cnc-metrics", engVersion="24.1.5", helm_sh_chart="nrf-client-nfmanagement-24.1.5", instance="10.233.109.152:9000", io_kompose_service="occnp-occnp-nrf-client-nfmanagement", job="occne-infra/occne-nf-cnc-podmonitor", microservice="occnp-nrf-client-nfmanagement", mktgVersion="24.1.5.0.0", namespace="occnp", pod="occnp-occnp-nrf-client-nfmanagement-8f94667cf-bbhls", pod_template_hash="8f94667cf", vendor="Oracle"} |
9.32 Error Mapping Metrics
Table 9-662 occnp_error_handler_in_total
| Field | Details |
|---|---|
| Description | This metric counts the number of requests reached the error-handler. This metric is incremented on initialization of error handling. |
| Type | Counter |
| Dimensions |
|
| Example | occnp_error_handler_in_total{application="policyds",application_exception="HttpException",wrapped_exception="TimeoutException",} 1.0 |
Table 9-663 occnp_error_handler_exec_total
| Field | Details |
|---|---|
| Description | This metric counts the number of times error handling is performed. It will only increment if a rule is found and executed. Metric on error handling performed by framework. |
| Type | Counter |
| Dimensions |
|
| Example | occnp_error_handler_exec_total{application="policyds",application_exception="HttpException",error_type="INTERNAL",operation="LOOKUP",origin="HTTP",rule_name="HTTP_REQUEST",source_interface="POLICY",status="502",target_interface="BSF",wrapped_exception="BadGateway",} 1.0 |
Table 9-664 occnp_error_handler_out_total
| Field | Details |
|---|---|
| Description | This metric counts the number of requests exited the error-handler. This metric is incremented on completion of error handling. |
| Type | Counter |
| Dimensions |
|
| Example | occnp_error_handler_out_total{application="policyds",application_exception="HttpException",error_resolved="true",wrapped_exception="BadRequest",} 1.0 |
9.33 Metrics for Automated Certificate Lifecycle Management
The following metrics are used to support automated certificate lifecycle management for Policy:
Table 9-665 oc_certificatemanagement_tls_certificate_info
| Field | Details |
|---|---|
| Description | This metric is used to peg status of TLS certificates. |
| Type | Guage |
| Dimensions |
|
| Example |
9.34 Common Metrics
This section describes the metrics and examples for metrics that are common to all the services.
Table 9-666 occnp_http_message_priority_request_count_total
| Field | Details |
|---|---|
| Description | This metric is pegged when PCF receives an incoming request or there is an outgoing request from PCF.
This metric applies to the SM service, User Services (CHF Connector and UDR Connector), and Binding Services. Future releases might add support for additional services. |
| Type | Counter |
| Dimensions |
|
| Example |
occnp_http_message_priority_request_count_total{app_kubernetes_io_instance="xxx", app_kubernetes_io_managed_by="Helm", app_kubernetes_io_name="sm-service", app_kubernetes_io_part_of="occnp", app_kubernetes_io_version="26.1.200-ocngf-pre-dev-xxx.0.0", application="occnp", container="sm-service", direction="in", endpoint="cnc-metrics", engVersion="26.1.200-ocngf-pre-dev-titans", eval_priority="24", exported_application="pcf_smservice", helm_sh_chart="sm-service-26.1.200-ocngf-pre-dev-xxx", hostname="xxx-pcf-smservice-74d9d88474-jqn4m", instance="10.233.114.76:9000", interfaceType="Npcf_SMPolicyControl", io_kompose_service="xxx-pcf-smservice", job="occne-infra/occne-nf-cnc-podmonitor", microservice="occnp_pcf_sm", mktgVersion="26.1.200-ocngf-pre-dev-xxx.0.0", msgType="Create", namespace="hm3-ns03", pod="titans-pcf-smservice-74d9d88474-jqn4m", pod_template_hash="74d9d88474", rcvd_priority="24", vendor="Oracle"} 1.0 occnp_http_message_priority_request_count_total{app_kubernetes_io_instance="xxx", app_kubernetes_io_managed_by="Helm", app_kubernetes_io_name="user-service", app_kubernetes_io_part_of="occnp", app_kubernetes_io_version="26.1.200-ocngf-pre-dev-xxx.0.0", application="occnp", container="user-service", direction="out", endpoint="cnc-metrics", engVersion="26.1.200-ocngf-pre-dev-xxx", eval_priority="NA", exported_application="pcf_userservice", helm_sh_chart="user-service-26.1.200-ocngf-pre-dev-xxx", hostname="xxx-occnp-udr-connector-7f75dcf879-nlp6m", instance="10.233.114.174:9000", interfaceType="Nudr_DataRepository", io_kompose_service="xxx-occnp-udr-connector", job="occne-infra/occne-nf-cnc-podmonitor", microservice="occnp_pcf_user", mktgVersion="26.1.200-ocngf-pre-dev-xxx.0.0", msgType="Get_Policy_Data", namespace="hm3-ns03", pod="xxx-occnp-udr-connector-7f75dcf879-nlp6m", pod_template_hash="7f75dcf879", rcvd_priority="24", vendor="Oracle"} 1.0 |
Table 9-667 occnp_http_message_priority_response_count_total
| Field | Details |
|---|---|
| Description | This metric is pegged when PCF receives an incoming response or when there is an outgoing response from PCF.
This metric applies to the SM service, User Services (CHF Connector and UDR Connector), and Binding Services. Future releases might add support for additional services. |
| Type | Counter |
| Dimensions |
Note: response_code always reflects the specific code received, such as 200, 201, 404, or 500. References to 1xx, 2xx, 3xx, 4xx, or 5xx are used as placeholders for groups of response codes and should not be interpreted as actual output values from the metric. |
| Example |
occnp_http_message_priority_response_count_total{app_kubernetes_io_instance="xxx", app_kubernetes_io_managed_by="Helm", app_kubernetes_io_name="sm-service", app_kubernetes_io_part_of="occnp", app_kubernetes_io_version="26.1.200-ocngf-pre-dev-xxx.0.0", application="occnp", container="sm-service", direction="out", endpoint="cnc-metrics", engVersion="26.1.200-ocngf-pre-dev-titans", eval_priority="NA", exported_application="pcf_smservice", helm_sh_chart="sm-service-26.1.200-ocngf-pre-dev-xxx", hostname="xxx-pcf-smservice-74d9d88474-jqn4m", instance="10.233.114.76:9000", interfaceType="Npcf_SMPolicyControl", io_kompose_service="xxx-pcf-smservice", job="occne-infra/occne-nf-cnc-podmonitor", microservice="occnp_pcf_sm", mktgVersion="26.1.200-ocngf-pre-dev-xxx.0.0", msgType="Create", namespace="hm3-ns03", pod="xxx-pcf-smservice-74d9d88474-jqn4m", pod_template_hash="74d9d88474", rcvd_priority="NA", responseCode="201", vendor="Oracle"} occnp_http_message_priority_response_count_total{app_kubernetes_io_instance="xxx", app_kubernetes_io_managed_by="Helm", app_kubernetes_io_name="user-service", app_kubernetes_io_part_of="occnp", app_kubernetes_io_version="26.1.200-ocngf-pre-dev-xxx.0.0", application="occnp", container="user-service", direction="in", endpoint="cnc-metrics", engVersion="26.1.200-ocngf-pre-dev-xxx", eval_priority="NA", exported_application="pcf_userservice", helm_sh_chart="user-service-26.1.200-ocngf-pre-dev-xxx", hostname="xxx-occnp-udr-connector-7f75dcf879-nlp6m", instance="10.233.114.174:9000", interfaceType="Nudr_DataRepository", io_kompose_service="xxx-occnp-udr-connector", job="occne-infra/occne-nf-cnc-podmonitor", microservice="occnp_pcf_user", mktgVersion="26.1.200-ocngf-pre-dev-titans.0.0", msgType="Subscribe", namespace="hm3-ns03", pod="xxx-occnp-udr-connector-7f75dcf879-nlp6m", pod_template_hash="7f75dcf879", rcvd_priority="NA", responseCode="201", vendor="Oracle"} |
Table 9-668 hikaricp_connections_idle
| Field | Details |
|---|---|
| Description | Number of established but idle connections. |
| Type | Gauge |
| Dimension |
|
| Example | hikaricp_connections_idle{application="bsf-management-service",name="dataSource", |
Table 9-669 hikaricp_connections_max
| Field | Details |
|---|---|
| Description | Maximum number of active connections that can be allocated at the same time. |
| Type | Gauge |
| Dimension |
|
| Example | hikaricp_connections_max{application="bsf-management-service",name="dataSource", |
Table 9-670 hikaricp_connections_min
| Field | Details |
|---|---|
| Description | Minimum number of idle connections in the pool. |
| Type | Gauge |
| Dimension |
|
| Example | hikaricp_connections_min{application="bsf-management-service",name="dataSource", |
Table 9-671 hikaricp_connections_active
| Field | Details |
|---|---|
| Description | Current number of active connections that have been allocated from the data source. |
| Type | Gauge |
| Dimension |
|
| Example | hikaricp_connections_active{application="bsf-management-service",name="dataSource", |
Table 9-672 executor_queued_tasks
| Field | Details |
|---|---|
| Description | |
| Type | Gauge |
| Dimension |
|
| Example |
executor_queued_tasks{application="xxx",hostname="xx", name="HttpServerCustomThreadPoolExecutor"} 0.0 |
Table 9-673 executor_active_threads
| Field | Details |
|---|---|
| Description | |
| Type | Gauge |
| Dimension |
|
| Example |
executor_active_threads{application="xxx",hostname="xx", name="HttpServerCustomThreadPoolExecutor"} |
Table 9-674 executor_pool_max_threads
| Field | Details |
|---|---|
| Description | Undertow max worker pool size. |
| Type | Gauge |
| Dimensions |
|
| Example |
executor_pool_max_threads{application="xx",hostname="xx", name="HttpServerCustomThreadPoolExecutor"} 16.0 |
Table 9-675 executor_pool_size_threads
| Field | Details |
|---|---|
| Description | Undertow worker pool size. |
| Type | Gauge |
| Dimensions |
|
| Example |
executor_pool_size_threads{application="xx",hostname="xx", name="HttpServerCustomThreadPoolExecutor"} 4.0 |
9.35 ASM Metrics
This section describes the ASM metrics.
Table 9-676 upstream_rq_timeout
| Field | Details |
|---|---|
| Description | Maximum duration allowed for a request to an upstream service to complete, including any retries. This timeout is a critical configuration in proxy services like Envoy, which sits between downstream clients and upstream servers. |
| Type | Counter |
| Dimension |
|
| Example | {cluster_name="inbound|8000||", microservice="occnp_pcf_sm"} |
Table 9-677 upstream_rq_active
| Field | Details |
|---|---|
| Description | Tracks the number of currently active, or in-flight, requests to an upstream service. This metric is crucial for monitoring service mesh performance and resource utilization. |
| Type | Gauge |
| Dimension |
|
| Example | {cluster_name="inbound|8000||", microservice="occnp-occnp-ingress-gateway"} |
Table 9-678 upstream_rq_rx_reset
| Field | Details |
|---|---|
| Description | Its an Envoy proxy counter that tallies the number of upstream requests that were terminated by a TCP connection reset from the remote, or upstream, host. |
| Type | Counter |
| Dimension |
|
| Example | {cluster_name="inbound|8000||", microservice="occnp-occnp-egress-gateway"} |
Table 9-679 upstream_rq_tx_reset
| Field | Details |
|---|---|
| Description | It is an Envoy-level counter that tracks the total number of HTTP requests that were reset locally by the Envoy proxy before receiving a response from the upstream service. |
| Type | Counter |
| Dimension |
|
| Example | {cluster_name="inbound|38868||", microservice="oc-diam-gateway"} |
Table 9-680 upstream_cx_active
| Field | Details |
|---|---|
| Description | It is an Envoy metric that tracks the number of currently active connections from an Envoy proxy to its upstream cluster. It is used in service mesh technologies like Istio and AWS App Mesh, which rely on the Envoy proxy for their data plane. |
| Type | Gauge |
| Dimension |
|
| Example | {cluster_name="prometheus_stats", microservice="occnp_pcf_sm"} |
Table 9-681 downstream_cx_ssl_total
| Field | Details |
|---|---|
| Description | It is a counter used by the Envoy proxy to track the total number of new downstream client connections that used a Secure Sockets Layer (SSL) or Transport Layer Security (TLS) handshake. |
| Type | Counter |
| Dimension |
|
| Example | {cluster_name="xds-grpc", microservice="occnp_pcf_sm"} |
Table 9-682 downstream_cx_http2_active
| Field | Details |
|---|---|
| Description | It refers to the number of currently active HTTP/2 connections from a client (the "downstream"). |
| Type | Gauge |
| Dimensions |
|
| Example | {cluster_name="prometheus_stats", microservice="occnp-occnp-egress-gateway"} |
Table 9-683 downstream_cx_active
| Field | Details |
|---|---|
| Description | It measures the number of active network connections to a service proxy like Envoy, and is used to monitor the performance and stability of a service. |
| Type | Gauge |
| Dimensions |
|
| Example | {cluster_name="prometheus_stats", microservice="occnp-occnp-ingress-gateway"} |
Table 9-684 downstream_cx_total
| Field | Details |
|---|---|
| Description | Counts the total number of connections that Envoy has accepted from its downstream clients (like web browsers or mobile apps) to a specific listener. It's a counter metric that helps in understanding overall connection volume and can be used to calculate connections per second (CPS) and analyze connection churn, indicating the rate at which clients are creating and closing connections to the proxy. |
| Type | Counter |
| Dimensions |
|
| Example | {cluster_name="xds-grpc", microservice="occnp-occnp-egress-gateway"} |
9.36 Sbi-NF-Peer-Info Header Metrics
The following table describes the Sbi-NF-Peer-Info Header Metrics:
operation_type: Identifies the SBI operation associated with theNF-Peer-Infoheader. Supported values are:create: Used for create operations, such as SM Create and Binding Register to BSF.update: Used for update operations, such as SM Update.delete: Used for delete operations, such as SM Delete, Binding Deregister to BSF, and UDR connector delete operations.update_notify: Used for update notification messages sent to the SMF.terminate_notify: Used for termination notification messages sent to the SMF.subscribe: Used for subscription requests sent to the CHF.unsubscribe: Used for unsubscription requests sent to the CHF.AuditNotify: Used for BSF audit operations in the binding service.get: Used for UDR connector get operations.post: Used for UDR connector post operations.patch: Used for UDR connector patch operations.put: Used for UDR connector put operations.notify: Used for notifications sent to the UDR or CHF connector.
external_nf: Identifies the external NF that participates in the communication. Supported values are:SMF: Communication between PCF and SMF.UDR: Communication between PCF and UDR.CHF: Communication between PCF and CHF.BSF: Communication between PCF and BSF.
validation_status: Indicates whether the received 3gpp-Sbi-NF-Peer-Info header satisfies the NF-Peer-Info validation rules defined for this feature. Supported values are:invalid: Set when the received NF-Peer-Info header contains the srcservinst parameter without the corresponding srcinst parameter.valid: Set for all received headers that do not meet the invalid condition.NA: Used for all metrics associated with NF-Peer-Info headers sent by PCF to external NFs.
Note:
Thevalidation_status dimension is based only on the NF-Peer-Info attribute dependency validation defined earlier. It does not validate the format, syntax, or contents of individual header parameters, such as srcinst, srcservinst, dstinst, or dstservinst. For example, UUID format validation is not performed when determining the dimension value.
Table 9-685 occnp_nf_peer_info_header_received_total
| Field | Details |
|---|---|
| Description |
The PCF reports the total number of incoming HTTP messages that include the 3gpp-Sbi-NF-Peer-Info header. |
| Metric Type | Counter |
| Dimensions |
|
- occnp_nf_peer_info_header_received_total{application="pcf_smservice",dst_instance="di48b3cb-265d-40fe-9368-db4ac72b7716",dst_serv_instance="dsi48b3cb-265d-40fe-9368-db4ac72b7716",external_nf="SMF",operation_type="create",src_instance="si48b3cb-265d-40fe-9368-db4ac72b7716",src_serv_instance="ss48b3cb-265d-40fe-9368-db4ac72b7716",validation_status="valid"} 1.0
- occnp_nf_peer_info_header_received_total{application="pcf_smservice",dst_instance="di48b3cb-265d-40fe-9368-db4ac72b7716",dst_serv_instance=" ",external_nf="SMF",operation_type="create",src_instance=" ",src_serv_instance="ssi48b3cb-265d-40fe-9368-db4ac72b7716",validation_status="invalid"} 1.0
Table 9-686 occnp_nf_peer_info_header_sent_total
| Field | Details |
|---|---|
| Description |
The PCF reports the total number of outgoing HTTP messages that include the 3gpp-Sbi-NF-Peer-Info header. |
| Metric Type | Counter |
| Dimensions |
|
- occnp_nf_peer_info_header_sent_total{application="pcf_smservice",dst_instance="si48b3cb-265d-40fe-9368-db4ac72b7716",dst_serv_instance="ss48b3cb-265d-40fe-9368-db4ac72b7716",external_nf="SMF",operation_type="create",src_instance="site1",src_serv_instance="03063893-cf9e-4f7a-9827-067f6fa9dd02",validation_status="NA"} 1.0