5 Metrics
This chapter provides information about newly introduced and updated metrics and its dimensions.
5.1 Dimension Description
The following table provides information on Dimension of Metrics.
Table 5-1 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 | 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: Notifications from NRF to scpc-notification will be pegged with the service type as scpc-notification. |
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. |
ocscp_fqdn | Includes the FQDN of SCP, which is used to deploy
SCP.
The sample values are Loc6, Loc7, and so on. |
plmn_id | Includes the serving PLMN ID of SCP.
The sample value is mnc123-mcc254. |
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 enabled using
values.yaml .scpAuthorityMetricLabelDisabled: false |
ocscp_message_type | Includes the message type received at SCP. It can be of
any type:
|
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 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. |
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. |
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. |
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. |
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 | Error that is received from the NRF during the oAuth2 query. |
error-reason | Reason for ingress or egress connection failures. |
errorType | The error reason that caused notification processing to fail. |
event | The notification was even received in the notification. Example, deregister. |
eventName | Showing the migration state of the NRF DNS SRV feature.
Possible values
|
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, so refer to the respective metric for interpretation. |
failureReason | Reasons for the failure of the NRF DNS SRV feature migration. |
headerModified | Indicates whether any header is modified by the mediation service in response. |
host_type | Indicates the host type used for sending the request. example, "IP" or "FQDN" |
http_method | Indicates the HTTP method of the request getting treatment for overload. Example: PUT, PATCH, POST, etc. |
interScpHost | Contains the host of the SCP to which the request is being sent. |
is_from_local_cache | Whether the NRF discovery response is reterived from local cache (true) or NRF (false) |
is_inter_plmn | 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. |
ocscp_nf_service_type | The NF service type |
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. |
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.1.1 SCP 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.Table 5-2 ocscp_metric_http_rx_req_total
Field | Details |
---|---|
Description | The total number of incoming HTTP requests at the scp-worker service. |
Type | Counter |
Dimension |
Note:
|
Example |
|
Table 5-3 ocscp_metric_http_tx_req_total
Field | Details |
---|---|
Description |
The total number of HTTP requests forwarded by Service Communication Proxy to the upstream cluster. Each SCP-worker pod will peg this metric. Note:The ocscp_authority dimension will get
pegged only when it is enabled using the
|
Type | Counter |
Dimension |
Note:
|
Example |
|
Table 5-4 ocscp_metric_http_rx_res_total
Field | Details |
---|---|
Description | Total number of HTTP responses received by SCP with
specific HTTP response codes (e.g., 201, 503, etc.).
Each SCP-worker pod will peg this metric. |
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-5 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 (e.g., 201, 503, etc.)
Each SCP-worker pod will peg this metric when sending the response back to the consumer. Note:The ocscp_authority
dimension will get pegged only when it is enabled using the
|
Type | Counter |
Dimension |
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. |
Example |
|
Table 5-6 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-7 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-8 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-9 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-10 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-11 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-12 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-13 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-14 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-15 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-16 ocscp_db_operation_failure_total
Field | Details |
---|---|
Description | Number of times audit failed due to database failure. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-17 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-18 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-19 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-20 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-21 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-22 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-23 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-24 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-25 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-26 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-27 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-28 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-29 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-30 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-31 ocscp_metric_scp_generated_response_total
Field | Details |
---|---|
Description | Captures the error response generated by SCP. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-32 ocscp_notification_failure_type_total
Field | Details |
---|---|
Description | Number of Notification failed to process. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-33 ocscp_nrf_notifications_requests_nf_total
Field | Details |
---|---|
Description | Number of Notifications Requests from NRF specific to NFs per NF Type. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-34 ocscp_notification_nf_profile_processing_success_total
Field | Details |
---|---|
Description | Number of notifications processed successfully. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-35 ocscp_audit_ondemand_success_total
Field | Details |
---|---|
Description | Number of Successful On-Demand Audit invokes. |
Type | Counter |
Dimension | nrfRegionOrSetId
For example: (Reg11,Reg1,Reg2) ocscp_fqdn |
Example |
|
Table 5-36 ocscp_audit_ondemand_failure_total
Field | Details |
---|---|
Description | Number of Failure On-Demand Audit invokes. |
Type | Counter |
Dimension | nrfRegionOrSetId
For example: (Reg11,Reg1,Reg2) ocscp_fqdn |
Example |
|
Table 5-37 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-38 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-39 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-40 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-41 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-42 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-43 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_fqdn="udm1svc.default.svc.cluster.local"} ocscp_metric_upstream_response_timeout_total{ocscp_nf_setid="set1.udmset.5gc.mnc012.mcc345"} |
Table 5-44 ocscp_metric_http_streaminfo_create_total
Field | Details |
---|---|
Description | Captures information of application, microservice, fqdn and vendor whenever StreamInfo Object is initialized |
Type | Counter |
Dimension |
|
Example |
ocscp_metric_http_streaminfo_create_total{ocscp_fqdn="ocscp-scp-worker.scpsvc.svc.cluster.local"} |
Table 5-45 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. |
Type | Counter |
Dimension |
|
Example |
ocscp_metric_http_streaminfo_delete_total{ocscp_fqdn="ocscp-scp-worker.scpsvc.svc.cluster.local"} |
Table 5-46 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_fqdn="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_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-47 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_fqdn="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-48 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-49 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-50 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-51 ocscp_no_nf_instance
Field | Details |
---|---|
Description | Indicates the state of number of instances for NFType. |
Type | Gauge |
Dimension |
|
Example |
|
Table 5-52 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-53 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-54 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-55 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-56 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-57 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-58 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-59 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-60 ocscp_notification_request_total
Field | Details |
---|---|
Description | This metric pegs the number of times notifications received on the notification module. |
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-61 ocscp_audit_tx_req_total
Field | Details |
---|---|
Description | This metric pegs the number of times an audit request is initiated for particular NFType, nrfRegionOrSetId, and nrfHost. |
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-62 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. |
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-63 ocscp_metric_interscp_http_tx_req_total
Field | Details |
---|---|
Description | Number of HTTP requests forwarded to the next hop SCP |
Type | Counter |
Dimension |
|
Example |
|
Table 5-64 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. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-65 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-66 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-67 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-68 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-69 ocscp_metric_http_ar_tx_req_total
Field | Details |
---|---|
Description | Indicates the total number of alternate route attempts made by SCP. |
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-70 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-71 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-72 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-73 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-74 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-75 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-76 ocscp_alternate_resolution_dnssrv_rx_error_res
Field | Details |
---|---|
Description | Indicates failed DNS SRV query responses. |
Type | Gauge |
Dimension |
|
Example |
|
Table 5-77 ocscp_producer_load_throttled
Field | Details |
---|---|
Description | Indicates that the producer NF load has exceeded the throttled threshold. |
Type | Gauge |
Dimension | producerFqdn |
Example | ocscp_producer_load_throttled{producerFqdn="udm1svc.scpsvc.svc.cluster.local"} |
Table 5-78 ocscp_producer_load_alternateRoute
Field | Details |
---|---|
Description | Indicates that the producer NF load has exceeded the alternate route state threshold. |
Type | Gauge |
Dimension | producerFqdn |
Example | ocscp_producer_load_alternateRoute{producerFqdn="pcf1svc.scpsvc.svc.cluster.local"} |
Table 5-79 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-80 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-81 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-82 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-83 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-84 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-85 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-86 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-87 ocscp_metric_sepp_http_rx_req_total
Field | Details |
---|---|
Description | The total number of HTTP requests routed towards SEPP. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-88 ocscp_metric_sepp_http_rx_res_total
Field | Details |
---|---|
Description | The total number of HTTP responses received from SEPP. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-89 ocscp_metric_sepp_http_tx_res_total
Field | Details |
---|---|
Description | The total number of HTTP responses routed towards SEPP. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-90 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-91 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-92 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-93 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-94 ocscp_metric_5gsbi_rx_req_total
Field | Details |
---|---|
Description | The total number of incoming HTTPS requests at scp-worker service. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-95 ocscp_metric_5gsbi_tx_req_total
Field | Details |
---|---|
Description | The total number of HTTPS requests forwarded by SCP to upstream cluster. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-96 ocscp_metric_5gsbi_tx_res_total
Field | Details |
---|---|
Description | The total number of HTTPS responses forwarded by SCP
with specific HTTP response codes, for example, 201, 503, and so on.
Note:The ocscp_authority dimension will get
pegged only when it is enabled using the
|
Type | Counter |
Dimension |
|
Example |
|
Table 5-97 ocscp_metric_5gsbi_rx_res_total
Field | Details |
---|---|
Description | The total number of HTTPS responses received by SCP with specific HTTP response codes, for example, 201, 503, and so on. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-98 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-99 ocscp_metric_https_egress_connection_failure_total
Field | Details |
---|---|
Description | The total number of HTTPS egress connection failures. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-100 ocscp_metric_https_ingress_connection_failure_total
Field | Details |
---|---|
Description | The total number of HTTPS ingress connection failures. |
Type | Counter |
Dimension |
|
Example |
|
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_nrf_notifications_requests_total
Field | Details |
---|---|
Description | Number of NRF notifications received. |
Type | Counter |
Dimension | nfType |
Example | ocscp_nrf_notifications_requests_total{ocscp_nf_type="UDM"} |
Table 5-105 ocscp_soothsayer_audit_db_fetch
Field | Details |
---|---|
Description | Indicates the database fetched for audit. |
Type | Counter |
Dimension | ocscp_soothsayer_audit_db_fetch |
Example | ocscp_nrf_notifications_requests_total{ocscp_nf_type="UDM"} |
Table 5-106 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-107 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-108 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-109 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-110 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-111 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-112 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-113 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-114 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-115 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-116 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-117 ocscp_mediation_http_tx_total
Field | Details |
---|---|
Description | Indicates that the request is forwarded to Mediation. |
Type | Counter |
Dimension |
|
Example | ocscp_mediation_http_tx_total(ocscp_mediation_filtername="PCFsmpolicy",ocscp_mediation_triggerpoint="requestIngress") |
Table 5-118 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. |
Type | Counter |
Dimension |
|
Example | ocscp_mediation_http_rx_total(ocscp_mediation_filtername="PCFsmpolicy",ocscp_mediation_triggerpoint="requestIngress") |
Table 5-119 ocscp_mediation_upstream_service_time_ms_total
Field | Details |
---|---|
Description | Indicates the time taken for Mediation processing. |
Type | Counter |
Dimension |
|
Example | ocscp_mediation_upstream_service_time_ms_total(ocscp_mediation_triggerpoint="requestIngress") |
Table 5-120 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(ocscp_mediation_filtername="PCFsmpolicy",ocscp_mediation_triggerpoint="requestIngress") |
Table 5-121 ocscp_notification_queue_utilization
Field | Details |
---|---|
Description | Indicates Notification queue utilization. |
Type | Gauge |
Dimension |
|
Example |
|
Table 5-122 ocscp_notification_queue_alert
Field | Details |
---|---|
Description | Indicates Notification queue alert. |
Type | Gauge |
Dimension |
|
Example |
|
Table 5-123 ocscp_nrfproxy_queue_utilization
Field | Details |
---|---|
Description | Indicates NrfProxy queue utilization. |
Type | Gauge |
Dimension |
|
Example |
|
Table 5-124 ocscp_worker_queue_utilization
Field | Details |
---|---|
Description | Indicates Worker queue utilization. |
Type | Gauge |
Dimension |
|
Example |
|
Table 5-125 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-126 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-127 ocscp_worker_queue_alert
Field | Details |
---|---|
Description | Indicates Worker queue alert. |
Type | Gauge |
Dimension |
|
Example |
|
Table 5-128 ocscp_metric_nf_lci_rx_total
Field | Details |
---|---|
Description | Indicates the number of messages received with the LCI header. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-129 ocscp_metric_nf_lci_tx_total
Field | Details |
---|---|
Description | Indicates the number of messages received with the LCI header. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-130 ocscp_metric_scp_lci_tx_total
Field | Details |
---|---|
Description | Indicates the number of messages forwarded with SCP's LCI header. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-131 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-132 ocscp_scp_load
Field | Details |
---|---|
Description | Metric to record SCP load value. |
Type | Gauge |
Dimension |
|
Example |
|
Table 5-133 ocscp_nf_load
Field | Details |
---|---|
Description | Metric to record NF load value. |
Type | Gauge |
Dimension |
|
Example |
|
Table 5-134 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-135 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-136 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-137 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-138 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-139 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-140 ocscp_metric_nf_unhealthy_total
Field | Details |
---|---|
Description | Number of times a producer NF is marked unhealthy. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-141 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-142 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-143 ocscp_metric_sepp_unhealthy_total
Field | Details |
---|---|
Description | Number of times SEPP is marked unhealthy. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-144 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-145 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-146 ocscp_sepp_unhealthy
Field | Details |
---|---|
Description | Indicate whether all the SEPP instances are unhealthy. |
Type | Gauge |
Dimension |
|
Example |
|
Table 5-147 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_cause="Incorrect Data Director Information",ocscp_nf_service_type="nudm-uecm",ocscp_trafficfeed_triggerpoint="requestEgress"} |
Table 5-148 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-149 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-150 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-151 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-152 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. |
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-153 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-154 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-155 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-156 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-157 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-158 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-159 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-160 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-161 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-162 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-163 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-164 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-165 ocscp_worker_cca_validation_failed_total
Field | Details |
---|---|
Description | Indicates the number of requests that failed CCA validation. |
Type | Counter |
Dimension |
|
Example |
|
Table 5-166 ocscp_worker_cca_validation_feature_enabled_without_https
Field | Details |
---|---|
Description | Indicates the cache queue utilization.
Metrics Pegging Condition: This metric value shows the current utilization of the queue. |
Type | Gauge |
Dimension |
|
Example |
|
Table 5-167 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-168 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-169 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-170 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-23.4.4-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-171 ocscp_worker_health_check_rx_req_total
Field | Details |
---|---|
Description | Number of health check requests received by SCP |
Type | Counter |
Dimension |
|
Example |
|
Table 5-172 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-173 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-174 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-175 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-176 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-177 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-178 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-179 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-180 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-181 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-182 ocscp_nrf_oauth_error_counts_total
Field | Details |
---|---|
Description | Error responses received from NRF |
Type | Counter |
Dimension |
|
Example | - |
Table 5-183 ocscp_oauth_access_token_tx_rsp_total
Field | Details |
---|---|
Description | Responses from SCP-nrfProxy-oauth to SCP-Worker. |
Type | Counter |
Dimension |
|
Example | - |
Table 5-184 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-185 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-186 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-187 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-188 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-189 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-190 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-191 ocscp_notification_lock_operation_time
Field | Details |
---|---|
Description | Indicates the time taken to acquire and release the lock |
Type | Counter |
Dimension |
|
Example |
|
Table 5-192 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-193 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-194 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-195 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-196 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-197 ocscp_configuration_dnssrv_nrf_invalid_data
Field | Details |
---|---|
Description | Indicates the number of invalid DNS SRV records received
by SCP from the DNS SRV server through alternate resolution.
For instance, an invalid target FQDN, an invalid weight, an invalid priority, or an invalid port might all result in invalid DNS SRV records. |
Type | Counter |
Dimensions |
|
Examples |
|
Table 5-198 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-199 ocscp_configuration_dnssrv_nrf_non_migration_task_success_count_total
Field | Details |
---|---|
Description | Indicates the number of successful nonmigrated tasks. |
Type | Counter |
Dimensions |
|
Examples |
|
Table 5-200 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-201 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-202 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-203 ocscp.subscription.nrf.deregistration.success.total
Field | Details |
---|---|
Description | Indicates the number of successful deregistrations with NRF. |
Type | Counter |
Dimensions |
|
Examples |
|
Table 5-204 ocscp.subscription.nrf.deregistration.failure.total
Field | Details |
---|---|
Description | Indicates the number of failed deregistrations with NRF. |
Type | Counter |
Dimensions |
|
Examples |
|
Table 5-205 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-206 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-207 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-208 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-209 ocscp_metric_nf_oci_rx_total
Field | Details |
---|---|
Description | Indicates the number of messages received with OCI. |
Type | Counter |
Dimensions |
|
Examples |
|
Table 5-210 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-211 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-212 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-213 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-214 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-215 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-216 coherence_cache_size
Field | Details |
---|---|
Description | The total number of entries in cache. |
Type | Counter |
Dimensions |
|
Examples | coherence_cache_size{coherenceCluster="scp-coherence-cluster"} |
5.1.2 Mediation Metrics
The following table describes metric supported by the Mediation feature:
Table 5-217 ocscp_med_total_rule_count
Field | Details |
---|---|
Description |
Total number of Mediation rules configured. |
Type | Gauge |
Dimension |
|
Example usage to filter metric by dimension on the Grafana GUI |
ocscp_med_total_rule_count{app= "nf-mediation",nfInstanceId="IWF1",vendor="oracle",kubernetes_namespace="medsvc"} |
Table 5-218 ocscp_med_active_rule_count
Field | Details |
---|---|
Description | Displays the total number of rules invoked at a time. |
Type | Gauge |
Dimension |
|
Example usage to filter metric by dimension on the Grafana GUI | ocscp_med_active_rule_count_total{app="nf-mediation",nfInstanceId="IWF1",vendor="oracle",kubernetes_namespace="medsvc"} |
Table 5-219 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-220 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="consumerRequest",app="nf-mediation",ruleGroupName="scp-agenda"} |
Table 5-221 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="consumerRequest",ruleGroupName="scp-agenda",statusCode~="2.*"} |
Table 5-222 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="consumerRequest",app="nf-mediation-test",ruleGroupName="scp-agenda"} |
Table 5-223 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="consumerRequest"} |
Table 5-224 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-225 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-226 ocscp_med_individual_rule_processing_time
Field | Details |
---|---|
Description | Processing time of the every rule invoked. |
Type | Histogram |
Dimension |
|
Example usage to filter metric by dimension on the Grafana GUI | - |
Table 5-227 ocscp_med_msg_processing_time_seconds
Field | Details |
---|---|
Description | Processing time of messages received by Mediation. |
Type | Histogram |
Dimension |
|
Example usage to filter metric by dimension on the Grafana GUI | - |
Table 5-228 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-229 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-230 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-231 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-232 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-233 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 | - |
Note:
In the above table, <metricPrefix> indicates metric prefix that can be customized. The default metric prefix is ocmed.