5 Metrics
This chapter provides information about newly introduced and updated metrics and its dimensions.
The following table describes the SCP metric types used to measure the health and performance of SCP and its core functionalities:
Table 5-1 Metric Type
Metric Type | Description |
---|---|
Counter |
Represents the total number of occurrences of an event or traffic, such as measuring the total amount of traffic received and transmitted by SCP, and so on. |
Gauge |
Represents a single numerical value that changes randomly. This metric type is used to measure various parameters, such as SCP load values, memory usage, and so on. |
Histogram | Represents the number of occurrences that fall into predefined intervals, or buckets, such as those used for measuring response times. |
5.1 SCP OCI Metrics Dashboard
ocscp_oci_metric_dashboard_25.1.100.zip
file on OCI Logging Analytics Dashboard Service, see Oracle Communications Cloud Native Core, OCI Deployment Guide. OCI does not support
Grafana, OCI uses the Logging Analytics Dashboard Service for
visualizing the metrics and logs.
5.2 Dimension Description
The following table provides information on Dimension of Metrics.
Table 5-2 SCP Dimension Descriptions
Dimension | Description |
---|---|
ocscp_nf_type | Includes the producer NF type that is extracted from the
URI of the message.
The sample values are UDM, PCF, AMF, and so on. |
ocscp_nf_service_type | Service name of the producer NF in delegated discovery
metrics. Includes the producer NF Service type that is extracted from
the URI of the message.
The sample values are nudm-uecm, nudm-sdm, scpc-notification, and so on. Note:
|
ocscp_req_msg_size | Indicates the request message size buckets.
The sample values are 1(size < 1k bytes), 2 (1k < size < 2k bytes), 4 (2k < size < 4k ), and so on. |
ocscp_locality | Indicates the SCP site name or locality name with which
SCP is deployed.
The sample values are Loc6, Loc7, and so on. |
ocscp_fqdn | Includes the FQDN of SCP, which is used to deploy SCP. |
plmn_id |
It represents the PLMN of the destination where the request needs to be routed. |
ocscp_authority | Includes the authority of SCP.
The sample value is FQDN:PORT or IP:PORT. Note: This
dimension will get pegged only when it is enabled using
values.yaml .scpAuthorityMetricLabelDisabled: false |
ocscp_message_type | Includes the message type received at SCP. It can be of
any of the following types:
|
ocscp_consumer_host | Includes the consumer host details extracted from the
user-agent header. SCP should be able to decode that particular format
only if the user-agent header is available in certain allowed
configurable formats.
Note: The ocscp_consumer_host dimension
will include the value OCSCP-INITIATED-MSG only in the case of SCP
self-generated requests. These requests can be identified based on
the header
( |
ocscp_consumer_nf_inst ance_id | Includes the consumer NF Instance ID details extracted from the user-agent header. SCP should be able to decode that particular format only if the user-agent header is available in certain allowed configurable formats. |
ocscp_consumer_nf_type | Includes consumer NF type details extracted from the user-agent header. SCP should be able to decode that particular format only if the user-agent header is available in certain allowed configurable formats. |
ocscp_consumer_nf_unique_id | Includes the consumer NF's Unique ID details extracted from the user-agent header. SCP should be able to decode that particular format only if the user-agent header is available in certain allowed configurable formats. |
ocscp_peer_nf_instance_id | NF Instance ID of the peer to which message (request or
response) is routed.
For requests, the NF instance ID is obtained from information on a known NF producer or consumer. For responses, the NF Instance ID is obtained from the User-Agent/XFCC header. SCP should be able to decode that particular format only if the user-agent header is available in certain allowed configurable formats. |
ocscp_peer_nf_service_type |
NF service type of peer to which message (request or response) is routed. For requests, the NF service type is obtained from information on a known NF producer or consumer. For responses, service type is obtained from learned information about NF extracted from the User-Agent/XFCC header. SCP should be able to decode that particular format only if the user-agent header is available in certain allowed configurable formats. |
action | Action taken ("error_sent" or "rerouted") on request throtteling because of OCI enforcement. |
scope | The OCI scope received in the OCI header. |
auditMode | The mode of Audit in which SCP performs with NRF using
NRF discovery or management services.
The possible values are "nnrf-disc" Or "nnrf-mgmt" |
auditType | Type of audit triggered by the audit microservice. It can
be an on-demand audit or a regular audit, depending on what triggered
the audit. Example: A change in TSI from local to NRF will trigger an
on-demand audit.
The possible values are "OnDemand" and "Scheduled". |
bodyModified | This dimension is used to know if the response received from mediation has any changes in the body that is sent in the request towards mediation. |
bucketKey | The key used to maintain the value of the message rate in egress or ingress rate limit functionality. |
cause | The reason for the event's occurrence. The value can vary from one metric to another. |
cca_consumer_nfInstanceId | The NF instance ID of the consumer sending the CCA header. |
certificate_type | The type of certificate used, such as primary server, secondary server, etc. |
certificate_type | Indicates the type of certificates that are about to
expire.
The following are the valid applicable certificate
types:
|
coherenceCluster | The name of the coherence cluster used in the SCP deployment. |
configurationName | The name of the configuration that has changed. |
cpu_level | The level for CPU utilization, whether it is under minor, major, or critical utilization levels based on the configurations. |
dbOperation | The DB operation that happened on a DB table. Example: find, findAll, save, saveAll, get, count, delete, deleteAll. |
destination | Indicates the destination SVC, like scpc-notification, scp-nrfproxy, and so on. |
destination (TLS) | Contains the destination address details involved in HTTPS connection. |
detail | This dimension contains details about the issue that has happened. |
duplicateTargetFqdn | When a duplicate target fqdn is detected across different NRF SRV fqdns. |
error-reason | Reason for ingress or egress connection failures. |
errorType | The error reason that caused notification processing to fail. |
eventName | Showing the migration state of the NRF DNS SRV feature.
Possible values are:
|
eventType | It shows the status of the egress requests on the Jetty client or the event type received in notification requests from NRF. This is used in different metrics, thus refer to the respective metric for interpretation. |
failureReason | Reasons for the failure of the NRF DNS SRV feature migration. |
failureReason (TLS) | Contains HTTPS connection failure reason (Handshake failure reason) |
headerModified | Indicates whether any header is modified by the mediation service in response. |
host_type | Indicates the host type used for sending the request. For example, "IP" or "FQDN". |
http_method | Indicates the HTTP method of the request getting treatment for overload. For example, PUT, PATCH, POST, and so on. |
interScpHost | Contains the host of the SCP to which the request is being sent. |
is_from_local_cache | Defines whether the NRF discovery response is reterived from local cache (true) or NRF (false) |
is_inter_plmn | Defines whether NRF Delegated Discovery made is for inter plmn (true) or for intra plmn (false) |
locality | The locality of the foreign NF. |
lockEvent | The notification cache lock event (released or acquired) |
msName | The name of the scp microservice. |
nfInstanceId | The producer NF instance ID. |
nfProfileProcessingStatus | The status of the notification profile processing. |
nf_status | The status of NF, for example, REGISTERED. |
nfType | The NF type, for example, UDM. |
notificationSource | Indicates the source of notification received at the Notification microservice. It can be NRF or some SCP microservice. |
rule_name | Denotes the rule that matches one of the discovery headers in the excludeDiscoveryQuery List, and hence caching is skipped. |
ocscp_producer_nf_type | Includes the producer NF type. |
nrfHost | NRF FQDN or IP address configured for audit. |
nrfRegionOrSetId | NRF region or SetId configrued for audit |
nrfSrvFqdn | NRF Fqdn configured in DNS SRV |
ocscp_alternate_nf_end_point | Selected alternate producer NF's end point. |
ocscp_alternate_producer_host | Selected alternate producer NF FQDN. |
ocscp_alternate_producer_nf_instance_id | Selected alternate producer NF's instance Id. |
ocscp_alternate_producer_service_instance_id | Selected alternate producer NF's service instance Id. |
ocscp_alternate_route_type | Alternate routing mechanism selected. |
ocscp_attempted_producers | List of attempted producers before sending back an error response to the consumer. |
ocscp_sub | Requester NF instance ID in the oauth2 token request. |
ocscp_aud | Target NF instance ID in the oauth2 token request. |
ocscp_cause |
Traffic Feed Metrics: Provides information on the cause of traffic feed failures (for example, unreachable, noleader, incorrect data director configuration). Routing Metrics: Provides information on the cause of routing failures. (for example, UnknowHostException, Circuit Breaking) Rate limit Metrics: Provides information on the cause for the rate limit not being applied (for example, configuration not found). |
ocscp_configured_egress_rate | Configured rate of egress rate limit for a NF. |
ocscp_configured_ingress_rate | Configured rate of ingress rate limit for a NF. |
ocscp_egress_rl_bucketkey | Key name for egress rate limit bucket. |
ocscp_error_condition | Error Condition resulting in routing attempt failure. |
ocscp_error_group | Error group for error condition resulting in Routing
Attempt Failure (for example, Destination webclient connection
failure).
Possible values:
|
ocscp_ingress_rl_bucketkey | Key name for the ingress rate limit bucket. |
ocscp_ingress_rl_headerformat | The User Agent header format used by SCP to extract consumer host information to apply an ingress rate limit. |
ocscp_ingress_rl_headername | Headers used to apply the ingress rate limit. |
ocscp_med_upstream_service_time | Time taken for mediation processing in milliseconds. |
ocscp_mediation_filtername | Name of the filter applied to send a request towards mediation. |
ocscp_mediation_triggerpoint | Trigger point used to send requests toward mediation. |
ocscp_nexthop_scp_fqdn | FQDN of the selected SCP for interscp requests. |
ocscp_nf_end_point |
The value of the ocscp_nf_end_point dimension can be "fqdn:port" if SCP routes the request using FQDN or "IP:port" if SCP routes the request using IP.
|
ocscp_nf_instance_id | Producer NF instance ID for health check metrics. |
ocscp_nf_setid | The NF setId of selected producer NF. If nfsetid is present in the discovery headers or routing binding headers, retrieve it from there; otherwise, it should be extracted from the nfprofile of producer. |
ocscp_nrf_service_type | Service name of the NRF NF in delegated discovery metrics. |
ocscp_peer_scp_fqdn | The FQDN of peer SCP. |
ocscp_peer_scp_instance_id | The NF instance Id of peer SCP. |
ocscp_primary_producer_fqdn | The FQDN of the selected primary producer NF, in the case of alternate routing. |
ocscp_processing_time | The bucket list of SCP requests or response processing times. |
ocscp_producer_host | The FQDN of selected producer NF. |
ocscp_producer_nf_fqdn | The FQDN of producer NF for InterSCP Metrics. |
ocscp_producer_nf_instance_id |
|
ocscp_producer_nf_type | The NF Type of producer NF selected by SCP.(For example, UDM, PCF and so on) |
ocscp_producer_service_instance_id |
Possible Values: Service instance ID format as defined in the specification. "NA" if service instance ID is unavailable. |
ocscp_res_msg_size |
Message size of the response sent by SCP to the consumer. Message size buckets. for example, 1 (size < 1k bytes), 2 (1k < size < 2k bytes), 4 (2k < size < 4k), etc. |
ocscp_response_code | Response code sent by SCP to the consumer (for example, a success response such as 200 or 201, an error response such as 503, 400, and so on.) |
ocscp_response_code_class | Response code class of response code sent by SCP to the consumer. (For example, response code class 2xx for success responses, 5xx, 4xx, or 3xx for error responses.) |
ocscp_scope | Scope NF Load received is applicable to nfInstance or serviceInstance. |
ocscp_scp_end_point | Producer SCP endpoint details for interSCP metrics. Endpoint details can contain a FQDN or IP address. |
ocscp_scp_instance_id | Producer SCP instance ID for interSCP metrics. |
ocscp_sepp_end_point | Selected SEPP endpoint details for InterPLMN metrics. Endpoint details can contain a FQDN or IP address. |
ocscp_sepp_fqdn | Selected SEPP FQDN details for InterPLMN metrics. |
ocscp_sepp_instance_id | Selected SEPP instance ID for InterPLMN metrics. |
ocscp_server_header | Server header received in case of failure received from side car. |
ocscp_threshold_level | The CPU threshold level. |
ocscp_upstream_service_time | The time taken to receive a response from producer NF. |
peer_info | The NF instance ID of the peer for which the load is reported. |
pod_name | The pod name for which metric is pegged. |
PrimaryEndPoint | Primary end point selected by SCP for routing before alternate routing. |
processingTimeInMs | Total time taken for notification processing in milliseconds. |
queueCapacity |
Notification Metrics: Maximum Notification queue size (runQueue:40, notificationQueue:5000, waitingQueue: 5000) Nrf Proxy Metrics: Maximum size is 10000. Load Manager Metrics: Maximum size is 10000. Cache Metrics: The maximum size of the queue is 30000 for scpCacheExecutorQueue and 10000 for others. Worker Metrics: Metrics: The maximum size is 10000. |
queueName |
Notification Queue Name (runQueue, notificationQueue, waitingQueue) NRF Proxy Metrics: Name of the nrf-proxy queue (scpDownstreamExecutorQueue, scpUpstreamExecutorQueue) Load Manager Metrics: Name of the queue (sutLciCohEvExecutorQueue, sutLciAppEvExecutorQueue, peerLciCohEvExecutorQueue, peerLciAppEvExecutorQueue, loadCohEvExecutorQueue, loadAppEvExecutorQueue) Cahce Metrics: Name of the queue (scpCacheExecutorQueue, accessTokenAppEvExecutorQueue, accessTokenCohEvExecutorQueue) Worker Metrics: Name of the queue (scpDownstreamExecutorQueue, scpUpstreamExecutorQueue, scpNrfProxyDownstreamExecutorQueue, scpClientExecutorQueue, scpUpdateSSLCertsQueue, scpMediationDownstreamExecutorQueue, scpReconfigureEgressRLExecutorQueue) |
reqType | The request type for the oauth tocket request (for example, ondemand or proactive). |
requester_nfType | The requester NF Type received the request for oauth token. |
requestType | The HTTP method of request received on configuration (for example, GET, PUT, or DELETE). |
responseCode | The HTTP status code in the response from SCP. |
responseCodeClass | The HTTP status code class in response to SCP (For
example, the response code is 2xx for success responses, 5xx, 4xx, or
3xx for error responses.)
The possible values are "OnDemand" and "Scheduled". |
sbi_message_priority | The value of the sbi_message_prirotiy header in the request received. |
scheme | The scheme received in the rx request or the scheme of the selected producer for the tx request. |
scp_local_coh_cluster_name | The SCP local coherence cluster name. |
scp_nf_instance_id | The NF instance ID of SCP. |
scp_remote_coh_cluster_fqdn | The remote SCP coherence cluster FQDN. |
scp_remote_coh_cluster_name | The remote SCP coherence cluster name. |
scp_remote_coh_cluster_nf_instance_id | The remote SCP coherence cluster NF instance ID. |
scp_remote_coh_cluster_port | The remote SCP coherence cluster port. |
scp_service | The SCP microservice name for which metric is pegged. |
service_proto_name | The service proto-name used for DNS SRV resolution. |
severity | The severity of the condition. |
source | The Microservice from which the request was originated. |
source (TLS) | Contains the source address details involved in HTTPS connection. |
status | The health check status code. |
status_code | The response status code. |
subscriber_info_present | If any of the following discovery headers are present in the request: 3gpp-sbi-discovery-supi, 3gpp-sbi-discovery-gpsi, 3gpp-sbi-discovery-external-group-identity, 3gpp-sbi-discovery-routing-indicator, 3gpp-sbi-discovery-msisdn, or 3gpp-sbi-discovery-imsi. |
subscriber_info_present_in_discovery_headers | If any of the following discovery headers are present in the request: 3gpp-sbi-discovery-supi, 3gpp-sbi-discovery-gpsi, 3gpp-sbi-discovery-external-group-identity, 3gpp-sbi-discovery-routing-indicator, 3gpp-sbi-discovery-msisdn, or 3gpp-sbi-discovery-ims. |
successRspType | The success response code received for the health check. |
tableName | The table name indicates which operation is performed. For example, SERVICE_ENTRIES. |
target_nfType | The NF type in oauth access token request. |
targetFqdn | The NF FQDN in an oauth access token request. |
taskId | The NRF DNS SRV migration task ID. |
taskName | The NRF DNS SRV migration task name. |
taskState | The NRF DNS SRV migration task state. |
timeInMs | The time taken in Notification queues. |
title | The error reason for Health check failure. |
triggerpoint | The mediation triggerpoint |
tls_version | Indicates the TLS version used to establish the HTTPS
connection.
Note: In some failure cases, the TLS version will not be available and will be displayed as "NA" . |
refresh_status | Indicates whether the invalidated cache record at the scp-worker is successfully refreshed. |
valid_NRF_response_to_fail | Whether SCP converts 200 OK (NRF) to 400 error due to an empty profile list. |
validation_type | The validation type for CCA. |
kafka_partition_id | Partition ID of the Kafka partition, which is selected for traffic feed messages For the partition selection strategy "RoundRobin," partitions are not known to the SCP application, thus the partition ID is used as "NA.". |
kafka_broker_id | The broker ID of the Kafka partition leader is selected for the traffic feed message. For the partition selection strategy "RoundRobin," broker IDs are not known to the SCP application, thus the broker ID is used as "NA.". |
ocscp_object_pool_name | The name of the object pool in the case of multiple object pool implementations. |
ocscp_worker_client_name | The name of the async client for identification of pool objects paraphrase. |
ocscp_object_trans_state | The transaction status of pool objects during the transaction timeout for pool objects. |
clash_type | The cause of clash for pool objects. |
ocscp_attempted_producers | This is a list of producer FQDNs or IPs attempted for a particular SBI message. |
ocscp_timeout_point | Indicates the location where the metric was recorded. |
ocscp_requester_nfType | Specifies the type of requester NF that was received in the request for the OAuth token. |
ocscp_target_nfType | Specifies the target NF type in the OAuth access token request. |
ocscp_validation_failure | Indicates the type of validation failure for the timestamp header. |
ocscp_mediation_udv_name | This dimension indicates the name of the user-defined mediation variable. |
ocscp_mediation_udv_max_usage_limit | The integer limit for the maximum per transaction usage of mediation user-defined variables. |
ocscp_nf_type_nf_service_type | The concatenated value of nftype and nfservice. |
alternate_route_cause | This dimension indicates the cause of alternate routing when SCP initiates alternate routing, such as ErrorReceived, Timeout, or ConnectionError. |
producer_nf_info |
This dimension provides information about the destination producer NF Type and the destination NF service name of the request message, separated by a hyphen. Format:<NF Type>-<NF Service
Name> Example: UDM-nudn-uecm The
value of the dimension follows the format
|
Note:
- The values for these dimensions, such as ocscp_consumer_host, ocscp_consumer_nf_instance_id, and ocscp_consumer_nf_type are available based on the availability of the User-Agent header in incoming message requests. SCP should be able to decode that particular format only if the User-Agent header is available in certain allowed configurable formats.
- In the notification message type, certain dimension values such as ocscp_nf_service_type, ocscp_nf_setid, and ocscp_nf_type may not qualify for pegging. In the scenario where the service name cannot be derived from the PATH URI, pegging will not take place, and if these dimensions are identified through headers, pegging will occur.
5.2.1 Metrics
Caution:
User, computer and applications, and character encoding settings may cause an issue when copy-pasting commands or any content from PDF. The PDF reader version also affects the copy-pasting functionality. It is recommended to verify the pasted content when the hyphens or any special characters are part of the copied content.Note:
- Please note that Kubernetes-based dimensions, such as pod name or namespace, require updates based on the Prometheus deployment.
- All the metrics with HTTP in their names are pegged for both HTTP and HTTPS traffic because Hypertext Transfer Protocol Secure (HTTPS) is the secured version of HTTP.
Table 5-3 ocscp_metric_http_rx_req_total
Field | Details |
---|---|
Description | The total number of incoming HTTP requests at the
scp-worker service.
The ocscp_nf_service_type dimension for notification is "n<nfType>-unknown or NA-unknown". Note: Peg this metric for both HTTP and HTTPS traffic because Hypertext Transfer Protocol Secure (HTTPS) is the secured version of HTTP. |
Type | Counter |
Dimension |
Non OCI Dimensions
OCI Dimensions
|
Example |
|
Table 5-4 ocscp_metric_http_tx_req_total
Field | Details |
---|---|
Description |
The total number of HTTP requests forwarded by SCP to the upstream cluster. Each SCP-worker pod will peg this metric. The ocscp_nf_service_type dimension for notification is "n<nfType>-unknown or NA-unknown". Note: The ocscp_authority dimension will get
pegged only when it is enabled using the
Note: Peg this metric for both HTTP and HTTPS traffic because Hypertext Transfer Protocol Secure (HTTPS) is the secured version of HTTP. |
Type | Counter |
Dimension | Non OCI Dimensions
OCI Dimensions
|
Example |
|
Table 5-5 ocscp_metric_http_rx_res_total
Field | Details |
---|---|
Description | Total number of HTTP responses received by SCP with
specific HTTP response codes (for example, 201, 503, and so on).
Each SCP-Worker pod will peg this metric. The ocscp_nf_service_type dimension for notification is "n<nfType>-unknown or NA-unknown". Note: Peg this metric for both HTTP and HTTPS traffic because Hypertext Transfer Protocol Secure (HTTPS) is the secured version of HTTP. |
Type | Counter |
Dimension |
Non OCI Dimensions
Note: These dimensions are available based on the availability of the User-Agent header in incoming message requests. SCP should be able to decode that particular format only if the User-Agent header is available in certain allowed configurable formats. OCI Dimensions
|
Example |
|
Table 5-6 ocscp_metric_http_tx_res_total
Field | Details |
---|---|
Description | Total number of HTTP responses forwarded by SCP
back to the consumer or request originator with specific HTTP
response codes (For example, 201, 503, and so on)
Each SCP-worker pod will peg this metric when sending the response back to the consumer. The ocscp_nf_service_type dimension for notification is "n<nfType>-unknown or NA-unknown". Note: The
ocscp_authority dimension will get pegged only when it is
enabled using the Note: Peg this metric for both HTTP and HTTPS traffic because Hypertext Transfer Protocol Secure (HTTPS) is the secured version of HTTP. |
Type | Counter |
Dimension |
Non OCI Dimensions
Note: The ocscp_consumer_host dimension for the metric can have an "OCSCP-INITIATED-MSG" value if the request is an SCP self-generated request. OCI Dimensions
|
Example |
|
Table 5-7 ocscp_metric_attempts_to_forward_route_total
Field | Details |
---|---|
Description | Total number of requests that matched the catch-all-route routing rule. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-8 ocscp_metric_routing_attempt_fail_total
Field | Details |
---|---|
Description | Total number of request that SCP failed to route due to any reason. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-9 ocscp_metric_request_processing_time_total
Field | Details |
---|---|
Description | This metric captures the processing time by SCP for ingress requests into the time buckets, for example, 1ms, 2ms, 4ms, 8ms and so on. |
Type | Histogram |
Dimension |
|
Example |
|
Table 5-10 ocscp_metric_response_processing_time_total
Field | Details |
---|---|
Description | This metric captures the processing time by SCP for ingress responses into the time buckets (for example, 1ms, 2ms, 4ms, 8ms and so on). |
Type | Histogram |
Dimension |
|
Example |
|
Table 5-11 ocscp_metric_request_per_try_timeout_total
Field | Details |
---|---|
Description | This metric captures the number of incoming request whose per try timeout expired. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-12 ocscp_metric_transaction_timeout_total
Field | Details |
---|---|
Description | This metric captures the total number of request whose transaction timed out. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-13 ocscp_metric_max_routing_attempts_exhausted_total
Field | Details |
---|---|
Description | This metric captures the total number of requests whose maximum routing attempts expired during alternate routing. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-14 ocscp_notifications_rejected_topologysource_local _total
Field | Details |
---|---|
Description |
Number of NF notification messages rejected because "learning from NRF" was configured as "not allowed". Metrics Pegging Condition: This metrics will be pegged whenever notification is received for NF configured as LOCAL. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-15 ocscp_topologysource_toggle_nrf_to_local_total
Field | Details |
---|---|
Description | Number of times topology source changed from "NRF" to "Local" for given NF. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-16 ocscp_topologysource_toggle_local_to_nrf_total
Field | Details |
---|---|
Description | Number of times topology source changed from "Local" to "NRF" for given NF. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-17 ocscp_db_operation_failure_total
Field | Details |
---|---|
Description | Number of times audit failed due to database failure. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-18 ocscp_notification_nf_profile_processing_failure_total
Field | Details |
---|---|
Description | Number of times notification process failure. |
Type | Counter |
Dimension |
|
Example |
ocscp_notification_nf_profile_processing_failure_total{nfType ="UDM",nfinstanceid="6faf3abc-6e4a-4454-a507-a14ef8e1bc4b",ocscp_fqdn="ocscp-scp-worker.scpsvc.svc.cluster.local"} |
Table 5-19 ocscp_patch_subscription_nf_success_total
Field | Details |
---|---|
Description | Number of successful patch operation of subscription based on nfType and nrfRegionOrSetId. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-20 ocscp_patch_subscription_nf_failure_total
Field | Details |
---|---|
Description | Number of failure patch operation of subscription based on nfType and nrfRegionOrSetId. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-21 ocscp_unsubscription_nf_success_total
Field | Details |
---|---|
Description | Number of successful operations of unsubscription based on nfType and nrfRegionOrSetId. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-22 ocscp_unsubscription_nf_failure_total
Field | Details |
---|---|
Description | Number of failure operations of unsubscription based on nfType and nrfRegionOrSetId. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-23 ocscp_subscription_nf_success_total
Field | Details |
---|---|
Description | Number of successful operations of subscription based on nftype and nrfRegionOrSetId. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-24 ocscp_subscription_nf_failure_total
Field | Details |
---|---|
Description | Number of failure operations of subscription based on nfType and nrfRegionOrSetId. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-25 ocscp_audit_2xx_empty_nf_array
Field | Details |
---|---|
Description | The state of metrics is 1 when SCP audit receives empty NF array response for nfType. Then, state of metrics is changes to 0 when audit receives non empty NF array. |
Type | Gauge |
Dimension |
|
Example |
ocscp_audit_2xx_empty_nf_array_rx_total{nrfRegionOrSetId="Reg2"} ocscp_audit_2xx_empty_nf_array_rx_total(nfType="UDM"} ocscp_audit_2xx_empty_nf_array_rx_total{scpFqdn="ocscp-scp-worker.scpsvc.svc.cluster.local"} |
Table 5-26 ocscp_audit_error_response
Field | Details |
---|---|
Description |
The state of metrics is 1 when SCP audit receives error response for nfType. Then, state of metrics is changed to 0 when audit receives non error response for nfType. |
Type | Gauge |
Dimension |
|
Example | ocscp_audit_error_response{ocscp_fqdn="ocscp-scp-worker.scpsvc.svc.cluster.local"} |
Table 5-27 ocscp_subscription_nrf_registration_success_total
Field | Details |
---|---|
Description | This metrics pegs the number of times registration successful for a particular nrfRegionOrSetId. |
Type | Counter |
Dimension | nrfRegionOrSetId
For example: (Reg11,Reg1,set1.nrfset.5gc.mnc014.mcc310) ocscp_fqdn |
Example |
|
Table 5-28 ocscp_subscription_nrf_registration_failure_total
Field | Details |
---|---|
Description | This metrics pegs the number of times registration failed for a particular nrfRegionOrSetId. |
Type | Counter |
Dimension | nrfRegionOrSetId
For example: (Reg11,Reg1,set1.nrfset.5gc.mnc014.mcc310) ocscp_fqdn |
Example |
|
Table 5-29 ocscp_subscription_nrf_heartbeat_success_total
Field | Details |
---|---|
Description | This metrics pegs the number of times heartbeat successful for a particular nrfRegionOrSetId. |
Type | Counter |
Dimension | nrfRegionOrSetId
For example: (Reg11,Reg1,set1.nrfset.5gc.mnc014.mcc310) ocscp_fqdn |
Example |
|
Table 5-30 ocscp_subscription_nrf_heartbeat_failures_total
Field | Details |
---|---|
Description | This metrics pegs the number of times heartbeat failed for a particular nrfRegionOrSetId. |
Type | Counter |
Dimension | nrfRegionOrSetId
For example: (Reg11,Reg1,set1.nrfset.5gc.mnc014.mcc310) ocscp_fqdn |
Example |
|
Table 5-31 ocscp_metric_upstream_service_time_total
Field | Details |
---|---|
Description | This metric captures the time taken by upstream host is responding the request in time buckets, for example, 1ms, 2ms, 4ms, 8ms, and so on. |
Type | Histogram |
Dimension |
|
Example |
|
Table 5-32 ocscp_metric_scp_generated_response_total
Field | Details |
---|---|
Description | Captures the error response generated by SCP. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-33 ocscp_notification_failure_type_total
Field | Details |
---|---|
Description | Number of Notification failed to process. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-34 ocscp_nrf_notifications_requests_nf_total
Field | Details |
---|---|
Description | Indicates the number of notification messages specific to NFs per NF Type from NRF. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-35 ocscp_notification_nf_profile_processing_success_total
Field | Details |
---|---|
Description | Indicates the number of processed notifications that include the notifications from NRF, AUDIT, and Reconfiguration. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-36 ocscp_config_tsi_change_ondemand_audit_invoke_success_total
Field | Details |
---|---|
Description | Number of successful On-Demand Audit invocations when TSI is changed. |
Type | Counter |
Dimension | nrfRegionOrSetId
For example: (Reg11,Reg1,Reg2) ocscp_fqdn |
Example |
|
Table 5-37 ocscp_config_tsi_change_ondemand_audit_invoke_failure_total
Field | Details |
---|---|
Description | Number of failed On-Demand Audit invocations when TSI is changed. |
Type | Counter |
Dimension | nrfRegionOrSetId
For example: (Reg11,Reg1,Reg2) ocscp_fqdn |
Example |
|
Table 5-38 ocscp_duplicate_audit_profile_total
Field | Details |
---|---|
Description | Number of duplicate profiles added by audit due to notification slowness |
Type | Counter |
Dimension |
nfType (for example: UDM, AMF) nfInstanceId (for example: 4947a69a-f61b-4bc1-b9da-47c9c5d14b64) ocscp_fqdn |
Example |
|
Table 5-39 ocscp_notification_foreign_nf_locality_absent
Field | Details |
---|---|
Description | Sets to 1 if a foreign NF is registered from an unknown locality that is locality is not present in the foreign NF |
Type | Gauge |
Dimension |
locality (for example: UNKNOWN_LOCALITY) nfInstanceId (for example: 1faf1bbc-6e4a-4454-a507-a14ef8e1bb6a) nftype (for example: UDM, AMF) nrfregionorsetid (for example: Reg1,Reg2) ocscp_fqdn |
Example |
|
Table 5-40 ocscp_notification_foreign_nf_locality_unserved
Field | Details |
---|---|
Description | Sets to 1 if a foreign NF is registered and its locality is not served by any SCP |
Type | Gauge |
Dimension |
locality (for example: Loc80) nfInstanceId (for example: 1faf1bbc-6e4a-4454-a507-a14ef8e1bb6a) nftype (for example: UDM, AMF) nrfregionorsetid (for example: Reg1, Reg2) ocscp_fqdn |
Example |
|
Table 5-41 ocscp_notification_duplicate_foreign_location
Field | Details |
---|---|
Description | Sets to 1 if Locality of foreign NF(mate/serving locality in case of foreign SCP) is same as one of locality present in the local SCP. |
Type | Gauge |
Dimension |
locality (for example: Loc83) nfInstanceId (for example: 1faf1bbc-6e4a-4454-a507-a14ef8e1bb6a) nftype (for example: UDM, AMF) nrfregionorsetid (for example: Reg1, Reg2) ocscp_fqdn |
Example |
|
Table 5-42 ocscp_interscp_downstream_rq_total
Field | Details |
---|---|
Description | Keeps track of ingress message received from another SCP |
Type | Counter |
Dimension |
ocscp_fqdn (for example: site2-ocscp-scp-worker.scpsvc.svc.cluster.local") ocscp_nf_service_type (for example:"nudm-uecm") ocscp_nf_type (for example:"UDM") ocscp_fqdn |
Example |
|
Table 5-43 ocscp_metric_rule_engine_processing_time_total
Field | Details |
---|---|
Description | Captures the processing time by SCP for rule engine |
Type | Counter |
Dimension |
|
Example |
ocscp_metric_rule_engine_processing_time_total{ocscp_locality="Loc7"} ocscp_metric_rule_engine_processing_time_total{ocscp_nf_service_type=" nudm-uecm"} ocscp_metric_rule_engine_processing_time_total{ ocscp_nf_type="UDM"} ocscp_metric_rule_engine_processing_time_total{ocscp_processing_time="29"} |
Table 5-44 ocscp_metric_upstream_response_timeout_total
Field | Details |
---|---|
Description | Contains information of timeout for every attempt made by producer to get a response. |
Type | Counter |
Dimension |
|
Example |
ocscp_metric_upstream_response_timeout_total{ ocscp_nf_type="UDM"} ocscp_metric_upstream_response_timeout_total{ocscp_locality="Loc7"} ocscp_metric_upstream_response_timeout_total{ocscp_nf_service_type=" nudm-uecm"} ocscp_metric_upstream_response_timeout_total{ocscp_processing_time="29"} ocscp_metric_upstream_response_timeout_total{ocscp_response_code="504 GATEWAY_TIMEOUT"} ocscp_metric_upstream_response_timeout_total{ocscp_producer_host="udm1svc.default.svc.cluster.local"} ocscp_metric_upstream_response_timeout_total{ocscp_nf_setid="set1.udmset.5gc.mnc012.mcc345"} |
Table 5-45 ocscp_metric_http_streaminfo_create_total
Field | Details |
---|---|
Description | Captures information of application, microservice, fqdn
and vendor whenever StreamInfo Object is initialized.
Note: Peg this metric for both HTTP and HTTPS traffic because Hypertext Transfer Protocol Secure (HTTPS) is the secured version of HTTP. |
Type | Counter |
Dimension |
|
Example |
ocscp_metric_http_streaminfo_create_total{ocscp_fqdn="ocscp-scp-worker.scpsvc.svc.cluster.local"} |
Table 5-46 ocscp_metric_http_streaminfo_delete_total
Field | Details |
---|---|
Description | Captures information of application, microservice, fqdn
and vendor just before StreamInfo Object is destroyed before the garbage
collection.
Note: Peg this metric for both HTTP and HTTPS traffic because Hypertext Transfer Protocol Secure (HTTPS) is the secured version of HTTP. |
Type | Counter |
Dimension |
|
Example |
ocscp_metric_http_streaminfo_delete_total{ocscp_fqdn="ocscp-scp-worker.scpsvc.svc.cluster.local"} |
Table 5-47 ocscp_upstream_rq_pending_overflow_total
Field | Details |
---|---|
Description | Captures total number of requests for which circuit has been broken due to http2MaxLimit reached for outstanding requests. |
Type | Counter |
Dimension |
|
Example |
ocscp_upstream_rq_pending_overflow_total{ ocscp_nf_type="UDM"} ocscp_upstream_rq_pending_overflow_total{ocscp_nf_service_type=" nudm-uecm"} ocscp_upstream_rq_pending_overflow_total{ocscp_locality="Loc7"} ocscp_upstream_rq_pending_overflow_total{ocscp_producer_host="udm1svc.default.svc.cluster.local"} ocscp_upstream_rq_pending_overflow_total{ocscp_producer_nf_instance_id="6faf1bbc-6e4a-4454-a507-a14ef8e1bc5c"} ocscp_upstream_rq_pending_overflow_total{ocscp_producer_service_instance_id="fe137ab7-740a-46ee-aa5c-951806d77b02"} ocscp_upstream_rq_pending_overflow_total{ocscp_fqdn="ocscp-scp-worker.scpsvc.svc.cluster.local"} |
Table 5-48 ocscp_circuit_breaking_applied
Field | Details |
---|---|
Description | Indicates the circuit breaking state. If outstanding request limit has been reached then gauge will show 1 otherwise 0. |
Type | Gauge |
Dimension |
|
Example |
ocscp_circuit_breaking_applied{ ocscp_nf_type="UDM"} ocscp_circuit_breaking_applied{ocscp_nf_service_type=" nudm-uecm"} ocscp_circuit_breaking_applied{ocscp_locality="Loc7"} ocscp_circuit_breaking_applied{ocscp_producer_host="udm1svc.default.svc.cluster.local"} ocscp_circuit_breaking_applied{ocscp_producer_nf_instance_id="6faf1bbc-6e4a-4454-a507-a14ef8e1bc5c"} ocscp_circuit_breaking_applied{ocscp_fqdn="ocscp-scp-worker.scpsvc.svc.cluster.local"} |
Table 5-49 ocscp_configuration_tx_res_total
Field | Details |
---|---|
Description | Indicates the number of times the configuration microservice receives request from users. |
Type | Counter |
Dimension |
|
Example |
ocscp_configuration_tx_res_total{configurationName="Systemoptions"} ocscp_configuration_tx_res_total{requestType="PUT"} ocscp_configuration_tx_res_total{responseCode="200"} ocscp_configuration_tx_res_total{ocscp_fqdn="ocscp-scp-worker.scpsvc.svc.cluster.local"} |
Table 5-50 ocscp_rx_configuration_total
Field | Details |
---|---|
Description | Indicates the number of times the configuration microservice responds to users either with a successful or failure response. |
Type | Counter |
Dimension |
|
Example |
ocscp_rx_configuration_total{configurationName="SystemOptions"} ocscp_rx_configuration_total{requestType="PUT"} ocscp_rx_configuration_total{ocscp_fqdn="ocscp-scp-worker.scpsvc.svc.cluster.local"} |
Table 5-51 ocscp_notification_all_routing_rules_deleted_total
Field | Details |
---|---|
Description | Indicates no of times all routing rules are deleted. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-52 ocscp_no_nf_instance
Field | Details |
---|---|
Description | Indicates the state of number of instances for NFType. |
Type | Gauge |
Dimension |
|
Example |
|
Table 5-53 ocscp_metric_egress_rate_limiting_not_applied_req_total
Field | Details |
---|---|
Description | Number of requests routed without egress rate limiting treatment. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-54 ocscp_metric_egress_rate_limiting_alternate_routed_req_total
Field | Details |
---|---|
Description | Number of requests alternate routed because of egress rate limiting. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-55 ocscp_metric_egress_rate_limiting_throttle_req_total
Field | Details |
---|---|
Description | Number of requests throttled due to egress rate limiting |
Type | Counter |
Dimension |
|
Example |
|
Table 5-56 ocscp_metric_ingress_rate_limiting_not_applied_req_total
Field | Details |
---|---|
Description | Number of requests routed without ingress rate limiting treatment |
Type | Counter |
Dimension |
|
Example |
|
Table 5-57 ocscp_metric_ingress_rate_limiting_throttle_req_total
Field | Details |
---|---|
Description | Number of requests throttled due to ingress rate limiting |
Type | Counter |
Dimension |
|
Example |
|
Table 5-58 ocscp_notification_received_different_nrfregionorsetid_total
Field | Details |
---|---|
Description | Number of duplicate notifications skipped with the nrfRegionOrSetId update |
Type | Counter |
Dimension |
|
Example |
ocscp_notification_received_different_nrfregionorsetid_total{nfType="UDM"} ocscp_notification_received_different_nrfregionorsetid_total{nfInstanceId="6faf1bbc-6e4a-4454-a507-a14ef8e1bc5c"} ocscp_notification_received_different_nrfregionorsetid_total{nrfRegionOrSetId="Reg1"} ocscp_notification_received_different_nrfregionorsetid_total{ocscp_fqdn="ocscp-scp-worker.scpsvc.svc.cluster.local"} |
Table 5-59 ocscp_audit_2xx_empty_nf_array_rx_total
Field | Details |
---|---|
Description | Number of 2xx responses with empty body |
Type | Counter |
Dimension |
|
Example |
ocscp_audit_2xx_empty_nf_array_rx_total{nrfRegionOrSetId="Reg2"} ocscp_audit_2xx_empty_nf_array_rx_total(nfType="UDM"} ocscp_audit_2xx_empty_nf_array_rx_total{ocscp_fqdn="ocscp-scp-worker.scpsvc.svc.cluster.local"} |
Table 5-60 ocscp_audit_nrf_failure_response_rx_total
Field | Details |
---|---|
Description | Number of failed responses received from NRF for SCP audit |
Type | Counter |
Dimension |
|
Example |
ocscp_audit_nrf_failure_response_rx_total{nrfRegionOrSetId="Reg1"} ocscp_audit_nrf_failure_response_rx_total{nfType="AUSF"} ocscp_audit_nrf_failure_response_rx_total{ocscp_fqdn="ocscp-scp-worker.scpsvc.svc.cluster.local"} |
Table 5-61 ocscp_notification_request_total
Field | Details |
---|---|
Description | Pegs the number of notifications received on the notification module, which includes notifications from sources NRF, AUDIT, and RECONFIGURATION, except for the NF profile notification with invalid JSON. |
Type | Counter |
Dimension |
|
Example |
ocscp_notification_request_total {eventType="NF_REGISTERED"} ocscp_notification_request_total {nfStatus="REGISTERED"} ocscp_notification_request_total {nfType="UDM"} ocscp_notification_request_total {nfInstanceId="6faf1bbc-6e4a-4454-a507-a14ef8e1bc5c"} ocscp_notification_request_total {notificationSource="NRF"} ocscp_notification_request_total {nrfRegionOrSetId="Reg1"} ocscp_notification_request_total{ocscp_fqdn="ocscp-scp-worker.scpsvc.svc.cluster.local"} |
Table 5-62 ocscp_audit_tx_req_total
Field | Details |
---|---|
Description | This metric pegs the number of times audit requests are initiated for particular NFType, nrfRegionOrSetId, and nrfHost by the scpc-Audit service. This metric is pegged for the scheduled Audit cycle. |
Type | Counter |
Dimension |
|
Example |
ocscp_audit_tx_req_total{auditType="onDemand"} ocscp_audit_tx_req_total{nrfHost="nrf.svc.cluster.local"} ocscp_audit_tx_req_total{nfType="AMF"} ocscp_audit_tx_req_total{auditMode="nnrf-disc"} ocscp_audit_tx_req_total{nrfRegionOrSetId="Reg1"} ocscp_audit_tx_req_total{ocscp_fqdn="ocscp-scp-worker.scpsvc.svc.cluster.local"} |
Table 5-63 ocscp_audit_rx_res_total
Field | Details |
---|---|
Description | This metric pegs the number of times a response has been received for an initiated audit request. This metric is pegged for the scheduled Audit cycle. |
Type | Counter |
Dimension |
|
Example |
ocscp_audit_rx_res_total{auditType="onDemand"} ocscp_audit_rx_res_total{nrfHost="nrf.svc.cluster.local"} ocscp_audit_rx_res_total{nfType="AMF"} ocscp_audit_rx_res_total{auditMode="nnrf-disc"} ocscp_audit_rx_res_total{nrfRegionOrSetId="Reg1"} ocscp_audit_rx_res_total{responseCodeClass="2xx"} ocscp_audit_rx_res_total{responseCode="201"} ocscp_audit_rx_res_total{ocscp_fqdn="ocscp-scp-worker.scpsvc.svc.cluster.local"} |
Table 5-64 ocscp_metric_interscp_http_tx_req_total
Field | Details |
---|---|
Description | Number of HTTP requests forwarded to the next hop SCP
Here, the dimension
The ocscp_nf_service_type dimension for notification is "n<nfType>-unknown or NA-unknown". Note: Peg this metric for both HTTP and HTTPS traffic because Hypertext Transfer Protocol Secure (HTTPS) is the secured version of HTTP. |
Type | Counter |
Dimension |
Non OCI Dimensions
Non OCI Dimensions
|
Example |
|
Table 5-65 ocscp_metric_interscp_http_rx_res_total
Field | Details |
---|---|
Description | Number of HTTP responses received from SCP with specific
HTTP response codes, for example, 201, 503, and so on.
Here, the dimension The ocscp_nf_service_type dimension for notification is "n<nfType>-unknown or NA-unknown". Note: Peg this metric for both HTTP and HTTPS traffic because Hypertext Transfer Protocol Secure (HTTPS) is the secured version of HTTP. |
Type | Counter |
Dimension |
Non OCI Dimensions
OCI Dimensions
|
Example |
|
Table 5-66 ocscp_metric_jetty_client_requests_total
Field | Details |
---|---|
Description | Number of HTTP requests sent to producer NFs by the Jetty client. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-67 ocscp_worker_pod_overload_discard_req_total
Field | Details |
---|---|
Description | Number of requests discarded with error responses through overload control treatment of SCP-worker service when CPU utilization or Pending Transactions exceeds threshold. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-68 ocscp_alternate_resolution_dnssrv_req_total
Field | Details |
---|---|
Description | Indicates the total number of requests sent to DNS SRV. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-69 ocscp_alternate_resolution_dnssrv_res_total
Field | Details |
---|---|
Description | Indicates the total number of DNS SRV queries received from the DNS server. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-70 ocscp_metric_http_ar_tx_req_total
Field | Details |
---|---|
Description | Indicates the total number of alternate route attempts
made by SCP.
Note: Here, the instanceid of SEPP is used for interplmn scenarios, the instanceid of SCP is used for inter-scp scenarios, otherwise, the instanceid of the producer is utilized. Note: Peg this metric for both HTTP and HTTPS traffic because Hypertext Transfer Protocol Secure (HTTPS) is the secured version of HTTP. |
Type | Counter |
Dimension |
Note: In the notification message type, certain dimension values such as ocscp_nf_service_type, ocscp_nf_setid, and ocscp_nf_type may not qualify for pegging. In the scenario where the service name cannot be derived from the PATH URI, pegging will not take place, and if these dimensions are identified through headers, pegging will occur. |
Example |
|
Table 5-71 ocscp_metric_sidecarproxy_failures_total
Field | Details |
---|---|
Description | Number of error responses received from service mesh sidecar proxy because of transport error towards producer NFs. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-72 ocscp_metric_remote_response_without_server_header_total
Field | Details |
---|---|
Description | Number of times SCP adds the server header in the error response received from producer NFs without server header. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-73 ocscp_metric_add_or_update_server_header_custom_behavior_total
Field | Details |
---|---|
Description | Number of times SCP adds or updates the server header in the error response received from producer NFs. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-74 ocscp_metric_add_or_update_server_header_custom_behavior_v2_total
Field | Details |
---|---|
Description | Number of times SCP adds or updates the server header for
the enhancement V2 behavior in the following scenarios:
|
Type | Counter |
Dimension |
|
Example |
|
Table 5-75 ocscp_metric_add_server_header_default_behavior_total
Field | Details |
---|---|
Description | Number of times SCP adds the server header in the error response received from producer NFs. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-76 ocscp_metric_failure_from_peer_scp_total
Field | Details |
---|---|
Description | Number of times SCP receives error responses with server header containing only the next hop FQDN of SCP. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-77 ocscp_peer_scp_unhealthy
Field | Details |
---|---|
Description | Number of times (as gauge) the peer SCP is marked as unavailable. |
Type | Gauge |
Dimension |
|
Example |
|
Table 5-78 ocscp_alternate_resolution_dnssrv_rx_error_res
Field | Details |
---|---|
Description | Indicates failed DNS SRV query responses. |
Type | Gauge |
Dimension |
|
Example |
|
Table 5-79 ocscp_load_manager_peer_load_throttled_threshold
Field | Details |
---|---|
Description | Indicates that the peer load has exceeded the Throttled threshold. This metric is pegged by the load manager pod. |
Type | Gauge |
Dimension |
|
Example |
ocscp_load_manager_peer_load_throttled_threshold{ocscp_peer_fqdn="smf1svc.scpsvc.svc.cluster.local",ocscp_peer_nf_instance_id="11111112-aaaa-aaaa-aaaa-111111111111",ocscp_peer_service_instance_id="3aad8c63-0cc0-4b74-9582-4e6475214ae8",ocscp_peer_service_name="nsmf-pdusession"} |
Table 5-80 ocscp_load_manager_peer_load_alternateRoute_threshold
Field | Details |
---|---|
Description | Indicates that the peer load has exceeded the Alternate Route state threshold. This metric is pegged by the load manager pod. |
Type | Gauge |
Dimension |
|
Example |
ocscp_load_manager_peer_load_alternateRoute_threshold{ocscp_peer_fqdn="smf1svc.scpsvc.svc.cluster.local",ocscp_peer_nf_instance_id="11111112-aaaa-aaaa-aaaa-111111111111",ocscp_peer_service_instance_id="3aad8c63-0cc0-4b74-9582-4e6475214ae8",ocscp_peer_service_name="nsmf-pdusession"} |
Table 5-81 ocscp_metric_ondemand_discovery_tx_req_total
Field | Details |
---|---|
Description | Number of times SCP worker sends on-demand discovery request to nrfproxy. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-82 ocscp_metric_ondemand_discovery_rx_res_total
Field | Details |
---|---|
Description | Number of times SCP worker receives on-demand discovery response from nrfproxy. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-83 ocscp_metric_ondemand_discovery_cache_match_total
Field | Details |
---|---|
Description | Number of times SCP worker is able to resolve discovery requests using local cache. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-84 ocscp_nrf_nf_discovery_tx_req_total
Field | Details |
---|---|
Description | The total number of discovery requests sent to NRF by nrfproxy. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-85 ocscp_nrf_nf_discovery_rx_res_total
Field | Details |
---|---|
Description | The total number of discovery responses received from NRF by nrfproxy. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-86 ocscp_nrf_nf_discovery_rx_req_total
Field | Details |
---|---|
Description | The total number of discovery requests received by nrfproxy from SCP worker. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-87 ocscp_nrf_nf_discovery_tx_res_total
Field | Details |
---|---|
Description | The total number of discovery responses sent by nrfproxy to SCP worker. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-88 ocscp_nrfproxy_generated_error_response_total
Field | Details |
---|---|
Description | The total number of error responses generated by nrfproxy excluding NRF returned errors. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-89 ocscp_metric_sepp_http_rx_req_total
Field | Details |
---|---|
Description | The total number of HTTP requests routed towards SEPP.
Note: Peg this metric for both HTTP and HTTPS traffic because Hypertext Transfer Protocol Secure (HTTPS) is the secured version of HTTP. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-90 ocscp_metric_sepp_http_rx_res_total
Field | Details |
---|---|
Description | The total number of HTTP responses received from
SEPP.
The ocscp_nf_service_type dimension for notification is "n<nfType>-unknown or NA-unknown". Note: Peg this metric for both HTTP and HTTPS traffic because Hypertext Transfer Protocol Secure (HTTPS) is the secured version of HTTP. |
Type | Counter |
Dimension |
Non OCI Dimensions
OCI Dimensions
|
Example |
|
Table 5-91 ocscp_metric_sepp_http_tx_res_total
Field | Details |
---|---|
Description | The total number of HTTP responses routed towards
SEPP.
Note: Peg this metric for both HTTP and HTTPS traffic because Hypertext Transfer Protocol Secure (HTTPS) is the secured version of HTTP. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-92 ocscp_metric_sepp_routing_attempt_fail_total
Field | Details |
---|---|
Description | The total number of inter-PLMN requests routing failed towards SEPP. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-93 ocscp_metric_sepp_routing_attempt_fail_current
Field | Details |
---|---|
Description | Set to 1 if inter-plmn requests routing failed towards SEPP. |
Type | Gauge |
Dimension |
|
Example |
|
Table 5-94 ocscp_metric_sepp_not_configured_total
Field | Details |
---|---|
Description | The total number of inter-PLMN requests failed because SEPP is not configured for target PLMN received in interPlmnFqdn from 3gpp-Sbi-Target-apiRoot HTTP header or interPlmnFqdn after discovery response. |
Type | Counter |
Dimension |
|
Example | ocscp_metric_sepp_not_configured_total{plmn_id= "mnc123-mcc254"} |
Table 5-95 ocscp_metric_sepp_not_configured_current
Field | Details |
---|---|
Description | Set to 1 if inter-plmn requests failed because SEPP is not configured for target PLMN received in interPlmnFqdn from 3gpp-Sbi-Target-apiRoot HTTP header or interPlmnFqdn after discovery response. |
Type | Gauge |
Dimension |
|
Example | ocscp_metric_sepp_not_configured_current{plmn_id= "mnc123-mcc254"} |
Table 5-96 ocscp_metric_5gsbi_rx_req_total
Field | Details |
---|---|
Description | The total number of incoming requests. This metric can be used to segregate the ingress requests based on scheme, such as HTTP or HTTPS. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-97 ocscp_metric_5gsbi_tx_req_total
Field | Details |
---|---|
Description |
The total number of requests forwarded by Service Communication Proxy to the upstream cluster. This metric can be used to segregate the egress requests based on the scheme, such as HTTP or HTTPS. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-98 ocscp_metric_5gsbi_tx_res_total
Field | Details |
---|---|
Description |
The total number of responses forwarded by SCP with specific HTTP response codes (for example, 201, 503, and so on). This metric can be used to segregate the egress responses based on a scheme, such as HTTP or HTTPS. Note:The ocscp_authority dimension will get
pegged only when it is enabled using the
|
Type | Counter |
Dimension |
|
Example |
|
Table 5-99 ocscp_metric_5gsbi_rx_res_total
Field | Details |
---|---|
Description |
The total number of responses received by SCP with specific HTTP response codes (for example, 201, 503, and so on.) This metric can be used to segregate the ingress responses based on a scheme, such as HTTP or HTTPS. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-100 ocscp_metric_ssl_certificate_expire_total
Field | Details |
---|---|
Description | The state of metric becomes 1 when the server or client certificate is about to expire. |
Type | Gauge |
Dimension |
|
Example | ocscp_metric_ssl_certificate_expire_total{ocscp_fqdn="ocscp-scp-worker.scpsvc.svc.cluster.local"} |
Table 5-101 ocscp_metric_scp_cache_service_unreachable_total
Field | Details |
---|---|
Description | Number of times SCP worker is unable to find SCP cache service. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-102 ocscp_missed_nf_notifications_total
Field | Details |
---|---|
Description | Number of times the notifications are missed. |
Type | Counter |
Dimension | nfType |
Example | ocscp_missed_nf_notifications_total{ocscp_nf_type="UDM"} |
Table 5-103 ocscp_notifications_rejected_topologysource_nrf_total
Field | Details |
---|---|
Description | Number of notifications rejected from NRF as topology source. |
Type | Counter |
Dimension | nfType |
Example | ocscp_notifications_rejected_topologysource_nrf_total{ocscp_nf_type="UDM"} |
Table 5-104 ocscp_soothsayer_audit_db_fetch
Field | Details |
---|---|
Description | Indicates the database fetched for audit. |
Type | Counter |
Dimension | ocscp_soothsayer_audit_db_fetch |
Example | ocscp_soothsayer_audit_db_fetch{ocscp_nf_type="UDM"} |
Table 5-105 ocscp_update_topology_source_failure_total
Field | Details |
---|---|
Description | Number of times the topology source information is toggled. |
Type | Counter |
Dimension | nfType |
Example | ocscp_update_topology_source_failure_total{ocscp_nf_type="UDM"} |
Table 5-106 ocscp_worker_pod_overload_control_cpu_utilization_warn
Field | Details |
---|---|
Description | Indicates CPU utilization of SCP worker at Warn level. |
Type | Gauge |
Dimension |
|
Example | ocscp_worker_pod_overload_control_cpu_utilization_warn{pod_name="ocscp-scp-worker-6fcc755f9b-5hckw",scp_service="scp-worker"} |
Table 5-107 ocscp_worker_pod_overload_control_cpu_utilization_minor
Field | Details |
---|---|
Description | Indicates CPU utilization of SCP worker at Minor level. |
Type | Gauge |
Dimension |
|
Example | ocscp_worker_pod_overload_control_cpu_utilization_minor{pod_name="ocscp-scp-worker-6fcc755f9b-5hckw",scp_service="scp-worker"} |
Table 5-108 ocscp_worker_pod_overload_control_cpu_utilization_major
Field | Details |
---|---|
Description | Indicates CPU utilization of SCP worker at Major level. |
Type | Gauge |
Dimension |
|
Example | ocscp_worker_pod_overload_control_cpu_utilization_major{pod_name="ocscp-scp-worker-6fcc755f9b-5hckw",scp_service="scp-worker"} |
Table 5-109 ocscp_notifications_suspended_topologysource_nrf_total
Field | Details |
---|---|
Description | Indicates the number of times SUSPEND notifications are received by SCP. |
Type | Counter |
Dimension |
|
Example | ocscp_notifications_suspended_topologysource_nrf_total{status="suspended"} |
Table 5-110 ocscp_notifications_profile_deleted_deregistration_total
Field | Details |
---|---|
Description | Indicates the number of times NF profile is removed due to DEREGISTER ED notification. |
Type | Counter |
Dimension |
|
Example | ocscp_notifications_profile_deleted_deregistration_total{event=" deregistered"} |
Table 5-111 ocscp_metric_ar_attempt_fail_total
Field | Details |
---|---|
Description | Indicates the total number of failed alternate routing attempts made using static configuration. |
Type | Counter |
Dimension |
|
Example | ocscp_metric_ar_attempt_fail_total{ocscp_alternate_route_type="STATIC_CONFIG"} |
Table 5-112 ocscp_nrf_nf_discovery_request_processing_time_total
Field | Details |
---|---|
Description | Indicates the NRF request processing time by the scp-nrfproxy microservice. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-113 ocscp_nrf_nf_discovery_response_processing_time_total
Field | Details |
---|---|
Description | Indicates the NRF response processing time by the scp-nrfproxy microservice. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-114 ocscp_global_egress_rl_bucketkey_not_rate_controlled_total
Field | Details |
---|---|
Description | Indicates when the local SCP is not performing global rate control while other SCP instances in the scp-cache cluster are performing the rate control. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-115 ocscp_global_egress_rl_remote_participant_connectivity_failure
Field | Details |
---|---|
Description | Monitors the remote coherence participant connectivity status. |
Type | Gauge |
Dimension |
|
Example | ocscp_global_egress_rl_remote_participant_connectivity_failure{applicationName="ocscp",microservice="scp-cache",ocscp_fqdn="ocscp-scp-worker.scpsvc.svc.cluster.local",scp_local_coh_cluster_name="scp-coherence-cluster",scp_remote_coh_cluster_fqdn="ocscp-scp-cache.fedsvc.svc.cluster.local",scp_remote_coh_cluster_name="scp-coherence-cluster-fedsvc",scp_remote_coh_cluster_port="30001",ocscp_fqdn="ocscp-scp-worker.scpsvc.svc.cluster.local",scp_remote_coh_cluster_nf_instance_id="2faf1bbc-6e4a-4454-a507-a14ef8e1bc22"} |
Table 5-116 ocscp_mediation_http_tx_total
Field | Details |
---|---|
Description | Indicates that the request is forwarded to Mediation.
Note: Peg this metric for both HTTP and HTTPS traffic because Hypertext Transfer Protocol Secure (HTTPS) is the secured version of HTTP. |
Type | Counter |
Dimension |
|
Example | ocscp_mediation_http_tx_total(ocscp_mediation_filtername="PCFsmpolicy",ocscp_mediation_triggerpoint="requestIngress") |
Table 5-117 ocscp_mediation_http_rx_total
Field | Details |
---|---|
Description | Indicates that the response is received by SCP from
Mediation when Mediation is invoked from the request trigger point and
producer NF when Mediation is triggered from the response trigger
points.
Note: Peg this metric for both HTTP and HTTPS traffic because Hypertext Transfer Protocol Secure (HTTPS) is the secured version of HTTP. |
Type | Counter |
Dimension |
|
Example | ocscp_mediation_http_rx_total(ocscp_mediation_filtername="PCFsmpolicy",ocscp_mediation_triggerpoint="requestIngress") |
Table 5-118 ocscp_mediation_upstream_service_time_ms
Field | Details |
---|---|
Description | Indicates the time taken for Mediation processing. |
Type | Counter |
Dimension |
|
Example | ocscp_mediation_upstream_service_time_ms_total{applicationName="ocscp", microservice="scp-worker",ocscp_med_upstream_service_time="128ms",ocscp_mediation_triggerpoint="requestEgress", ocscp_nf_service_type="nsmf-pdusession",ocscp_nf_type="SMF", ocscp_fqdn="ocscp-scp-worker.scpsvc.svc.cluster.local",vendor="Oracle"} |
Table 5-119 ocscp_mediation_http_not_reachable
Field | Details |
---|---|
Description | Indicates that the request to Mediation has failed or connection is not established. |
Type | Gauge |
Dimension |
|
Example | ocscp_mediation_http_not_reachable{applicationName="ocscp",microservice="scp-worker", ocscp_mediation_triggerpoint="requestIngress",ocscp_nf_service_type="npcf-smpolicycontrol",ocscp_nf_type="PCF", ocscp_response_code="503",ocscp_fqdn="ocscp-scp-worker.scpsvc.svc.cluster.local",vendor="Oracle",} |
Table 5-120 ocscp_notification_queue_utilization
Field | Details |
---|---|
Description | Indicates Notification queue utilization. |
Type | Gauge |
Dimension |
|
Example |
|
Table 5-121 ocscp_notification_queue_alert
Field | Details |
---|---|
Description | Indicates Notification queue alert. |
Type | Gauge |
Dimension |
|
Example |
|
Table 5-122 ocscp_nrfproxy_queue_utilization
Field | Details |
---|---|
Description | Indicates NrfProxy queue utilization. |
Type | Gauge |
Dimension |
|
Example |
|
Table 5-123 ocscp_nrfproxy_queue_alert
Field | Details |
---|---|
Description | Indicates NrfProxy queue alert
Metrics Pegging Condition: This metric value will either be 0 or 1. Based on the severity value, it will be 1 for hgh severity, and correspondingly, for other severity values, it will be 0. |
Type | Gauge |
Dimension |
|
Example |
|
Table 5-124 ocscp_worker_queue_utilization
Field | Details |
---|---|
Description | Indicates Worker queue utilization. |
Type | Guage |
Dimension |
|
Example |
Below example will return worker queue utilization
metric for scpClientExecutorQueue:
Below example will returns all worker queues utilization
metric with queueCapacity:
Below example will return all worker queue utilization
metrics with utilization greater than 0:
|
Table 5-125 ocscp_worker_queue_alert
Field | Details |
---|---|
Description | Indicates Worker queue alert. |
Type | Gauge |
Dimension |
|
Example |
|
Table 5-126 ocscp_metric_nf_lci_rx_total
Field | Details |
---|---|
Description | Indicates the number of messages received with NF's LCI
header.
Here, "ocscp_peer_nf_instance_id" denotes the instance ID of the producer from which it has received the LCI header. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-127 ocscp_metric_nf_lci_tx_total
Field | Details |
---|---|
Description | Indicates the number of messages forwarded with NF's LCI
header.
Here, "ocscp_peer_nf_instance_id" denotes the instance ID of the NF where it is sending LCI. When sending a request to the producer, it represents the producer instance ID, while when sending a response to the consumer, it represents the consumer instance ID |
Type | Counter |
Dimension |
|
Example |
|
Table 5-128 ocscp_metric_scp_lci_tx_total
Field | Details |
---|---|
Description | Indicates the number of messages forwarded with SCP's
LCI header.
Here, "ocscp_peer_nf_instance_id" denotes the instance ID of the producer to which SCP sends this request with LCI header. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-129 ocscp_metric_nf_lci_cache_update_total
Field | Details |
---|---|
Description | Indicates the number of cache updates done by peer load change. |
Type | Counter |
Dimension | ocscp_fqdn |
Example | ocscp_metric_nf_lci_cache_update_total{ocscp_fqdn= "ocscp-scp-worker.scpsvc.svc.cluster.local"} |
Table 5-130 ocscp_scp_load
Field | Details |
---|---|
Description | Metric to record SCP load value. |
Type | Gauge |
Dimension |
|
Example |
|
Table 5-131 ocscp_nf_load
Field | Details |
---|---|
Description | Records the peer NF load value. |
Type | Gauge |
Dimension |
|
Example |
|
Table 5-132 ocscp_modeld_cache_key_size
Field | Details |
---|---|
Description | Metric to indicate modelD cache Key size in worker and nrfproxy. |
Type | Gauge |
Dimension |
|
Example |
|
Table 5-133 ocscp_cache_egress_grl_local_worker_token_consumption_total
Field | Details |
---|---|
Description | The local SCP worker token consumption in global egress rate limit. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-134 ocscp_cache_egress_grl_remote_worker_token_consumption_total
Field | Details |
---|---|
Description | The remote SCP worker token consumption in global egress rate limit. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-135 ocscp_cache_egress_grl_local_worker_msg_consumption_percentage_total
Field | Details |
---|---|
Description | The local SCP worker token consume percentage in global egress rate limit. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-136 ocscp_cache_egress_grl_controller_token_consumption_total
Field | Details |
---|---|
Description | The number of tokens consumed by the global rate controller to adjust token availability for cache services. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-137 ocscp_metric_svc_unreachable
Field | Details |
---|---|
Description | This metric is pegged whenever there is a communication failure between microservices. Once the communication between the source and the destination is reestablished, this metric is cleared. |
Type | Gauge |
Dimension |
Possible list of values:
|
Example |
|
Table 5-138 ocscp_metric_nf_unhealthy_total
Field | Details |
---|---|
Description | Number of times a producer NF is marked unhealthy. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-139 ocscp_metric_req_nf_unhealthy_total
Field | Details |
---|---|
Description | Number of message requests not routed to the selected producer NF because it is marked unhealthy. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-140 ocscp_metric_req_peer_scp_unhealthy_total
Field | Details |
---|---|
Description | Number of message requests not routed to the selected peer SCP because it is marked unhealthy. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-141 ocscp_metric_sepp_unhealthy_total
Field | Details |
---|---|
Description | Number of times SEPP is marked unhealthy. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-142 ocscp_metric_req_sepp_unhealthy_total
Field | Details |
---|---|
Description | Number of message requests not routed to the selected SEPP because SEPP is marked unhealthy. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-143 ocscp_metric_nf_set_unhealthy
Field | Details |
---|---|
Description | Indicates whether all the producer NFs in the NF SET are unhealthy. |
Type | Gauge |
Dimension | ocscp_nf_setid |
Example | ocscp_metric_nf_set_unhealthy{ocscp_nf_setid="123-445-363"} |
Table 5-144 ocscp_sepp_unhealthy
Field | Details |
---|---|
Description | Indicate whether all the SEPP instances are unhealthy. |
Type | Gauge |
Dimension |
|
Example |
|
Table 5-145 ocscp_metric_trafficfeed_not_attempted_total
Field | Details |
---|---|
Description | Number of messages selected for traffic feed based on the trigger point configuration filter criteria but not attempted to send because of some condition. |
Type | Counter |
Dimension |
|
Example | ocscp_metric_trafficfeed_not_attempted_total{ocscp_nf_type="UDM",ocscp_cause="Incorrect Data Director Information",ocscp_nf_service_type="nudm-uecm",ocscp_trafficfeed_triggerpoint="requestEgress",kafka_partition_id="NA",kafka_broker_id="NA"} |
Table 5-146 ocscp_metric_trafficfeed_failed_total
Field | Details |
---|---|
Description | Number of messages failed to send to traffic feed. |
Type | Counter |
Dimension |
|
Example | ocscp_metric_trafficfeed_failed_total{ocscp_cause="Incorrect Data Director Information",ocscp_nf_service_type="nudm-uecm",ocscp_trafficfeed_triggerpoint="requestEgress"} |
Table 5-147 ocscp_metric_trafficfeed_attempted_total
Field | Details |
---|---|
Description | Number of messages sent to traffic feed. |
Type | Counter |
Dimension |
|
Example | ocscp_metric_trafficfeed_total{ocscp_nf_service_type="nausf-auth",ocscp_trafficfeed_triggerpoint="requestEgress"} |
Table 5-148 ocscp_worker_fqdn_resolution_total
Field | Details |
---|---|
Description | Number of messages for which fqdn is resolved by DNS or from nfProfile. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-149 ocscp_worker_interplmn_fqdn_resolution_total
Field | Details |
---|---|
Description | Number of messages for which inter-plmn fqdn is resolved by DNS or from nfProfile. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-150 ocscp_worker_http_req_host_type_total
Field | Details |
---|---|
Description | Number of messages with http host as IP or FQDN.
Note: When a message request is implicit or of default notification type, the value of the ocscp_worker_http_req_host_type_total metric is updated based on the host of the message request, with value IP or FQDN that is independent of the configuration of the Egress Host Preference feature. Note: Peg this metric for both HTTP and HTTPS traffic because Hypertext Transfer Protocol Secure (HTTPS) is the secured version of HTTP. |
Type | Counter |
Dimension |
Note: These dimensions are available based on the availability of the User-Agent header in incoming message requests. SCP should be able to decode that particular format only if the User-Agent header is available in certain allowed configurable formats. |
Example |
|
Table 5-151 ocscp_worker_cpu_pod_overload_control_status
Field | Details |
---|---|
Description | Indicates CPU utilization of SCP worker at any level. |
Type | Gauge |
Dimension |
|
Example |
|
Table 5-152 ocscp_worker_pod_overload_control_pendingTrans_utilization_minor
Field | Details |
---|---|
Description | Indicates pending transaction utilization of SCP worker at minor level. |
Type | Gauge |
Dimension |
|
Example | ocscp_worker_pod_overload_control_pendingTrans_utilization_minor{pod_name="ocscp-scp-worker-668c75fbc8-kptfv",scp_service="scp-worker"} |
Table 5-153 ocscp_worker_pod_overload_control_pendingTrans_utilization_major
Field | Details |
---|---|
Description | Indicates pending transaction utilization of SCP worker at major level. |
Type | Gauge |
Dimension |
|
Example | ocscp_worker_pod_overload_control_pendingTrans_utilization_major{pod_name="ocscp-scp-worker-668c75fbc8-kptfv",scp_service="scp-worker"} |
Table 5-154 ocscp_worker_pod_overload_control_pendingTrans_utilization_critical
Field | Details |
---|---|
Description | Indicates pending transaction utilization of SCP worker at critical level. |
Type | Gauge |
Dimension |
|
Example | ocscp_worker_pod_overload_control_pendingTrans_utilization_critical{pod_name="ocscp-scp-worker-668c75fbc8-kptfv",scp_service="scp-worker"} |
Table 5-155 ocscp_worker_pod_overload_control_pendingTrans_utilization_warn
Field | Details |
---|---|
Description | Indicates pending transaction utilization of SCP worker at warn level. |
Type | Gauge |
Dimension |
|
Example | ocscp_worker_pod_overload_control_pendingTrans_utilization_warn{pod_name="ocscp-scp-worker-668c75fbc8-kptfv",scp_service="scp-worker"} |
Table 5-156 ocscp_worker_pendingTrans_pod_overload_control_status
Field | Details |
---|---|
Description | Indicates pending transaction utilization of SCP worker at any level. |
Type | Gauge |
Dimension |
|
Example |
|
Table 5-157 ocscp_worker_pod_overload_control_resource_utilization_minor
Field | Details |
---|---|
Description | Indicates overload control resource utilization of SCP worker at minor level. |
Type | Gauge |
Dimension |
|
Example | ocscp_worker_pod_overload_control_resource_utilization_minor{pod_name="ocscp-scp-worker-668c75fbc8-kptfv",scp_service="scp-worker"} |
Table 5-158 ocscp_worker_pod_overload_control_resource_utilization_major
Field | Details |
---|---|
Description | Indicates overload control resource utilization of SCP worker at major level. |
Type | Gauge |
Dimension |
|
Example | ocscp_worker_pod_overload_control_resource_utilization_major{pod_name="ocscp-scp-worker-668c75fbc8-kptfv",scp_service="scp-worker"} |
Table 5-159 ocscp_worker_pod_overload_control_resource_utilization_critical
Field | Details |
---|---|
Description | Indicates overload control resource utilization of SCP worker at critical level. |
Type | Gauge |
Dimension |
|
Example | ocscp_worker_pod_overload_control_resource_utilization_critical{pod_name="ocscp-scp-worker-668c75fbc8-kptfv",scp_service="scp-worker"} |
Table 5-160 ocscp_worker_pod_overload_control_resource_utilization_warn
Field | Details |
---|---|
Description | Indicates overload control resource utilization of SCP worker at warn level. |
Type | Gauge |
Dimension |
|
Example | ocscp_worker_pod_overload_control_resource_utilization_warn{pod_name="ocscp-scp-worker-668c75fbc8-kptfv",scp_service="scp-worker"} |
Table 5-161 ocscp_worker_pod_overload_control_status
Field | Details |
---|---|
Description | Indicates overload control resource utilization of SCP worker at any level. |
Type | Gauge |
Dimension |
|
Example |
|
Table 5-162 ocscp_worker_cca_validation_performed_total
Field | Details |
---|---|
Description | Indicates the number of requests on which CCA validation is performed. |
Type | Counter |
Dimension |
|
Example | ocscp_worker_cca_validation_performed_total{ocscp_fqdn="ocscp-scp-worker.ny-ocscp-01.svc.thrust2"} |
Table 5-163 ocscp_worker_cca_validation_failed_total
Field | Details |
---|---|
Description | Indicates the number of requests that failed CCA validation. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-164 ocscp_worker_cca_validation_feature_enabled_without_https
Field | Details |
---|---|
Description | The CCA header validation feature is enabled without SCP HTTPS deployment. |
Type | Gauge |
Dimension | ocscp_fqdn |
Example | ocscp_worker_cca_validation_feature_enabled_without_https{ocscp_fqdn="ocscp-scp-worker.ny-ocscp-01.svc.thrust2"} |
Table 5-165 ocscp_cache_queue_alert
Field | Details |
---|---|
Description | Indicates the cache queue alert.
Metrics Pegging Condition: This metric value is either 0 or 1. Based on severity, the value will be 1 for that severity, and correspondingly, for other severities, the value will be 0. |
Type | Gauge |
Dimension |
|
Example |
|
Table 5-166 ocscp_load_manager_queue_utilization
Field | Details |
---|---|
Description | Indicates the load manager queue utilization.
Metrics Pegging Condition: This metric value shows the current utilisation of the queue. |
Type | Guage |
Dimension |
|
Example |
|
Table 5-167 ocscp_load_manager_queue_alert
Field | Details |
---|---|
Description | Indicates the load manager queue alert.
Metrics Pegging Condition: This metric value is either 0 or 1. Based on severity, the value will be 1 for that severity, and correspondingly, for other severities, the value will be 0. |
Type | Gauge |
Dimension |
|
Example |
|
Table 5-168 ocscp_global_egress_rl_remote_participant_is_duplicate
Field | Details |
---|---|
Description | This metric keeps track of duplicate remote coherence participants. |
Type | Gauge |
Dimension |
|
Example | ocscp_global_egress_rl_remote_participant_is_duplicate{app="ocscp-scp-cache", app_kubernetes_io_component="microService", app_kubernetes_io_instance="ocscp", app_kubernetes_io_managed_by="Helm", app_kubernetes_io_name="scp-cache", app_kubernetes_io_part_of="ocscp", app_kubernetes_io_version="<SCP release version>", coherenceCluster="scp-coherence-cluster", helm_sh_chart="scp-cache-25.1.100-beta.22", instance="192.168.140.194:8091", job="kubernetes-pods", microservice="scp-cache", namespace="scpsvc", pod="ocscp-scp-cache-dc9b4775b-vhmtx", pod_template_hash="dc9b4775b", ocscp_fqdn="ocscp-scp-worker.scpsvc.svc.cluster.local", scp_local_coh_cluster_name="scp-coherence-cluster", scp_nf_instance_id="6faf1bbc-6e4a-4454-a507-a14ef8e1bc5e", scp_remote_coh_cluster_fqdn="ocats-scp-ocats-scpglbratelimitstub.scpsvc.svc.cluster.local", scp_remote_coh_cluster_name="scpstub-coherence-cluster", scp_remote_coh_cluster_nf_instance_id="6faf1bbc-6e4a-4454-a507-a14ef8e1bc5e", scp_remote_coh_cluster_port="30001", vendor="oracle"} |
Table 5-169 ocscp_worker_health_check_rx_req_total
Field | Details |
---|---|
Description | Number of health check requests received by SCP |
Type | Counter |
Dimension |
|
Example |
|
Table 5-170 ocscp_worker_health_check_success_res_total
Field | Details |
---|---|
Description | Number of success responses sent by SCP in response to the health check status query |
Type | Counter |
Dimension |
|
Example |
|
Table 5-171 ocscp_worker_health_check_error_res_total
Field | Details |
---|---|
Description | Number of error responses sent by SCP in response to the health check status query |
Type | Counter |
Dimension |
|
Example |
|
Table 5-172 ocscp_interscp_health_check_status_success_total
Field | Details |
---|---|
Description | Number of health check success status of peer SCP based on Outlier Detection and Health Check features |
Type | Counter |
Dimension |
|
Example |
|
Table 5-173 ocscp_interscp_health_check_status_failure_total
Field | Details |
---|---|
Description | Number of health check failure status of peer SCP based on Outlier Detection and Health check features |
Type | Counter |
Dimension |
|
Example |
|
Table 5-174 ocscp_health_check_status_failed
Field | Details |
---|---|
Description |
SCP health check status. The value can be either 0 or 1. 0 indicates SCP health check status is successful. 1 indicates SCP health check status has failed. |
Type | Gauge |
Dimension |
|
Example |
|
Table 5-175 ocscp_interscp_health_check_status_failed
Field | Details |
---|---|
Description |
Inter-SCP health check status based on Outlier Detection and Health Check features The value can be either 0 or 1. 0 indicates inter-SCP health check status is successful. 1 indicates inter-SCP health check status has failed. |
Type | Gauge |
Dimension |
|
Example |
|
Table 5-176 ocscp_oauth_access_token_cache_match_total
Field | Details |
---|---|
Description | Number of times requests fetched by access token from cache in SCP-nrfProxy-oauth |
Type | Counter |
Dimension | ocscp_fqdn |
Example | - |
Table 5-177 ocscp_worker_access_token_forwarded_in_tx_res_total
Field | Details |
---|---|
Description | Number of responses in the 3gpp-Sbi-Access-Token header |
Type | Counter |
Dimension | ocscp_fqdn |
Example | - |
Table 5-178 ocscp_worker_access_token_forwarded_in_tx_req_total
Field | Details |
---|---|
Description | Number of requests in the 3gpp-Sbi-Access-Token header |
Type | Counter |
Dimension | ocscp_fqdn |
Example | - |
Table 5-179 ocscp_worker_access_token_cache_match_total
Field | Details |
---|---|
Description | Number of times requests fetched access token from cache in SCP-Worker |
Type | Counter |
Dimension | ocscp_fqdn |
Example | - |
Table 5-180 ocscp_nrf_oauth_error_counts_total
Field | Details |
---|---|
Description | Error responses received from NRF |
Type | Counter |
Dimension |
|
Example | - |
Table 5-181 ocscp_oauth_access_token_tx_rsp_total
Field | Details |
---|---|
Description | Responses from SCP-nrfProxy-oauth to SCP-Worker. |
Type | Counter |
Dimension |
|
Example | - |
Table 5-182 ocscp_oauth_access_token_rx_res_total
Field | Details |
---|---|
Description | Responses from NRF to SCP-nrfProxy-oauth through SCP-Worker. |
Type | Counter |
Dimension |
|
Example | - |
Table 5-183 ocscp_oauth_access_token_tx_req_total
Field | Details |
---|---|
Description | Requests generated by SCP-nrfProxy-oauth toward NRF through SCP-Worker. |
Type | Counter |
Dimension |
|
Example | - |
Table 5-184 ocscp_oauth_access_token_rx_req_total
Field | Details |
---|---|
Description | Requests received in the SCP-nrfProxy-oauth from SCP-Worker. |
Type | Counter |
Dimension | ocscp_fqdn |
Example | - |
Table 5-185 ocscp_worker_access_token_rx_res_total
Field | Details |
---|---|
Description | Access token response from SCP-nrfProxy-oauth to SCP-Worker. |
Type | Counter |
Dimension |
|
Example | ocscp_worker_access_token_rx_res_total{,ocscp_consumer_nf_type="AMF",ocscp_nf_service_type="nsmf-pdusession",ocscp_nf_type="SMF",ocscp_response_code="200",ocscp_response_code_class="2",ocscp_fqdn="ocscp-scp-worker.scpsvc.svc.cluster.local"} |
Table 5-186 ocscp_worker_access_token_tx_req_total
Field | Details |
---|---|
Description | Access token request from SCP-Worker to SCP-nrfProxy-oauth. |
Type | Counter |
Dimension |
|
Example | ocscp_worker_access_token_tx_req_total{ocscp_consumer_nf_type="AMF",ocscp_nf_service_type="nsmf-pdusession",ocscp_nf_type="SMF",ocscp_fqdn="ocscp-scp-worker.scpsvc.svc.cluster.local"} |
Table 5-187 ocscp_audit_interscp_health_check_tx_req_total
Field | Details |
---|---|
Description | Number of inter-SCP health check requests triggered by SCPC-Audit to SCP-Worker |
Type | Counter |
Dimension |
|
Example |
|
Table 5-188 ocscp_audit_interscp_health_check_rx_res_total
Field | Details |
---|---|
Description | Number of inter-SCP health check responses received by SCPC-Audit from SCP-Worker |
Type | Counter |
Dimension |
|
Example |
|
Table 5-189 ocscp_notification_lock_operation_time
Field | Details |
---|---|
Description | Indicates the time taken to acquire and release the lock |
Type | Counter |
Dimension |
|
Example |
|
Table 5-190 ocscp_ignored_processed_nf_notification_total
Field | Details |
---|---|
Description |
Indicates the notifications that are not processed (ignored) because another notification with the same nfinstanceid is processed by another thread. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-191 ocscp_notification_queue_waiting_time
Field | Details |
---|---|
Description | Indicates the time taken by the notification in the waiting queue. |
Type | Counter |
Dimension |
|
Example | ocscp_notification_queue_waiting_time {namespace="ocscp"} |
Table 5-192 ocscp_notification_profile_processing_time
Field | Details |
---|---|
Description | Indicates the total time taken to process notifications. |
Type | Counter |
Dimension |
|
Example | ocscp_notification_profile_processing_time {nfType = "AUSF"} |
Table 5-193 ocscp_metric_5gsbi_upstream_destination_rejection_total
Field | Details |
---|---|
Description |
Tracks the total number of upstream destinations rejected by SCP due to certain unhealthy conditions of the host, such as CircuitBreaker, Producer Congestion Control, etc.
|
Type | Counter |
Dimension |
|
Example |
|
Table 5-194 ocscp_metric_5gsbi_rx_res_failure_total
Field | Details |
---|---|
Description | Tracks the total number of upstream response failures at SCP with a specific cause, such as ConnectionTimeout and UnknownHostException so on. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-195 ocscp_configuration_dnssrv_nrf_non_migration_task_failure_count_total
Field | Details |
---|---|
Description | Indicates the number of failed nonmigrated tasks of the
DNS SRV-based NRF Info feature.
The nonmigrated tasks are
as follows:
|
Type | Counter |
Dimensions |
|
Examples |
|
Table 5-196 ocscp_configuration_dnssrv_nrf_non_migration_task_success_count_total
Field | Details |
---|---|
Description | Indicates the number of successful nonmigrated
tasks.
The nonmigrated tasks are as follows:
|
Type | Counter |
Dimensions |
|
Examples |
|
Table 5-197 ocscp_configuration_dnssrv_nrf_non_migration_task_failure
Field | Details |
---|---|
Description | Indicates the status of the nonmigrated task of the DNS
SRV based NRF Info feature. The status of nonmigrated tasks will be
either 0 or 1.
The nonmigrated tasks are as follows:
|
Type | Gauge |
Dimensions |
|
Examples |
|
Table 5-198 ocscp_configuration_dnssrv_nrf_migration_task_failure
Field | Details |
---|---|
Description | Indicates the status of the migrated task of the DNS SRV
based NRF Info feature. The status of migrated tasks will be either 0 or
1.
The migrated tasks are as follows:
If there is any failure in the following migration task, then the value will become 1, otherwise the value will be 0. |
Type | Gauge |
Dimensions |
|
Examples |
|
Table 5-199 ocscp_configuration_dnssrv_nrf_duplicate_target_detected
Field | Details |
---|---|
Description | Indicates when duplicate target FQDNs are detected across different NRF SRV FQDNs. |
Type | Gauge |
Dimensions |
|
Examples |
|
Table 5-200 ocscp_subscription_nrf_deregistration_success_total
Field | Details |
---|---|
Description | Indicates the number of successful deregistrations with NRF. |
Type | Counter |
Dimensions |
|
Examples |
|
Table 5-201 ocscp_subscription_nrf_deregistration_failure_total
Field | Details |
---|---|
Description | Indicates the number of failed deregistrations with NRF. |
Type | Counter |
Dimensions |
|
Examples |
|
Table 5-202 ocscp_worker_peer_oci_conveyance_total
Field | Details |
---|---|
Description | Indicates the number of messages routed by SCP with peer NF's Overload Control Information (OCI) header. |
Type | Counter |
Dimensions |
|
Examples |
|
Table 5-203 ocscp_worker_oci_conveyance_total
Field | Details |
---|---|
Description | Indicates the number of messages routed by SCP with SCP's OCI header. |
Type | Counter |
Dimensions |
|
Examples |
|
Table 5-204 ocscp_worker_oci_enforced_total
Field | Details |
---|---|
Description |
Indicates the number of messages on which OCI is enforced causing those messages to be responded with error or alternate routed. |
Type | Counter |
Dimensions |
|
Examples |
|
Table 5-205 ocscp_worker_rx_unsupported_oci_scope_total
Field | Details |
---|---|
Description | Indicates the number of messages received with unsupported OCI scope from peer. |
Type | Counter |
Dimensions |
|
Examples |
|
Table 5-206 ocscp_metric_nf_oci_rx_total
Field | Details |
---|---|
Description | Indicates the number of messages received with OCI. |
Type | Counter |
Dimensions |
|
Examples |
|
Table 5-207 ocscp_metric_trafficfeed_partition_unhealthy
Field | Details |
---|---|
Description | No leader is available for Kafka partition. |
Type | Gauge |
Dimensions |
|
Examples | ocscp_metric_trafficfeed_partition_unhealthy{ocscp_cause="no_leader",ocscp_nf_service_type="nudm-uecm",ocscp_trafficfeed_triggerpoint="requestEgress",kafka_partition_id="NA",kafka_broker_id="NA"} |
Table 5-208 ocscp_metric_trafficfeed_success_total
Field | Details |
---|---|
Description | Number of messages sent to traffic feed.
This metric is unavailable when "acks" is set to "0". To make it available, change "acks" to "1" or "all". |
Type | Counter |
Dimensions |
|
Examples | ocscp_metric_trafficfeed_success_total{ocscp_nf_service_type="nausf-auth",ocscp_trafficfeed_triggerpoint="requestEgress",kafka_partition_id="NA",kafka_broker_id="NA"} |
Table 5-209 ocscp_metric_trafficfeed_cluster_unhealthy
Field | Details |
---|---|
Description | The whole traffic feed Kafka cluster is down. |
Type | Gauge |
Dimensions | cause (unreachable) |
Examples | ocscp_metric_trafficfeed_cluster_unhealthy{ocscp_cause=unreachable} |
Table 5-210 ocscp_ignore_unknown_service_total
Field | Details |
---|---|
Description | The total number of unknown services ignored in the NF profile. |
Type | Counter |
Dimensions |
|
Examples |
|
Table 5-211 ocscp_worker_ondemand_discovery_response_cache_skipped_total
Field | Details |
---|---|
Description | The total number of discovery responses from NRF to SCP-Worker that are skipped from being cached due to the configured rule (the configured rule is specified by the RuleName dimension). |
Type | Counter |
Dimensions |
|
Examples |
|
Table 5-212 ocscp_worker_ondemand_discovery_response_cache_added_total
Field | Details |
---|---|
Description | The total number of discovery responses from NRF to SCP-Worker that are cached. |
Type | Counter |
Dimensions |
|
Examples |
|
Table 5-213 ocscp_worker_ondemand_discovery_response_cache_removed_total
Field | Details |
---|---|
Description | The total number of discovery responses from NRF to SCP-Worker that were removed from the cache either due to expiry time or queue overflow. |
Type | Counter |
Dimensions |
|
Examples |
|
Table 5-214 ocscp_nrfproxy_ondemand_discovery_response_cache_skipped_total
Field | Details |
---|---|
Description | The total number of discovery responses from NRF to nrf-proxy that are skipped from being cached due to the configured rule (the configured rule is specified by the RuleName dimension). |
Type | Counter |
Dimensions |
|
Examples | ocscp_nrfproxy_ondemand_discovery_response_cache_skipped_total{microservice="scp-nrfproxy",ocscp_producer_nf_type="PCF",rule_name="rule1",} |
Table 5-215 ocscp_nrfproxy_ondemand_discovery_response_cache_added_total
Field | Details |
---|---|
Description | The total number of discovery responses from NRF to nrf-proxy that are cached. |
Type | Counter |
Dimensions | ocscp_producer_nf_type |
Examples | ocscp_nrfproxy_ondemand_discovery_response_cache_added_total{microservice="scp-nrfproxy",ocscp_producer_nf_type="PCF"} |
Table 5-216 ocscp_nrfproxy_ondemand_discovery_response_cache_removed_total
Field | Details |
---|---|
Description | The total number of discovery responses from NRF to nrf-proxy that were removed from the cache either due to expiry time or queue overflow. |
Type | Counter |
Dimensions | ocscp_producer_nf_type |
Examples | oocscp_nrfproxy_ondemand_discovery_response_cache_removed_total{microservice="scp-nrfproxy",ocscp_producer_nf_type="PCF"} |
Table 5-217 ocscp_worker_problemdetails_details_maxlengthexceeded_total
Field | Details |
---|---|
Description | Number of messages for which the
ProblemDetails.detail parameter in the error
response exceeded the configured value for
errorDetailMaxSize in SCP Features REST API for
enhanced_error_rsp configuration.
|
Type | Counter |
Dimensions | ocscp_attempted_producers |
Examples | ocscp_worker_problemdetails_details_maxlengthexceeded_total{applicationName="ocscp",microservice="scp-worker",ocscp_attempted_producers="[udm1svc.scpsvc.svc.cluster.local, udm2svc.scpsvc.svc.cluster.local]",ocscp_fqdn="ocscp-scp-worker.scpsvc.svc.cluster.local",vendor="Oracle"} |
Table 5-218 ocscp_worker_object_pool_in_use_objects
Field | Details |
---|---|
Description | The total number of pool objects currently in use. |
Type | Gauge |
Dimensions | ocscp_object_pool_name |
Examples | ocscp_worker_object_pool_in_use_objects{ocscp_object_pool_name=STREAM_INFO_OBJECT_POOL} |
Table 5-219 ocscp_worker_object_pool_ready_to_use_objects
Field | Details |
---|---|
Description | The total number of pool objects present in the pool is ready to be used. |
Type | Gauge |
Dimensions | ocscp_object_pool_name |
Examples |
ocscp_worker_object_pool_ready_to_use_objects{ocscp_object_pool_name=STREAM_INFO_OBJECT_POOL} |
Table 5-220 ocscp_worker_object_pool_created_objects
Field | Details |
---|---|
Description | The total number of pool objects created. |
Type | Gauge |
Dimensions | ocscp_object_pool_name |
Examples |
ocscp_worker_object_pool_created_objects{ocscp_object_pool_name=STREAM_INFO_OBJECT_POOL} |
Table 5-221 ocscp_metric_http_egress_res_total
Field | Details |
---|---|
Description | The total number of egress 5G SBI responses from SCP,
including 5G SBI service responses, notification responses, and SCP
health check response messages.
Note: Peg this metric for both HTTP and HTTPS traffic because Hypertext Transfer Protocol Secure (HTTPS) is the secured version of HTTP. |
Type | Counter |
Dimensions | NA |
Examples |
ocscp_metric_http_egress_res_total{applicationName="ocscp",microservice="scp-worker",ocscp_fqdn="ocscp-scp-worker.scpsvc.svc.cluster.local",vendor="Oracle"} |
Table 5-222 ocscp_metric_http_ingress_req_total
Field | Details |
---|---|
Description | The total number of ingress 5G SBI requests at SCP
includes 5G SBI service requests, notification requests, and SCP health
check request messages.
Note: Peg this metric for both HTTP and HTTPS traffic because Hypertext Transfer Protocol Secure (HTTPS) is the secured version of HTTP. |
Type | Counter |
Dimensions | NA |
Examples |
ocscp_metric_http_ingress_req_total{applicationName="ocscp",microservice="scp-worker",ocscp_fqdn="ocscp-scp-worker.scpsvc.svc.cluster.local",vendor="Oracle"} |
Table 5-223 ocscp_worker_object_pool_denied_total
Field | Details |
---|---|
Description | The total count of pool objects denied once MAX_POOL_SIZE is reached. |
Type | Counter |
Dimensions | NA |
Examples |
ocscp_worker_object_pool_denied_total{ocscp_object_pool_name=STREAM_INFO_OBJECT_POOL} |
Table 5-224 ocscp_worker_object_pool_tran_timeout_objects_total
Field | Details |
---|---|
Description | The total counts of pool objects getting total transaction timeouts during different async transaction states in the callflow. |
Type | Counter |
Dimensions |
|
Examples |
|
Table 5-225 ocscp_worker_object_pool_clash_in_callback_total
Field | Details |
---|---|
Description | The total counts of pool objects getting clashed due to an unexpected async flow sequence conflict or usage time ambiguity. |
Type | Counter |
Dimensions |
|
Examples |
|
Table 5-226 ocscp_metric_message_current_request_rate_total
Field | Details |
---|---|
Description | The total number of current request rate per rate limit bucket key. |
Type | Counter |
Dimensions |
|
Examples |
|
Table 5-227 coherence_cache_hits
Field | Details |
---|---|
Description | The total number of cache hits since the last statistics reset. A cache hit refers to a read operation invocation for which an entry exists in this map. |
Type | Counter |
Dimensions |
|
Examples | coherence_cache_hits{coherenceCluster="scp-coherence-cluster"} |
Table 5-228 coherence_cache_size
Field | Details |
---|---|
Description | The total number of entries in cache. |
Type | Counter |
Dimensions |
|
Examples | coherence_cache_size{coherenceCluster="scp-coherence-cluster"} |
Table 5-229 ocscp_worker_https_ingress_connection_success_total
Field | Details |
---|---|
Description | This metric will be pegged upon the successful
establishment of an Ingress HTTPS connection.
Note: Peg this metric for both HTTP and HTTPS traffic because Hypertext Transfer Protocol Secure (HTTPS) is the secured version of HTTP. |
Type | Counter |
Dimensions |
|
Examples |
|
Table 5-230 ocscp_worker_https_ingress_connection_failure_total
Field | Details |
---|---|
Description | This metric will be pegged by Ingress connection
failures, where failure refers to the inability to establish a
connection due to handshake failure.
Note: Peg this metric for both HTTP and HTTPS traffic because Hypertext Transfer Protocol Secure (HTTPS) is the secured version of HTTP. |
Type | Counter |
Dimensions |
|
Examples |
|
Table 5-231 ocscp_worker_https_egress_connection_success_total
Field | Details |
---|---|
Description | This metric will be pegged upon the successful
establishment of an egress HTTPS connection.
Note: Peg this metric for both HTTP and HTTPS traffic because Hypertext Transfer Protocol Secure (HTTPS) is the secured version of HTTP. |
Type | Counter |
Dimensions |
|
Examples |
|
Table 5-232 ocscp_worker_https_egress_connection_failure_total
Field | Details |
---|---|
Description | This metric will be pegged in the case of egress HTTPS
connection failures. Here, failure refers to the inability to establish
a connection due to handshake failure.
Note: Peg this metric for both HTTP and HTTPS traffic because Hypertext Transfer Protocol Secure (HTTPS) is the secured version of HTTP. |
Type | Counter |
Dimensions |
|
Examples |
|
Table 5-233 ocscp_worker_5gsbi_upstream_connect_failure_total
Field | Details |
---|---|
Description | This metric is pegged when an upstream connection with a producer NF fails. |
Type | Counter |
Dimensions |
|
Examples |
|
Table 5-234 ocscp_nrfproxy_oauth_queue_alert
Field | Details |
---|---|
Description | This metric is pegged when the metric value is either 0 or 1. If the severity reaches Minor, Major, or Critical, the value is 1, else 0. |
Type | Gauge |
Dimensions |
|
Examples |
|
Table 5-235 ocscp_worker_pod_overload_control_cpu_utilization_total
Field | Details |
---|---|
Description | This metric is pegged when the CPU threshold exceeds the configured overload levels. |
Type | Counter |
Dimensions | ocscp_threshold_level |
Examples | ocscp_worker_pod_overload_control_cpu_utilization_total{ocscp_threshold_level="MINOR"} |
Table 5-236 ocscp_worker_self_oci_above_oci_conveyance_threshold_total
Field | Details |
---|---|
Description | This metric is pegged when SCP's load exceeds the configured load for self OCI conveyance. |
Type | Counter |
Dimensions | ocscp_oci_threshold_level |
Examples | ocscp_worker_self_oci_above_oci_conveyance_threshold_total{ocscp_oci_threshold_level="CRITICAL"} |
Table 5-237 ocscp_worker_outstanding_requests
Field | Details |
---|---|
Description | This metric tracks the number of requests for which SCP is waiting for a response after routing to the upstream peer. It will be pegged regardless of whether Circuit Breaker (CB) is enabled or not. |
Type | Gauge |
Dimensions |
|
Examples |
|
Table 5-238 ocscp_nrfproxy_ondemand_discovery_cache_notif_local_refresh_total
Field | Details |
---|---|
Description | This metric is pegged at the scp-nrfproxy when the received NF profile causes the cache at scp-nrfproxy to be updated locally. |
Type | Counter |
Dimensions |
|
Examples | ocscp_nrfproxy_ondemand_discovery_cache_notif_local_refresh_total{ocscp_producer_nf_instance_id="7faf1bbc-6e4a-4454-a507-aef01a101a27",ocscp_producer_service_instance_id="8faf1bbc-6e4a-4454-a507-aef01a101a33"} |
Table 5-239 ocscp_nrfproxy_ondemand_discovery_cache_invalid_notif_nrf_refresh_total
Field | Details |
---|---|
Description | This metric is pegged at the scp-nrfproxy when the received NF profile causes a cache record at scp-nrfproxy to be marked as invalid. |
Type | Counter |
Dimensions |
|
Examples | ocscp_nrfproxy_ondemand_discovery_cache_invalid_notif_nrf_refresh_total{ocscp_producer_nf_instance_id="7faf1bbc-6e4a-4454-a507-aef01a101a27",ocscp_producer_service_instance_id="7faf1bbc-6e4a-4454-a507-aef01a101a27"} |
Table 5-240 ocscp_worker_ondemand_discovery_cache_notif_local_refresh_total
Field | Details |
---|---|
Description | This metric is pegged at the scp-worker when the received NF profile causes a cache record at the scp-worker to be updated locally. |
Type | Counter |
Dimensions |
|
Examples | ocscp_worker_ondemand_discovery_cache_notif_local_refresh_total{ocscp_producer_nf_instance_id="7faf1bbc-6e4a-4454-a507-aef01a101a27",ocscp_producer_service_instance_id="8faf1bbc-6e4a-4454-a507-aef01a101a11"} |
Table 5-241 ocscp_worker_ondemand_discovery_cache_invalid_notif_nrf_refresh_total
Field | Details |
---|---|
Description | This metric is pegged at the scp-worker when the received NF profile causes a cache record at the scp-worker to be marked as invalid. |
Type | Counter |
Dimensions |
|
Examples | ocscp_worker_ondemand_discovery_cache_invalid_notif_nrf_refresh_total{ocscp_producer_nf_instance_id="7faf1bbc-6e4a-4454-a507-aef01a101a27",ocscp_producer_service_instance_id="7faf1bbc-6e4a-4454-a507-aef01a101a27"} |
Table 5-242 ocscp_nrfproxy_ondemand_discovery_cache_nrf_refreshed_status_total
Field | Details |
---|---|
Description | This metric is pegged at scp-nrfproxy when the invalid cache entry is refreshed after getting a discovery response from the NRF. |
Type | Counter |
Dimensions |
|
Examples | ocscp_nrfproxy_ondemand_discovery_cache_nrf_refreshed_status_total{refresh_status="Success",ocscp_response_code="200"} |
Table 5-243 ocscp_worker_ondemand_discovery_cache_nrf_refreshed_status_total
Field | Details |
---|---|
Description | This metric is pegged at scp-worker when the invalid cache entry is refreshed upon receiving a discovery response from the NRF. |
Type | Counter |
Dimensions |
|
Examples | ocscp_worker_ondemand_discovery_cache_nrf_refreshed_status_total{ocscp_response_code="200",refresh_status="Success"} |
Table 5-244 ocscp_worker_transaction_time_exhausted_total
Field | Details |
---|---|
Description | This metric indicates that the available time for SCP to further process a given request has exhausted at the scp-worker, based on the timestamp headers. |
Type | Counter |
Dimensions |
|
Examples |
Note: ocscp_consumer_info = (ocscp_consumer_nf_type#ocscp_consumer_host#ocscp_consumer_nf_instance_id) |
Table 5-245 ocscp_worker_timestamp_headers_validation_fail_total
Field | Details |
---|---|
Description |
This metric indicates the number of requests received with either invalid timestamp header values (for example, an invalid 3gpp-Sbi-Max-Rsp-Time header value) or invalid combinations of timestamp headers, but still processed by SCP. Note: SCP continues to route such requests using the configured routing options. |
Type | Counter |
Dimensions |
|
Examples | ocscp_worker_timestamp_headers_validation_fail_total{ocscp_nf_service_type="npcf-smpolicycontrol", ocscp_validation_failure="INVALID_HDR_COMBINATION"} |
Table 5-246 ocscp_nrfproxy_transaction_time_exhausted_total
Field | Details |
---|---|
Description |
This metric indicates that the available time for SCP to further process a given request has exhausted at the nrf-proxy service, based on the timestamp headers. |
Type | Counter |
Dimensions |
|
Examples |
|
Table 5-247 ocscp_oauth_transaction_time_exhausted_total
Field | Details |
---|---|
Description |
This metric indicates that the available time for SCP to further process a given request has exhausted at the nrf-proxy-oauth service, based on the timestamp headers. |
Type | Counter |
Dimensions |
|
Examples | ocscp_oauth_transaction_time_exhausted_total{ocscp_requester_nfType="AMF", ocscp_target_nfType="PCF"} |
Table 5-248 ocscp_worker_med_udv_read_failure_total
Field | Details |
---|---|
Description | This metric indicates that the read, access, or decode of user-defined variables in mediation has failed. |
Type | Counter |
Dimension |
|
Example usage to filter metric by dimension on the Grafana GUI | ocscp_worker_med_udv_read_failure_total{ocscp_mediation_triggerpoint="requestIngress",ocscp_mediation_udv_name="userDefined-var2"} |
Table 5-249 ocscp_worker_med_udv_usage_count_limit_exceeded_total
Field | Details |
---|---|
Description | This metric indicates that the count of user-defined variables in mediation for a particular transaction exceeds the configured maximum usage limit for a single transaction. |
Type | Counter |
Dimension |
|
Example usage to filter metric by dimension on the Grafana GUI | ocscp_worker_med_udv_usage_count_limit_exceeded_total{ocscp_mediation_triggerpoint="requestIngress",ocscp_mediation_udv_max_usage_limit="5",ocscp_nf_type_and_nf_service_type="UDM-nudm-sdm"} |
Table 5-250 ocscp_worker_routing_options_selected_total
Field | Details |
---|---|
Description | This metric indicates the number of requests matching with the specific Routing Options configuration. |
Type | Counter |
Dimension |
|
Example usage to filter metric by dimension on the Grafana GUI |
|
Table 5-251 ocscp_notification_duplicate_profile_detected_total
Field | Details |
---|---|
Description | This metric indicates whether SCP has received any
duplicate SCP or NRF instanceID for another nftype.
This metric is pegged when:
|
Type | Counter |
Dimension |
|
Example usage to filter metric by dimension on the Grafana GUI |
|
Table 5-252 ocscp_worker_pod_overload_control_pending_transaction_total
Field | Details |
---|---|
Description | This metric is pegged when the pending transaction overload threshold is above the normal level. |
Type | Counter |
Dimension | ocscp_threshold_level |
Example usage to filter metric by dimension on the Grafana GUI | ocscp_worker_pod_overload_control_pending_transaction_total{ocscp_threshold_level="MINOR"} |
Table 5-253 ocscp_configuration_rejected_request_total
Field | Details |
---|---|
Description | This metric is pegged when the number of requests to the Configuration service exceeds the configured rate limit. |
Type | Counter |
Dimension | cause |
Example usage to filter metric by dimension on the Grafana GUI | ocscp_configuration_rejected_request_total{cause="TOO_MANY_REQUESTS"} |
Table 5-254 ocscp_notification_nf_profile_rejected_total
Field | Details |
---|---|
Description | This metric is pegged in the following scenarios:
|
Type | Counter |
Dimension | cause |
Example usage to filter metric by dimension on the Grafana GUI |
|
Table 5-255 ocscp_worker_object_pool_uuid_conflict_total
Field | Details |
---|---|
Description | This metric is pegged when there is reusage of transaction context, which is either cleaned or currently in use. |
Type | Counter |
Dimension |
|
Example usage to filter metric by dimension on the Grafana GUI | ocscp_worker_object_pool_uuid_conflict_total{ocscp_object_pool_name="STREAM_INFO_OBJECT_POOL",ocscp_worker_client_name="addRequestTotalTimeoutHandler"operation_type="BY_CONFLICT"} |
Table 5-256 ocscp_worker_object_pool_operation_failure_total
Field | Details |
---|---|
Description | This metric is pegged when there is an object pool state operation failure. |
Type | Counter |
Dimension |
|
Example usage to filter metric by dimension on the Grafana GUI | ocscp_worker_object_pool_operation_failure_total{ocscp_object_pool_name="STREAM_INFO_OBJECT_POOL",ocscp_worker_client_name="DestForwardClient::destCallback",operation_type="POST_ACR", ocscp_object_status_code="OP_DENIED"} |
5.2.2 Mediation Metrics
The following table describes metric supported by the Mediation feature:
Table 5-257 ocscp_med_total_rule_count
Field | Details |
---|---|
Description |
Total number of Mediation rules configured. |
Type | Counter |
Dimension |
|
Example usage to filter metric by dimension on the Grafana GUI |
ocscp_med_total_rule_count{app= "nf-mediation",vendor="oracle"} |
Table 5-258 ocscp_med_active_rule_count
Field | Details |
---|---|
Description | Total number of rules executed when a rule match is found for a particular message. |
Type | Counter |
Dimension |
|
Example usage to filter metric by dimension on the Grafana GUI | ocscp_med_active_rule_count_total{app="nf-mediation",vendor="oracle"} |
Table 5-259 ocscp_med_individual_rule_exec_count_total
Field | Details |
---|---|
Description | Total number of times a particular rule gets invoked. |
Type | Counter |
Dimension |
|
Example usage to filter metric by dimension on the Grafana GUI | sum(ocscp_med_individual_rule_exec_count_total{app="nf-mediation"}) by (ruleName,ruleGroupName) |
Table 5-260 ocscp_med_http_req_total
Field | Details |
---|---|
Description |
Total number of ingress messages to NF. |
Type | Counter |
Dimension |
|
Example usage to filter metric by dimension on the Grafana GUI | ocscp_med_req_total{msgType="request",app="nf-mediation",ruleGroupName="scp-agenda"} |
Table 5-261 ocscp_med_http_rsp_total
Field | Details |
---|---|
Description | Total number of egress messages. |
Type | Counter |
Dimension |
|
Example usage to filter metric by dimension on the Grafana GUI | ocscp_med_rsp_total{msgType="request",ruleGroupName="scp-agenda",statusCode~="2.*"} |
Table 5-262 ocscp_med_test_req_total
Field | Details |
---|---|
Description | Total number of incoming messages to the NF Test mode. |
Type | Counter |
Dimension |
|
Example usage to filter metric by dimension on the Grafana GUI | ocscp_med_test_req_total{msgType="request",app="nf-mediation-test",ruleGroupName="scp-agenda"} |
Table 5-263 ocscp_med_test_rsp_total
Field | Details |
---|---|
Description | Total number of response by the Test mode. |
Type | Counter |
Dimension |
|
Example usage to filter metric by dimension on the Grafana GUI | ocscp_med_test_rsp_total{msgType="request"} |
Table 5-264 ocscp_med_msg_forwarded_to_test_mode_total
Field | Details |
---|---|
Description | Total Number of Requests forwarded to Test mode |
Type | Counter |
Dimension | app(nf-mediation, iwf-mediation) |
Example usage to filter metric by dimension on the Grafana GUI | sum(ocscp_med_msg_forwarded_to_test_mode_total) |
Table 5-265 ocscp_med_rule_update_status
Field | Details |
---|---|
Description | If rules reloading failed or successful.
Value = 0 {failed} Value = 1 {successful} |
Type | Gauge |
Dimension |
|
Example usage to filter metric by dimension on the Grafana GUI | ocscp_med_rule_update_status{app="nf-mediation"} |
Table 5-266 ocscp_med_individual_rule_processing_time_seconds
Field | Details |
---|---|
Description | Processing time of the every rule invoked. |
Type | Histogram |
Dimension |
quantile: A quantile in histogram metrics is a statistical measure that estimates the value below which a given percentage of observations fall, based on the distribution of data across predefined buckets. |
Example usage to filter metric by dimension on the Grafana GUI | - |
Table 5-267 ocscp_med_msg_processing_time_seconds
Field | Details |
---|---|
Description | Processing time of messages received by Mediation. |
Type | Histogram |
Dimension |
quantile: A quantile in histogram metrics is a statistical measure that estimates the value below which a given percentage of observations fall, based on the distribution of data across predefined buckets. statusCode: The response code for the transactions |
Example usage to filter metric by dimension on the Grafana GUI | - |
Table 5-268 ocscp_med_forward_to_ext_total
Field | Details |
---|---|
Description | Total number of messages forwarded to external. |
Type | Counter |
Dimension |
|
Example usage to filter metric by dimension on the Grafana GUI | - |
Table 5-269 ocscp_med_incoming_rsp_from_ext_total
Field | Details |
---|---|
Description |
Total number of responses from external. |
Type | Counter |
Dimension |
|
Example usage to filter metric by dimension on the Grafana GUI | - |
Table 5-270 ocscp_med_incoming_d2h_req_total
Field | Details |
---|---|
Description | Total number of requests from D2H service as a part of the protocol translation mode. |
Type | Counter |
Dimension |
|
Example usage to filter metric by dimension on the Grafana GUI | - |
Table 5-271 ocscp_med_outgoing_rsp_to_d2h_total
Field | Details |
---|---|
Description | Total number of responses to D2H service as a part of protocol translation mode. |
Type | Counter |
Dimension |
|
Example usage to filter metric by dimension on the Grafana GUI | - |
Table 5-272 ocscp_med_forward_to_h2d_total
Field | Details |
---|---|
Description | Total number of messages forwarded to H2D as a part of protocol translation mode. |
Type | Counter |
Dimension |
|
Example usage to filter metric by dimension on the Grafana GUI | - |
Table 5-273 ocscp_med_incoming_rsp_from_h2d_total
Field | Details |
---|---|
Description | Total number of responses received from H2D as a part of protocol translation as a service. |
Type | Counter |
Dimension |
|
Example usage to filter metric by dimension on the Grafana GUI | - |
Table 5-274 ocscp_med_udv_storage_failure_total
Field | Details |
---|---|
Description |
This metric tracks the total number of write operation failures encountered for a user-defined variable when a mediation rule is invoked during a transaction. Condition: The metric is incremented whenever a failure or exception
occurs during write operations such as |
Type | Counter |
Dimension |
|
Example usage to filter metric by dimension on the Grafana GUI | ocscp_med_udv_storage_failure_total{app="ocscp-scp-mediation", vendor="oracle", kubernetes_namespace="medsvc", userDefinedVariable="user-imsi", triggerPoint="requestIngress", operation="set"} |
Table 5-275 ocscp_med_udv_read_failure_total
Field | Details |
---|---|
Description |
This metric represents the total number of read operation failures that occur for a user-defined variable when a mediation rule is invoked for a transaction. Condition: This metric is pegged if any failure or exception occurs
during read operations, such as the |
Type | Counter |
Dimension |
|
Example usage to filter metric by dimension on the Grafana GUI | ocscp_med_udv_read_failure_total{app="ocscp-scp-mediation", vendor="oracle", kubernetes_namespace="medsvc", userDefinedVariable="user-imsi", triggerPoint="requestIngress", operation="has"} |
Table 5-276 ocscp_med_udv_used_total
Field | Details |
---|---|
Description |
This metric represents the total number of transactions in which a Write or Delete operation was performed on user-defined variables. Condition: This metric is pegged whenever a write or delete operation occurs for a transaction. |
Type | Counter |
Dimension |
|
Example usage to filter metric by dimension on the Grafana GUI | ocscp_med_udv_used_total{app="ocscp-scp-mediation", vendor="oracle", kubernetes_namespace="medsvc", triggerPoint="requestIngress", operation="WRITE"} |
Table 5-277 ocscp_med_udv_size_mismatch_total
Field | Details |
---|---|
Description |
This metric represents the total number of times the size of the value assigned to a user-defined variable exceeds the configured size. Condition: This metric is pegged whenever the size of the value assigned to a user-defined variable exceeds the configured size limit. |
Type | Counter |
Dimension |
|
Example usage to filter metric by dimension on the Grafana GUI | ocscp_med_udv_size_mismatch_total{app="ocscp-scp-mediation", vendor="oracle", kubernetes_namespace="medsvc", userDefinedVariable="user-imsi"} |
Table 5-278 ocscp_med_udv_type_mismatch_total
Field | Details |
---|---|
Description |
This metric represents the total number of times the type of the value assigned to a user-defined variable differs from the configured data type. Condition: This metric is pegged whenever the type of the value assigned to a user-defined variable does not match the configured data type. |
Type | Counter |
Dimension |
|
Example usage to filter metric by dimension on the Grafana GUI | ocscp_med_udv_type_mismatch_total{app="ocscp-scp-mediation", vendor="oracle", kubernetes_namespace="medsvc", userDefinedVariable="user-imsi"} |
Table 5-279 ocscp_med_udv_not_configured_total
Field | Details |
---|---|
Description |
This metric represents the total number of times a user-defined variable is used in a mediation rule without being configured. Condition: This metric is pegged whenever a user-defined variable that is not configured is still used in a mediation rule. |
Type | Counter |
Dimension |
|
Example usage to filter metric by dimension on the Grafana GUI | ocscp_med_udv_not_configured_total{app="ocscp-scp-mediation", vendor="oracle", kubernetes_namespace="medsvc", triggerPoint="requestIngress", userDefinedVariable ="user-imsi"} |
Table 5-280 ocscp_med_udvs_max_size_limit_exceeded_total
Field | Details |
---|---|
Description |
This metric represents the total number of times the combined size of all user-defined variables and their values exceeds the configured size limit. Condition: This metric is pegged whenever the total size of all user-defined variables and their values exceeds the configured size. |
Type | Counter |
Dimension |
|
Example usage to filter metric by dimension on the Grafana GUI | ocscp_med_udvs_max_size_limit_exceeded_total{app="ocscp-scp-mediation", vendor="oracle", kubernetes_namespace="medsvc", triggerPoint="requestIngress"} |