6 NRF Metrics, KPIs, and Alerts

6.1 NRF Metrics

This section includes information about metrics for Oracle Communications Cloud Native Core, Network Repository Function.

Note:

  • Sample NRF dashboard for Grafana is delivered to the customer through NRF CSAR package. Metrics and functions used to achieve KPI are covered in NRF CSAR package. For more information on how to download the NRF CSAR package from MOS, see Oracle Communications Cloud Native Core, Network Repository Function Installation, Upgrade, and Fault Recovery Guide.
  • The metric scraping time varies as per the environment in which it is deployed.

The name of the metrics may contain suffix such as total, seconds, max and so on. It gets added by the micrometer registry if it is not present in the metrics name. The metric name has the following format for suffix: <Basename of the metric>_<Suffix>

Table 6-1 Metrics type and Suffix

Metric Type Suffix Description
Counter _total Represents the total number of occurrences of an event or traffic, such as measuring the total amount of traffic received and transmitted by NRF, and so on.
Gauge NA Represents a single numerical value that changes randomly. This metric type is used to measure various parameters, such as NRF load values, memory usage, and so on.
Histogram _max, _bucket, _count, or _sum Represents the sample observations like request durations or response sizes and counts them in configurable buckets. To measure the latency values, _seconds is used.

Dimensions Legend for the Metrics

The following table includes the details about the metrics dimensions:

Table 6-2 Dimensions Legend

Dimension Description
Action Used in Gateway metrics.

Indicates the type of action taken for the requests. (rejects or processes a denied request based on the value of congestion level attribute in the denied request actions object.

Sample Values: REJECT, CONTINUE

ActionId Used in Gateway metrics.

Indicates the unique Id of the request.

Sample Values: 1, 2

Allowed Used in Gateway metrics.

Indicates if the requests are accepted or rejected. If the request is below fillRate, the value is set as true. If the request is above the fillRate, the value is set as false.

Sample Values: true, false

application Indicates the application name.

Sample Values: ocnrf

authority

Used in Gateway metrics.

Indicates the destination address.

BackendSvc

Used in Gateway metrics.

Indicates the address of destination.

BackendSvcAddressType

Used in Gateway metrics.

Indicates the IP type (IPv4/IPv6) of the destination from the Egress Gateway.

Bucket Indicates how many profiles are returned in the response of Discovery request. Range is not configurable. Possible values are 0-10, +Inf. According to NF profiles returned, corresponding bucket will be incremented by one. For example, if 2 profiles are returned, then bucket 2 will be incremented by one. Profiles getting returned more than 10 will fall in +Inf bucket.
CertificateName Indicates the ccaHeaderValidation file name configured in Helm.
ClientCertIdentity

Used in Gateway metrics.

Indicates the certificate identity of the client, SAN=127.0.0.1,localhost CN=localhost, N/A if data is not available.

ClientNfInstanceId Indicates the client NF Instance Id for NF Access Token.
client_type

Used in Gateway metrics.

Indicates the type of jetty client being used at Ingress Gateway.

Sample Values: h2, h2c

CongestionLevel

Used in Gateway metrics.

Indicates the congestion level of the pods.

Sample Values: 0, 1, 2, 3

connectionId Indicates the connectionId of the http2 connection.
ConsumerInstanceId Indicates the consumer NF's NfInstanceId configured in Sub in JWT token.
ConsumerNFInstanceId Indicates the consumer NF Instance Id for NF Access Token
ConsumerNFType Indicates request is for which consumer NF type.
content_available Used in Gateway metrics.

Indicates if the incoming request to Ingress Gateway has a request body present in it.

Sample Values: true, false

DataType Indicates the type of data.

Sample Values: NfProfiles, NfSubscriptions

dbOperation Indicates the database operation type such as Create, update, delete, and find.
DestinationHost

Used in Gateway metrics.

Indicates the destination IP address or FQDN of the host.
destinationHostAddressType

Used in Gateway metrics.

Indicates the destination IP type (IPv4 or IPv6) from Egress Gateway.

Direction

Used in Gateway metrics.

Indicates the direction of the request or response.

In case of Ingress Gateway, the value is ingress.

In case of Egress Gateway, the values are egress, egressOut.

DiscardAction

Used in Gateway metrics.

Indicates the type of pod discard in overload filter.

Sample Values: PercentageBased, PriorityBased

dnsResolvedType

Used in Gateway metrics.

Indicates the actual DNS resolved IP type (IPv4 or IPv6) of the destination.

egressRoutingMode

Used in Gateway metrics.

Indicates the value of the egressRoutingMode configured in Egress Gateway.

Sample Values: IPv4, IPv6, IPv4_IPv6, IPv6_IPv4, None

ErrorProfile

Used in Gateway metrics.

Indicates a valid error code for rejected requests based on the action.

Sample Values: "ERR_POD_PROTECTION_RATE_LIMIT"

error_reason

Indicates the reason for failure response received. If message is sent in the response, then it is filled with the message otherwise exception class is filled. In case of successful response it is filled with "no-error".

Sample Values:
  • "no_error" (In case successful response is received)
  • "java.nio.channels.ClosedChannelException"
  • "unable to find valid certification path to requested target"
  • "SSL handshake failed due to invalid SNI"
ErrorOriginator

Used in Gateway metrics.

Indicates the source of error like ServiceProducer, Nrf, IngressGW, None.

ErrorReason Indicates the CCA header validation failed message like: aud claim validation failed, sub claim validation failed, JWT Signature does not match, X5C certificate has expired.
event

Used in Gateway metrics.

Indicates the lifecycle event processed during the jetty request processing with the back-end services.

Sample Values: onQueued, onBegin, onHeaders, onCommit, onContent, onSuccess, onFailure

ExceptionAttribute Indicates the NFDiscover search query attribute due to which NFDiscover service operation is not rejected even SLF specific mandatory attributes are missing from search query.
FailureReason Indicates the failure reason for Roaming Support.
Sample Values:
  • PeerGeneratedError: Error response received from NRF Peer node.
  • EgressGatewayGeneratedError: Error response received from NRF Egress Gateway.
  • InternalError: Roaming request not sent to hNRF because failure occurred at hNRF due to internal error.
ForwardingBarringReason Indicates the forwarding barring reason for NF Access Token and NFDiscover service operations.
Sample Values:
  • forwardingFeatureDisabled: Forwarding feature is disabled.
  • forwardingRuleNotMatched: Forwarding Rule is not matching with the configuration.
GroupId Indicates the GroupId returned by SLF/UDR corresponding to SubscriptionId.
HeartbeatTimer Indicates the heartbeatTimer of the NfProfile. The value is considered in seconds.
Host

Used in Gateway metrics.

Indicates the gateway port (IP or FQDN). Indicates the remote address of client connected to the Ingress Gateway.

HttpStatusCode Indicates the HTTP Status Code.

Sample Values 429, 500

Note: If this error code is generated by Egress Gateway microservice, then the status code is updated as Egw-<response code>.

Sample Value: Egw-429

HttpVersion Indicates the Http protocol version.
Sample Values:
  • HTTP/1.1
  • HTTP/2.0
Id

Used in Gateway metrics.

Corresponds to the id defined in the routes of the Pod Protection configuration.

Sample Values: 1, 2, 3, default_route

InstanceIdentifier

Used in Gateway metrics.

Indicates the pod prefixes configured in helm when there are multiple instances in same deployment- Prefix configured in helm otherwise UNKNOWN.

isCurrentKeyId Indicates if a specific metric is for current key id in Access Token Configuration.

Sample Values: true, false

isLeaderPod

Used in Perf-Info.

Indicates if the pod calculating the threshold level is a leader pod or not.

Sample Values: true, false

jetty_request_timeout Used in Gateway metrics.

Indicates if a request at Egress Gateway failed due to request timeout at jetty level.

Sample Values: true, false

KeyId Indicates if the Key Id from Access Token Configuration is used to sign the Access Token.
KeyType Indicates the Key type of Access Token Configuration (private key or certificate).
LoadLevel Used in Gateway metrics.

Indicates the load level of backend microservices which are configured in the "routes" of the Ingress Gateway microservice.

Sample Values: L1, L2

Method/method Indicates the HTTP Method Name.
Sample Values:
  • PUT
  • GET
NegotiatedTLSVersion This denotes the TLS version used for communication between the server and the client. Sample Values: TLSv1.2, TLSv1.3.
NewStatus Indicates the new NfStatus of the NfProfile or NfService.
Sample Values:
  • REGISTERED
  • SUSPENDED
  • UNDISCOVERABLE
  • DEREGISTERED
NfFqdn

Indicates the FQDN of consumer NF.

The nfFqdn dimension will contain the FQDN as present in the nfProfile.

When service mesh is enabled, this dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

NfInstanceId Indicates the Unique identity of the NF Instance sending request to NRF.
NfServiceFqdn Indicates the FQDN of the NfService.
NFServiceType

Used in Gateway metrics.

Indicates the NFType extracted from URI. Path is /nxxx-yyy/vz/.......

Where nxxx-yyy is NFServiceType

UNKNOWN if unable to extract NFServiceType from the path

Example: nnrf-nfm/v1/nf-instances

NfSetFqdn Indicates the domain name or FQDN for NAPTR record. It is populated using amfSetFqdn.
NfType Indicates the types of Network Functions (NF).
NFType

Used in Gateway metrics.

Indicates the NFType extracted from URI. Path is /nxxx-yyy/vz/.......

Where xxx will be changed to (Upper Case) is NFType

UNKNOWN if unable to extract NFType from the path

Example: nnrf-nfm/v1/nf-instances

Node Indicates the name of the Kubernetes worker node on which microservice is running.
NotificationEventType Indicates the subscription request is for which event types.
Sample Values:
  • NF_REGISTERED
  • NF_DEREGISTERED
  • NF_PROFILE_CHANGED
NotificationHostPort Indicates the port of notification callback server.
NRFRole Indicates the NRF role whether it is hNRF or vNRF.

Sample Values: hNRF, vNRF

NrfFqdn Indicates the FQDN of NRF.
nrfInstanceId Indicates the Nrf Instance Id of NRF.
NrfLevel Indicates the NRF Deployment Name by which NRF can be identified, it will be NRF Instance Id passed through Helm.
Nsi Indicates the Network slices are identified by Network Slice Instances (NSIs). It is in the string format.
NumberOfRetriesAttempted Indicates the number of retries attempted to notification callback server.
oAuthHeaderPresent

Used in Gateway metrics.

Indicates if the oAuth header is present or not.

Sample Values: true, false

oAuthTokenPresent

Used in Gateway metrics.

Indicates if the oAuth token is present or not.

Sample Values: true, false

OperationType Indicates the Operation type of the request sent towards DNS server.
Sample Values:
  • Create: NF create request towards DNS server
  • Update: NF update request towards DNS Server
  • Delete: NF delete request towards DNS Server
OperationType Indicates if the NFSubscribe Service operation to specify if the request is to create or update the subscription.
Sample Values:
  • Create
  • Update
peer Indicates the SCP peer.
peerset Indicates the SCP peerset.
PreviousSLFFqdn Indicates the target SLF FQDN where the previous request was sent to and failed.
PreviousStatus Indicates the previous NfStatus of the NfProfile or NfService.
Sample Values:
  • REGISTERED
  • SUSPENDED
  • UNDISCOVERABLE
  • DEREGISTERED
Priority

Used in Gateway metrics.

Indicates the priority of the request.

Sample Values: 24

ProducerInstanceId Indicates the NrfInstanceId.
quantile Indicates the latency values with ranges as 10ms, 20ms, 40ms, 80ms, 100ms, 200ms, 500ms, 1000ms, and 5000ms.
QueryType

Indicates the type of the query sent by the NF.

Sample Values:
  • NfProfiles
  • NfSubscriptions
receivedAddressType

Used in Gateway metrics.

Indicates the IP type (IPv4/IPv6) of the remote client connected to the Ingress Gateway.

RejectionReason Indicates the rejection reason for NF Access Token, Roaming Support, Subscription limit breached.
Sample Values:
  • ClientNotAuthorized: Number of access token request for which client authorized failed
  • ProducerWithRequestedScopeNotFound: Number of access token not granted because of no producer instance registered for service/s in the scope
  • ProducerWithRequestedNfInstanceIdNotFound: Number of access token not granted because of no producer instance registered for No producer instance is registered at all for provided target Instance Id in request.
  • InconsistentScope: Number of access token not granted because services in the scope belong to different NF types.
  • ProducerNFTypeMismatch: Number of access token not granted because producer NF type in profile is not matching with the access token request.
  • InternalError: Number of access token not granted because failure at NRF due to internal error.
  • ConsumerNfTypeNotAllowed: Number of access token not granted because the consumer NFType is not allowed to access the requested NF.
  • ConsumerPlmnNotAllowed: Number of access token not granted because the consumer NF PLMN is not allowed to access the requested NF.
  • SecretNotAccessible: Number of access token not granted because the secret for current key id is not accessible.
  • InvalidFileData: Number of access token not granted because the current key id file data is invalid.
  • NamespaceNotAccessible: Number of access token not granted because the namespace for current key id is not accessible.
  • FileNotFound: Number of access token not granted because the file not found in secrets.
  • CurrentKeyIdNotConfigured: Number of access token not granted because the current key id is not configured.
  • ExpiredCertificate: Number of access token not granted because the NRF certificate is expired.
  • BadRequest: Number of access token not granted because the Request is incorrect.
  • NFFqdnAuthenticationFailed: Number of access token not granted because of NF Fqdn Authentication Failure
  • ConfigurationMissing: Number of access token not granted because of configuration missing
  • ConsumerDetailsNotMatched: Number of access token not granted because consumer details in profile is not matching with the access token request.
  • InvalidProducerPlmn: Number of access token not granted because targetPlmn in profile is not matching with the access token request.
  • ProducerNFProfileNotFound: Number of access token not granted because there are no NFs found for the requested profile
  • AuthScreeningFailed: Number of access token not granted because the consumer NF is not authorized to access the requested NF or its services.
  • InternalError: Request not forwarded because failure occurred at NRF due to internal error.
  • NRFCommunicationFailure: Request not forwarded because NRF is not able to connect with another NRF.
  • ErrorFromNRF: Error response received from another NRF.
  • NRFForwardingConfigurationMissing: Request not forwarded due to missing forwarding configuration.
  • LoopDetected: Received request message is already processed by NRF during forwarding mechanism.
  • *NotApplicable is applicable for 2xx Status code.
  • MandatoryAttributesMissing: Roaming request is rejected due to mandatory attribute missing in the request.
  • TargetMatchesNRFPLMN: Request intended for roaming but target PLMN matches with the vNRF PLMN.
  • TargetNotMatchesNRFPLMN: Request intended for roaming hNRF but target PLMN not matches with the hNRF PLMN.
  • NotificationURINonPLMNFormat: Notification URI in NFStatusSubscribe request is not in 3GPP defined PLMN format for roaming.
  • RoamingDisabledAttributesPresent: Roaming is disabled but roaming specific parameters are present.
  • RequesterNFTypeNotAllowed: Requester NF Type is not allowed to access the NF Producer Type.
  • RequesterPLMNNotAllowed: Requester PLMN Type is not allowed to access the NF Producer Type.
  • RequesterSNSSAINotAllowed: Requester SNSSAI Type is not allowed to access the NF Producer Type.
  • PeerGeneratedError: Error response received from NRF Peer node.
  • EgressGatewayGeneratedError: Error response received from NRF Egress Gateway.
  • InternalError: Roaming request not sent to hNRF because failure occurred at hNRF due to internal error.
  • EgressGatewayOverloaded: Error response received from NRF Egress Gateway when it is overloaded.
RemoteNrfInstanceId Indicates the Nrf Instance Id of the remote NRF.
RemoteSiteName Indicates the site name of remote NRF.
Replacement Indicates the value as populated using 3GPP AMF name.
Sample Values:
  • 0 - Healthy
  • 1 - Failure - Any Failure which is not covered below
  • 2 - Not Found in DNS server
  • 3 - Mismatch with DNS Server and NRF data
RequesterNfType Indicates the NF type which originating the request. This value comes from UserAgent header. For NFDiscover Service operation it is taken from Search Query.

In case, there is no header or value, this value will be UNKNOWN in the metrics.

RequesterPLMNId Indicates the PLMN ID which originating the request.
RequestType

Indicates the type of the service request sent by the NF.

Sample Values:

  • RemoteAndLocalSetProfiles - is pegged for the requests received from discovery and remote cache data service.
  • ProfilesByQueryParam - is pegged for the requests received from the nfregistration service for NfProfileRetrieval and NfListRetrieval, and from nfaccesstoken service for AccessToken requests.
  • RemoteAndLocalSetSubscriptions - is pegged for requests querying for subscription data.
ResponseReason Indicates the response reason in response sent back to NF.
Sample Values:
  • ResponseReason =SLFCommunicationFailure = NRF unable to communication with SLF
  • ResponseReason =MandatoryParamsMissing = Mandatory Parameter (Subscriber data) for performing SLF is missing in the incoming discovery request
  • ResponseReason =SLFSubscriberNotProvisioned = Subscriber not provisioned
  • ResponseReason =ErrorFromSLF = Error response received from SLF (non 2xx, excluding 404)
  • ResponseReason =InternalError = NRF internal error
  • ResponseReason =SuccessFromSLF = Successful SLF lookup
  • ResponseReason = SkipSlfAttributeUsedFromSearchQuery = No SLF performed due to SkipSLF attribute configuration
  • ResponseReason = ExceptionAttributePresentInSearchQuery = No SLF performed due to Exception attribute configuration
route_id Used in Gateway metrics.

Indicates a unique Id to identify a specific route. All the requests always get mapped to a unique route.

Sample Values: egress_scp_proxy1, default_route
RouteLevelColor

Used in Gateway metrics.

Indicates Green color for the requests accepted at route level policer and Red for requests rejected at route level policer.

Sample Values: RED, GREEN

Route_path

Used in Gateway metrics.

Indicates the Path predicate or Header predicate that matched the current request.

Scheme Inidicates the HTTP protocol scheme.
Sample Values:
  • HTTP
  • HTTPS
  • UNKNOWN
Scope Indicates the scope as received in the AccessToken Request

Sample Values: NfDiscover, NFProfileRetrieval

SecretName Indicates the k8SecretName configured in Helm.
serialNumber Indicates the type of the certificate.

Sample Values: serialNumber=4661 is used for RSA and serialNumber =4662 is used for ECDSA

service

Used in Perf-Info.

Indicates the NRF microservice type.

Sample Values: ocnrf-nfaccesstoken, ocnrf-nfdiscovery

ServiceInstanceId Indicates the unique ID of the service instance within a given NF Instance.
ServiceName Indicates the service instance name.

Sample Values: nudm-sdm

ServiceOperation Indicates the service operations as defined in 3GPP specification for NRF.
Sample Values
  • NfProfileRetrieval
  • NfListRetrieval
  • NfAccessToken
  • NfDiscover
  • NfStatusSubscribe
  • NfStatusUnsubscribe
  • NfStatusNotify
  • nrfCacheDataService
siteName Indicates the site name of NRF.
SkipSLFLookupParameter Indicates the NFDiscover search query attribute due to which SLF lookup is skipped.

Sample Values: group-id-list

SkipSLFLookupValue Indicates the configured value for which SLF lookup is skipped, if enableValueBasedSkipSLFLookup is set to true.

If the value of enableValueBasedSkipSLFLookup is set as false, the value of SkipSLFLookupValue dimension is set as NotApplicable.

slfFqdn Indicates the FQDN of the SLF.
sni_status Indicates if the SNI feature is enabled or disabled when an invalid SNI (direct and indirect routing) is sent.
Sample Values:
  • true
  • false
sNssai Indicates the Network slices are identified by Single Network Slice Selection Assistance Information (SNSSAI). It is in string format as outlined in 3GPP TS 29.571 section 5.4.4.2.
SourceNrfSetId Indicates the set ID of the source NRF.
Status Indicates the HTTP Status Code in response.

When used in Gateway metrics it indicates the status of the pod.

Sample Values: DISCARDED

StatusCode Indicates the HTTP Status code.
SubscriberPLMNId Indicates request is for which subscriber PLMN ID.
SubscriptionIdType Indicates the Subscription Id type for which SLF query is received.
subscriptionLimitFeatureStatus Indicates whether the Subscription Limit feature is enabled or disabled.
Sample Values:
  • enabled
  • disabled
SubscriptionStatus Indicates the Status of subscription.
Sample Values:
  • SUBSCRIBED
  • SUSPENDED
  • UNSUBSCRIBED
tableName Indicates the NRF Table Name
TargetNfInstanceId Indicates the target NF Instance Id for NF Access Token.
TargetNfType Indicates request is for which target NF type.
TargetNrfFqdn Indicates the FQDN of the NRF to which the request is forwarded to.
TargetNrfSetId Indicating the set ID of the target NRF.
TargetPLMNId Indicates request is for which target PLMN ID.
TargetSLFFqdn Indicates the target SLF FQDN where the current SLF request is sent.
TLSFqdn Indicates the Fully Qualified Domain Name (FQDN) received in TLS Certificate.
TriggerMode Indicates the trigger mode.

Sample Values

  • Automatic: Triggers generated by 3GPP service operations or NRF Audit.
  • Manual: Triggers generated by the operator initiated retrigger API.
type
This dimension is used in Gateway services and in Perf-Info.
  • Gateway services:

    Indicates whether it is a request towards Data Director or an acknowledgement from Data Director.

    Sample Values:
    • req: Indicates request is sent from Ingress Gateway Microservice towards Data Director.
    • ack: Indicates Data Director has sent an acknowledgement for the received request. This will be only pegged if ack is enabled in NRF Message Feed feature.
  • Perf-Info:

    Indicates the resource type.

    Sample Value: svc_failure_count, svc_pending_count, cpu

Updatetype (Partial/Complete) Indicates if the NF Update is with PUT (Complete) or PATCH (Partial) methods.
Sample Values:
  • PUT
  • PATCH
Uri Indicates the URI defined to identify the service operation at Ingress Gateway.
vendor Indicates the Vendor name of NRF.

Sample Values:Oracle

vfqdn Indicates the FQDN of the peer.
XfccHeaderPresent

Used in Gateway metrics.

Indicates if the XFCC header is present or not.

Sample Values: true, false

6.1.1 NRF Gateways Metrics

This section provides details about the Gateway metrics of NRF.

6.1.1.1 Ingress Gateway Metrics

Table 6-3 oc_ingressgateway_msgcopy_requests_total

Field Details
Description This is incremented whenever request message is sent or acknowledged from Kafka.
Type Counter
Dimensions type

Table 6-4 oc_ingressgateway_msgcopy_responses_total

Field Details
Description This is incremented whenever response message is sent or acknowledged from Kafka.
Type Counter
Dimensions type

Table 6-5 oc_ingressgateway_dd_unreachable

Field Details
Description

This indicates whether DD (kafka) is reachable or not

0 - reachable, 1 - unreachable

Type Gauge

Table 6-6 oc_ingressgateway_jetty_request_stat_metrics_total

Field Details
Description This metric is pegged for every event occurred when a request is sent to Ingress Gateway.
Type Counter
Dimensions event, client_type, InstanceIdentifier, DestinationHost

Table 6-7 oc_ingressgateway_jetty_response_stat_metrics_total

Field Details
Description This metric is pegged for every event occurred when a response is received by Ingress Gateway.
Type Counter
Dimensions event, client_type, InstanceIdentifier, DestinationHost

Table 6-8 oc_ingressgateway_traffic_rejection_mode

Field Details
Description Gauge metric that pegs if the traffic is being rejected or not. The possible values are 0 and 1 (where "1" stands for rejected).
Type Gauge

Table 6-9 oc_ingressgateway_http_requests_total

Field Details
Description Total number of ingress requests received at NRF.
Type Counter
Dimensions ClientCertIdentity, NFType, NFServiceType, Host, DestinationHost, oAuthTokenPresent, HttpVersion, Scheme, Route_path, InstanceIdentifier, consumerNfType, consumerInstanceId, ConsumerFqdn

Table 6-10 oc_ingressgateway_http_responses_total

Field Details
Description Total number of responses for the following service operations at NRF:
  • NfRegister
  • NfUpdate (complete/partial replacement)
  • NfDelete
  • NfProfileRetrieval
  • NfListRetrieval
  • NFStatusSubscribe
  • NFStatusUnSubscribe
  • NfDiscover
  • NfAccessToken
Type Counter
Dimensions Status, Method, Route_path, NFType, NFServiceType, Host, DestinationHost, HttpVersion, Scheme, InstanceIdentifier, ClientCertIdentity, ErrorOriginator, jetty_request_timeout, error-reason

Table 6-11 oc_ingressgateway_http_responses_total (4xx responses)

Field Details
Description Total number of 4xx responses for the following service operations at NRF.
  • NfRegister
  • NfUpdate (complete/partial replacement)
  • NfDelete
  • NfProfileRetrieval
  • NfListRetrieval
  • NFStatusSubscribe
  • NFStatusUnSubscribe
  • NfDiscover
  • NfAccessToken
Type Counter
Dimensions Status, Method, Route_path, NFType, NFServiceType, Host, DestinationHost, HttpVersion, Scheme, InstanceIdentifier, ClientCertIdentity, ErrorOriginator, jetty_request_timeout, error-reason

Table 6-12 oc_ingressgateway_http_responses_total (5xx responses)

Field Details
Description Total number of 5xx responses for the following service operations at NRF.
  • NfRegister
  • NfUpdate (complete/partial replacement)
  • NfDelete
  • NfProfileRetrieval
  • NfListRetrieval
  • NFStatusSubscribe
  • NFStatusUnSubscribe
  • NfDiscover
  • NfAccessToken
Type Counter
Dimensions Status, Method, Route_path, NFType, NFServiceType, Host, DestinationHost, HttpVersion, Scheme, InstanceIdentifier, ClientCertIdentity, ErrorOriginator, jetty_request_timeout, error-reason

Table 6-13 oc_ingressgateway_request_latency_seconds

Field Details
Description Time (in microseconds) to process an Ingress Gateway request. It is measured from when the request is received to when the response is sent
Type Histogram
Dimensions quantile, InstanceIdentifier, Route_path, Method

Table 6-14 oc_ingressgateway_connection_failure_total

Field Details
Description Total number of failures at Ingress Gateway while establishing a connection with NRF.
Type Counter
Dimensions Host, Port, Direction, InstanceIdentifier, error_reason, ErrorOriginator

Table 6-15 oc_ingressgateway_request_processing_latency_seconds

Field Details
Description Metric to capture the amount of time taken for processing of the request only within Ingress Gateway
Type Histogram
Dimensions quantile, InstanceIdentifier, Route_path, Method

Table 6-16 oc_ingressgateway_request_content_metrics_total

Field Details
Description This metric is pegged by default filter RequestContentMetrics. It pegs whether a request has the request body or not.
Type Counter
Dimensions method, content_available, InstanceIdentifier

Table 6-17 oc_ingressgateway_xfcc_header_validate_total

Field Details
Description This metric is pegged when xfccHeaderValidation is enabled in XfccHeaderValidationFilter. This metric along with the specified dimension captures the successful/ un-successful validation of XFCC header in the incoming request.
Type Counter
Dimensions Route_path, Status, Cause, CertsCompared, InstanceIdentifier, ErrorOriginator, ServiceType, ErrorDetail

Table 6-18 oc_ingressgateway_incoming_connections

Field Details
Description Gauge metric that will peg active incoming connections from client to Ingress Gateway.
Type Gauge
Dimensions Direction, Host, InstanceIdentifier

Table 6-19 oc_ingressgateway_outgoing_connections

Field Details
Description Gauge metric that will peg active outgoing connections from Ingress Gateway to destination.
Type Gauge
Dimensions Direction, Host, InstanceIdentifier

Table 6-20 oc_ingressgateway_count_invalid_route

Field Details
Description Counter metric that is pegged for every invalid route.
Type Counter
Dimensions oAuthHeaderPresent, XfccHeaderPresent

Table 6-21 oc_ingressgateway_request_latency_seconds_bucket

Field Details
Description This metric is pegged when a request comes to Ingress gateway. It shows latency consumed by ingress to process the request.
Type Histogram
Dimensions Method, Route_path, InstanceIdentifier

Table 6-22 oc_ingressgateway_server_latency_seconds_bucket

Field Details
Description This metric is pegged when a request comes to Ingress gateway. It shows latency consumed by the backend to process the request.
Type Histogram
Dimensions Method, Route_path, InstanceIdentifier

Table 6-23 oc_ingressgateway_jetty_request_stat_metrics_total

Field Details
Description This metric is pegged for every outgoing request from Ingress gateway to the backend at jetty level
Type Counter
Dimensions DestinationHost, InstanceIdentifier, event, client_type

Table 6-24 oc_ingressgateway_cca_header_request_total

Field Details
Description This metric is pegged when CCA validation is enabled and CCA header is present in the request.
Type Counter
Dimensions ConsumerInstanceId, ProducerInstanceId

Table 6-25 oc_ingressgateway_cca_header_response_total

Field Details
Description This metric is pegged when an error response is sent due to a validation error of the CCA header.
Type Counter
Dimensions ConsumerInstanceId, ProducerInstanceId, StatusCode, ErrorReason

Table 6-26 oc_ingressgateway_cca_certificate_info

Field Details
Description Gauge metric used to peg the expiry date of the certificate. This metric is used further for raising alarms.
Type Counter
Dimensions CertificateName, SecretName, SerialNumber

Table 6-27 oc_ingressgateway_pod_congestion_state

Field Details
Description The metric is used to track the overall congestion state per Ingress Gateway pod. The values of the metric is as follow:
  • -1: Feature is Disabled
  • 0: Normal
  • 1: DangerOfCongestion
  • 2: Congested

Note: Prometheus automatically injects pod name with label name "kubernetes_pod_name" to metric. This information is used for alert.

Type Gauge
Dimensions InstanceIdentifier

Table 6-28 oc_ingressgateway_pod_resource_stress

Field Details
Description This metric pegs the CPU usage and the pending message count, based on which Ingress Gateway pod is calculating its congestion state.
Type Gauge
Dimensions InstanceIdentifier, type

Possible values for type are CPU, MEMORY, PENDING_REQUEST.

Note: The type "MEMORY" is not used to determine the pod congestion state in NRF Ingress Gateway.

Table 6-29 oc_ingressgateway_pod_resource_state

Field Details
Description

This metric pegs the congestion state per resource type which is calculated based on the resource usage and configured threshold.

The values of the metric is as follow:

  • 0: Normal
  • 1: DoC
  • 2: Congested

Note: Prometheus automatically injects pod name with label name "kubernetes_pod_name" to metric. This information is used for alert.

Type Gauge
Dimensions InstanceIdentifier, type

Possible values for type are CPU, MEMORY, PENDING_REQUEST.

Note: The type "MEMORY" is not used to determine the pod congestion state in NRF Ingress Gateway.

Table 6-30 oc_ingressgateway_incoming_pod_connections_rejected_total

Field Details
Description

This metric pegs the number of connections dropped at Congested or DoC state.

Note: Prometheus automatically injects pod name with label name "kubernetes_pod_name" to metric. This information is used for alert.

Type Counter
Dimensions InstanceIdentifier, Direction

Table 6-31 oc_ingressgateway_incoming_tls_connections

Field Details
Description Number of TLS connections received on the Ingress Gateway and their negotiated TLS versions. The versions can be TLSv1.3 or TLSv1.2.
Type Gauge
Dimensions NegotiatedTLSVersion, Host, Direction, InstanceIdentifier

Table 6-32 oc_ingressgateway_incoming_ip_type

Field Details
Description This is incremented when the IP type of the active incoming connections from the client to Ingress Gateway.
Type Gauge
Dimensions host, receivedAddressType

Table 6-33 oc_ingressgateway_outgoing_ip_type

Field Details
Description This is incremented when the IP type of the active outgoing connections from Ingress Gateway to the backend services.
Type Gauge
Dimensions BackendSvc, BackendSvcAddressType

Table 6-34 oc_ingressgateway_http_request_ratelimit_values_total

Field Details
Description

This metric tracks the total count of requests handled by the rate limiting filter, categorized by whether each request was allowed or denied.

If there was no route configuration for the dropped message, the id attribute is set to "NA".

Type Counter
Dimension Id, Allowed, RouteLevelColor

Table 6-35 oc_ingressgateway_http_request_ratelimit_reject_chain_duration_histogram_seconds

Field Details
Description Records the reject chain duration.
Type Histogram
Dimension NA

Table 6-36 oc_ingressgateway_http_request_ratelimit_reject_chain_length_histogram

Field Details
Description This metric records the number of consecutive requests rejected before a successful acceptance and adds it to the corresponding bucket. This metric provides the number of failed requests due to bursty traffic.
Type Histogram
Dimension NA

Table 6-37 oc_ingressgateway_http_request_ratelimit_denied_count_total

Field Details
Description Records the details of the denied request.

If there is no denied request action configuration, the ActionId attribute is set to "default".

Type Counter
Dimension Action, ActionId, CongestionLevel, Priority, ErrorProfile

Table 6-38 oc_ingressgateway_congestion_cpu_state

Field Details
Description Records the CPU levels of the congestion state.
Type Gauge
Dimension NA

Table 6-39 oc_ingressgateway_congestion_system_state

Field Details
Description Records the system level based on CPU.
Type Gauge
Dimension NA

Table 6-40 oc_ingressgateway_system_state_duration_percentage

Field Details
Description Records the percentage of time the system was in a particular congestion level.
Type Gauge
Dimension level

Table 6-41 oc_ingressgateway_congestion_level_total

Field Details
Description Counts the number of times a congestion level was identified. This congestion level value varies between 0-10.
Type Counter
Dimension NA

Table 6-42 oc_ingressgateway_congestion_level_bucket_total

Field Details
Description Identifies the number of times the congestion level was observed.

Note: This metric also records any increase in CPU, which sometimes is not recorded in the oc_ingressgateway_congestion_cpu_state metric. Refer to both the metrics to obtain the congestion level of the pod.

Type Histogram
Dimension NA

Table 6-43 oc_ingressgateway_congestion_cpu_percentage_bucket

Field Details
Description Records the CPU percentage.
Type Histogram
Dimension NA

Table 6-44 oc_ingressgateway_route_overloadcontrol_discard_total

Field Details
Description This metric is pegged when the incoming request is discarded by the Overload load filter on percentage basis.

Note: The LoadLevel label identifies the exact overload threshold at which each request is dropped.
Type Counter
Dimension DiscardAction, ErrorOriginator, InstanceIdentifier, LoadLevel, Method, Scheme, ServiceName, Status
6.1.1.2 Egress Gateway Metrics

Table 6-45 oc_egressgateway_msgcopy_requests_total

Field Details
Description This is incremented whenever request message is sent or acknowledged from Kafka.
Type Counter
Dimensions type

Table 6-46 oc_egressgateway_msgcopy_responses_total

Field Details
Description This is incremented whenever response message is sent or acknowledged from Kafka.
Type Counter
Dimensions type

Table 6-47 oc_egressgateway_dd_unreachable

Field Details
Description

This indicates whether DD (kafka) is reachable or not

0 - reachable, 1 - unreachable

Type Gauge
Dimensions NA

Table 6-48 oc_egressgateway_http_requests_total

Field Details
Description Metric to capture the request count reaches the Egress Gateway from the application microservice and pegs with Direction as egress. Also, when the request goes out of Egress Gateway and pegs with Direction as egressOut.
Type Counter
Dimensions Method, NFType, NFServiceType, Host, HttpVersion, Scheme, Proxy, InstanceIdentifier, Direction,DestinationHost

Table 6-49 oc_egressgateway_http_responses_total

Field Details
Description Metric to capture when Egress Gateway sends response back to backend NF microservice and pegs with Direction as egress. Also, when the response is received Egress gateway and pegs with Direction as egressOut
Type Counter
Dimensions Status, Method, NFType, NFServiceType, Host, HttpVersion, Scheme, InstanceIdentifier, Direction, BlacklistedFqdn, DestinationHost, ErrorOriginator, jetty_request_timeout, error-reason

Table 6-50 oc_egressgateway_connection_failure_total

Field Details
Description This metric will be pegged by jetty client when the destination is not reachable by Egress Gateway. Here, the destination is producer NF.
Type Counter
Dimensions Host, Port, InstanceIdentifier, Direction, error_reason, ErrorOriginator

Table 6-51 oc_egressgateway_request_processing_latency_seconds

Field Details
Description Metric captures the amount of time taken for processing the request only within Egress Gateway
Type Histogram
Dimensions quantile, InstanceIdentifier, Route_path, Method

Table 6-52 oc_egressgateway_request_latency_seconds

Field Details
Description This metric is pegged in the last custom filter of the Egress Gateway while the response is being sent back to the consumer NF. This metric tracks the amount of time taken for processing the request. It starts as soon the request reaches the first custom filter of the application and lasts till the response is sent back to the consumer NF from the last custom filter of the application.
Type Histogram
Dimensions quantile, InstanceIdentifier, Route_path, Method

Table 6-53 oc_egressgateway_request_content_metrics_total

Field Details
Description This metric is pegged by default filter RequestContentMetrics. It pegs whether request has request body or not.
Type Counter
Dimensions method, content_available, InstanceIdentifier

Table 6-54 oc_egressgateway_incoming_connections

Field Details
Description Gauge metric that will peg active incoming connections from client to Egress Gateway.
Type Gauge
Dimensions Direction, Host, InstanceIdentifier

Table 6-55 oc_egressgateway_outgoing_connections

Field Details
Description Gauge metric that will peg active outgoing connections from Egress Gateway to destination.
Type Gauge
Dimensions Direction, Host, InstanceIdentifier

Table 6-56 oc_egressgateway_server_latency_seconds

Field Details
Description This metric is pegged in Jetty response listener that captures the amount of time taken for processing of the request by jetty client
Type Histogram
Dimensions quantile, InstanceIdentifier, Host, Method

Table 6-57 oc_egressgateway_jetty_request_stat_metrics_total

Field Details
Description This metric is pegged for every outgoing request from Egress gateway to the backend at jetty level
Type Counter
Dimensions DestinationHost, InstanceIdentifier, event

Table 6-58 oc_egressgateway_jetty_response_stat_metrics_total

Field Details
Description This metric is pegged for every event occurred when a response is received by Egress Gateway.
Type Counter
Dimensions event, client_type, InstanceIdentifier, DestinationHost

Table 6-59 oc_egressgateway_sni_error_total

Field Details
Description Indicates the count of TLS connection failure due to SNI validation failure.
Type Counter
Dimensions error_reason, sni_status

Table 6-60 oc_egressgateway_peer_health_status

Field Details
Description It defines Egress Gateway peer health status.
  • This metric is set to 1, if a peer is unhealthy.
  • This metric is reset to 0, when it becomes healthy again.
  • This metric is set to -1, if peer is removed from peerconfiguration.
Type Gauge
Dimensions peer, vfqdn

Table 6-61 oc_egressgateway_peer_health_ping_request_total

Field Details
Description This metric is incremented every time a health ping is sent toward a peer.
Type Counter
Dimensions peer, vfqdn

Note: If virtual host is configured then vfqdn is pegged along with peer otherwise only peer will be pegged.

Table 6-62 oc_egressgateway_peer_health_ping_response_total

Field Details
Description This metric is incremented every time a health ping response is received from a peer irrespective of success or failure.
Type Counter
Dimensions peer, vfqdn, status, cause

Note: If virtual host is configured then vfqdn is pegged along with peer otherwise only peer will be pegged.

Table 6-63 oc_egressgateway_peer_health_status_transitions_total

Field Details
Description This metric is incremented every time a peer is transitioned from Available to Unavailable or from Unavailable to Available.
Type Counter
Dimensions peer, vfqdn, from, to

Table 6-64 oc_egressgateway_peer_count

Field Details
Description This metric is incremented every time for the peer count.
Type Gauge
Dimensions peerset

Table 6-65 oc_egressgateway_peer_available_count

Field Details
Description This metric is incremented every time for the available peer count.
Type Gauge
Dimensions peerset

Table 6-66 oc_egressgateway_outgoing_tls_connections

Field Details
Description Number of TLS connections received on the Egress Gateway and their negotiated TLS versions. The versions can be TLSv1.3 or TLSv1.2.
Type Gauge
Dimensions NegotiatedTLSVersion, Host, Direction, InstanceIdentifier

Table 6-67 oc_egressgateway_incoming_ip_type

Field Details
Description This is incremented when the IP type of the active incoming connections from the NRF microservices to the Egress Gateway.
Type Gauge
Dimensions host, receivedAddressType

Table 6-68 oc_egressgateway_outgoing_ip_type

Field Details
Description This is incremented when the IP type of the active outgoing connections from Egress Gateway to the destination.
Type Gauge
Dimensions destinationHost, destinationHostAddressType

Table 6-69 oc_egressgateway_dualstack_ip_rejected_total

Field Details
Description This is incremented by counting the total IP rejections which are caused by a IP mismatch between the IP type configured in the egressRoutingMode and the IP type returned by DNS resolution.
Type Gauge
Dimensions authority, egressRoutingMode, dnsResolvedType

Table 6-70 oc_egressgateway_podlevel_throttling_allowed_total

Field Details
Description

Indicates the total number of requests processed by Egress Gateway microservice when the Egress Gateway pod throttling feature is enabled.

Note: The metric will not be pegged if the Egress Gateway pod throttling feature is disabled.

Type Counter
Dimensions route_id
6.1.1.3 Common Gateway Metrics

Table 6-71 oc_configserver_reachability

Field Details
Description Gauge metric to peg the reachability of the configuration server
Type Gauge
Dimensions NA

Table 6-72 oc_configclient_request_total

Field Details
Description This metric is pegged whenever the configuration client is polling for configuration update from common configuration server.
Type Counter
Dimensions releaseVersion, configVersion

Table 6-73 oc_configclient_response_total

Field Details
Description This metrics is pegged whenever config client receives response from common configuration server.
Type Counter
Dimensions releaseVersion, configVersion, updated

Table 6-74 oc_oauth_nrf_request_total

Field Details
Description This metric is pegged in the OAuth client implementation if the request is sent to NRF for requesting the OAuth token. OAuth client implementation is used in Egress Gateway.
Type Counter
Dimensions ConsumerNFInstanceId, ConsumerNFType, TargetNFType, TargetNFInstanceId, scope, NrfFqdn

Table 6-75 oc_oauth_nrf_response_success_total

Field Details
Description This metric is pegged in the OAuth client implementation if an OAuth token is successfully received from the NRF. OAuth client implementation is used in Egress Gateway.
Type Counter
Dimensions ConsumerNFInstanceId, ConsumerNFType, TargetNFType, TargetNFInstanceId, scope, NrfFqdn,StatusCode

Table 6-76 oc_oauth_nrf_response_failure_total

Field Details
Description This metric is pegged in the OAuthClientFilter in Egress Gateway whenever GetAccessTokenFailedException is caught.
Type Counter
Dimensions ConsumerNFInstanceId, ConsumerNFType, TargetNFType, TargetNFInstanceId, scope, NrfFqdn, ErrorOriginator, StatusCode

Table 6-77 oc_oauth_request_failed_internal_total

Field Details
Description This metric is pegged in the OAuthClientFilter in Egress Gateway whenever InternalServerErrorException is caught.
Type Counter
Dimensions ConsumerNFInstanceId, ConsumerNFType, ErrorOriginator, NrfFqdn, StatusCode, TargetNFType, TargetNFInstanceId, scope

Table 6-78 oc_oauth_token_cache_total

Field Details
Description This metric is pegged in the OAuth Client Implementation if the OAuth token is found in the cache.
Type Counter
Dimensions ConsumerNFInstanceId, ConsumerNFType, TargetNFType, TargetNFInstanceId, scope, NrfFqdn

Table 6-79 oc_oauth_request_invalid_total

Field Details
Description This metric is pegged in the OAuthClientFilter in Egress Gateway whenever a BadAccessTokenRequestException/JsonProcessingException is caught.
Type Counter
Dimensions ConsumerNFInstanceId, ConsumerNFType, TargetNFType, TargetNFInstanceId, scope, StatusCode, ErrorOriginator, NrfFqdn

Table 6-80 security_cert_x509_expiration_seconds

Field Details
Description Indicates the time to certificate expiry in epoch seconds.
Type Histogram
Dimensions serialNumber

6.1.2 Configuring NRF Metrics Dashboard in OCI

This section describes the steps to upload the ocnrf_oci_metric_dashboard_25.1.200.json file on OCI Logging Analytics Dashboard. As OCI doesn't support Grafana, OCI uses the Logging Analytics Dashboard Service for visualizing the metrics and logs.

The steps are:
  1. Log in to OCI Console.

    Note:

    For more details about logging in to the OCI, refer to Signing In to the OCI Console.
  2. Open the navigation menu and click Observability & Management.
  3. Under Logging Analytics, click Dashboards. The Dashboards page appears.
  4. Choose the Compartment on the left pane.
  5. Click Import dashboards.
  6. User can select and upload the ocnrf_oci_metric_dashboard_25.1.200.json file. ##METRIC_NAMESPACE in json file must be customized to metrics namespace that the user provided while deploying OCI adaptor.
  7. Import dashboard page appears. Click Import button on the page.
  8. Click filter Filter option in the ocnrf_oci_metric_dashboard page and select the Compartment, Namespace, Log Group Compartment, and Region from the drop-down list.

    User can view the imported dashboard and can view the metrics in the dashboard.

    Figure 6-1 ocnrf_oci_metric_dashboard


    ocnrf_oci_metric_dashboard

For more details, see Oracle Communications Cloud Native Core, OCI Adaptor Deployment Guide.

6.1.3 NRF NF Metrics

This section provides details about the NRF metrics.

Table 6-81 ocnrf_nfRegister_rx_requests_total

Field Details
Description Number of Registration Requests received.
Type Counter
Dimensions NrfLevel, NfInstanceId, RequesterNfType, NfFqdn

Note: The NfFqdn dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-82 ocnrf_nfRegister_tx_responses_total

Field Details
Description Number of Registration Responses sent.
Type Counter
Dimensions NrfLevel, NfInstanceId, RequesterNfType, HttpStatusCode, NfFqdn

Note: The NfFqdn dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-83 ocnrf_nfRegister_rx_requests_success_perService_total

Field Details
Description Number of Registrations received and processed successfully per Service.
Type Counter
Dimensions NrfLevel, NfInstanceId, serviceName, serviceInstanceId, NfFqdn

Note: The NfFqdn dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Recommended legend to see dimension level data (as applicable) NfRegistrations Per Service [ serviceName :- {{ serviceName }}, nfInstanceId :- {{NfInstanceId}} ]

Table 6-84 ocnrf_nfUpdate_rx_requests_total

Field Details
Description Number of Update Requests received.
Type Counter
Dimensions NrfLevel, NfInstanceId, RequesterNfType, Updatetype (Partial/Complete), NfFqdn

Note: The NfFqdn dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-85 ocnrf_nfUpdate_tx_responses_total

Field Details
Description Number of Update Responses sent.
Type Counter
Dimensions NrfLevel, NfInstanceId, RequesterNfType, Updatetype (Partial/Complete), HttpStatusCode, NfFqdn

Note: The NfFqdn dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-86 ocnrf_nfUpdate_rx_requests_success_perService_total

Field Details
Description Number of NfUpdates received and processed successfully per Service.
Type Counter
Dimensions NrfLevel, Updatetype (Partial/Complete), NfInstanceId, ServiceName, ServiceInstanceId, NfFqdn

Note: The NfFqdn dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Recommended legend to see dimension level data (as applicable) NFUpdates Per Service [serviceName :- {{ serviceName }}, serviceInstanceId:- {{ServiceInstanceId}}]

Table 6-87 ocnrf_nfHeartbeat_rx_requests_total

Field Details
Description Number of Heartbeat Requests received.
Type Counter
Dimensions NrfLevel, NfInstanceId, RequesterNfType, NfFqdn

Note: The NfFqdn dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-88 ocnrf_nfHeartBeat_tx_responses_total

Field Details
Description Number of Heartbeat Responses sent
Type Counter
Dimensions Nrflevel, NfInstanceId, RequesterNfType, HttpStatusCode, NfFqdn

Note: The NfFqdn dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-89 ocnrf_nfDeregister_rx_requests_total

Field Details
Description Number of deregistration requests received.
Type Counter
Dimensions NrfLevel, NfInstanceId, RequesterNfType, NfFqdn

Note: The NfFqdn dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-90 ocnrf_nfDeregister_tx_responses_total

Field Details
Description Number of deregistration responses sent.
Type Counter
Dimensions NrfLevel, NfInstanceId, RequesterNfType, HttpStatusCode, NfFqdn

Note: The NfFqdn dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-91 ocnrf_nfDeregister_rx_requests_success_perService_total

Field Details
Description Number of deregistration requests received and process successfully per service.
Type Counter
Dimensions NrfLevel, serviceName, serviceInstanceId, NfInstanceId, NfFqdn

Note: The NfFqdn dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Recommended legend to see dimension level data (as applicable) NFDeregistration Per Service [ serviceName :- {{ serviceName }}, serviceInstanceId:- {{ServiceInstanceId}} ]

Table 6-92 ocnrf_nfListRetrieval_rx_requests_total

Field Details
Description Number of NFListRetrieval requests received.
Type Counter
Dimensions NrfLevel, RequesterNfType, NfFqdn

Note: The NfFqdn dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-93 ocnrf_nfListRetrieval_tx_responses_total

Field Details
Description Number of NFListRetrieval responses sent.
Type Counter
Dimensions NrfLevel, RequesterNfType, HttpStatusCode, NfFqdn

Note: The NfFqdn dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-94 ocnrf_nfProfileRetrieval_rx_requests_total

Field Details
Description Number of NFProfileRetrieval requests received.
Type Counter
Dimensions NrfLevel, NfInstanceId, NfFqdn

Note: The NfFqdn dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-95 ocnrf_nfProfileRetrieval_tx_responses_total

Field Details
Description Number of NFProfileRetrieval responses sent.
Type Counter
Dimensions NrfLevel, NfInstanceId, HttpStatusCode, NfFqdn

Note: The NfFqdn dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-96 ocnrf_heartbeat_missed_total

Field Details
Description Number of heartbeats missed.
Type Counter
Dimensions NrfLevel, NfType, NfInstanceId, NfFqdn

Note: The NfFqdn dimension contain the FQDN as present in the NfProfile.

Table 6-97 ocnrf_nfStatusSubscribe_rx_requests_total

Field Details
Description Number of NStatusSubscribe requests received.
Type Counter
Dimensions NrfLevel, RequesterNfType, OperationType, NfFqdn

Note: The NfFqdn dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-98 ocnrf_nfStatusSubscribe_tx_responses_total

Field Details
Description Number of NfStatusSubscribe responses sent.

In case of subscription limit feature, NRF includes and populates new measurements for number of new subscription requests or subscription renewal rejected (due to limit being exceeded) per second.

Type Counter
Dimensions NrfLevel, RequesterNfType, HttpStatusCode, OperationType, NfFqdn, RejectionReason

Note: The NfFqdn dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-99 ocnrf_nfset_active_subscriptions

Field Details
Description

Number of global subscription count status.

For georedundancy, it reflects the total subscriptions in quad or triplet set.

Type Gauge
Dimensions NrfLevel

Table 6-100 ocnrf_nfset_limit_level

Field Details
Description Indicates the global subscription limit threshold level.
Type Gauge
Dimensions NrfLevel

Table 6-101 ocnrf_subscription_migration_status

Field Details
Description Indicates the status of the migration of records in the NfSubscriptions table.

Value 1 indicates that the migration is in Progress.

Value 0 indicates the migration is Complete.

Type Gauge
Dimensions subscriptionLimitFeatureStatus

Table 6-102 ocnrf_nfStatusUnsubscribe_rx_requests_total

Field Details
Description Number of NfStatusUnsubscribe requests received.
Type Counter
Dimensions NrfLevel, RequesterNfType, NfFqdn

Note: The NfFqdn dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-103 ocnrf_nfStatusUnsubscribe_tx_responses_total

Field Details
Description Number of NfStatusUnsubscribe responses sent.
Type Counter
Dimensions NrfLevel, RequesterNfType, HttpStatusCode, NfFqdn

Note: The NfFqdn dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-104 ocnrf_nfStatusNotify_tx_requests_total

Field Details
Description Number of NfStatusNotify requests sent.
Type Counter
Dimensions NrfLevel, NotificationEventType, TargetNfType, NfFqdn

Note: The NfFqdn dimension contains the FQDN as present in the NfProfile.

Table 6-105 ocnrf_nfStatusNotify_rx_responses_total

Field Details
Description Number of NfStatusNotify responses received.
Type Counter
Dimensions NrfLevel, NotificationEventType, NotificationHostPort, NumberOfRetriesAttempted, TargetNfType, HttpStatusCode, NfFqdn

Note: The NfFqdn dimension contains the FQDN as present in the NfProfile.

Table 6-106 ocnrf_nfStatusNotify_requests_failed_total

Field Details
Description Number of NfStatusNotify requests failed to sent out.
Type Counter
Dimensions NrfLevel, NotificationEventType, TargetNfType, NfFqdn

Note: The NfFqdn dimension contains the FQDN as present in the NfProfile.

Table 6-107 ocnrf_nfDiscover_rx_requests_total

Field Details
Description Number of NfDiscover Requests received.
Type Counter
Dimensions NrfLevel, TargetNfType, RequesterNfType, NfFqdn

Note: The NfFqdn dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Recommended legend to see dimension level data (as applicable) NfDiscover Req [ TargetNf :- {{ TargetNfType }}, RequesterNfType :- {{RequesterNfType}} ]

Table 6-108 ocnrf_nfDiscover_tx_responses_total

Field Details
Description Number of NfDiscover responses sent.
Type Counter
Dimensions NrfLevel, TargetNfType, RequesterNfType, HttpStatusCode, NfFqdn

Note: The NfFqdn dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-109 ocnrf_nfDiscover_rx_requests_success_perService_total

Field Details
Description Number of NfDiscover requests received and processed successfully per Service.
Type Counter
Dimensions NrfLevel, RequesterNfType, serviceName, NfFqdn

Note: The NfFqdn dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Recommended legend to see dimension level data (as applicable) NFDiscover Per Service [ serviceName :- {{ serviceName }} ]

Table 6-110 ocnrf_nfDiscover_profiles_discovered_total

Field Details
Description Number of Profiles returned in discovery response. Depending on bucket size and corresponding value will tell how many profiles are returned in discovery response.
Type Counter
Dimensions NrfLevel, TargetNfType, Bucket, NfFqdn

Note: The NfFqdn dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Recommended legend to see dimension level data (as applicable) Discovered profiles [ TargetNfType :- {{TargetNfType}}, Bucket :- {{ Bucket }} ]

Table 6-111 ocnrf_active_registrations_count

Field Details
Description Number of active NFs that are registered at the local site at any point of time.
Type Counter
Dimensions RequesterNfType, NrfLevel
Recommended legend to see dimension level data (as applicable) Active Registrations [ NfType-{{ NfType }}, NrfLevel-{{ NrfLevel }} ]

Table 6-112 ocnrf_message_processing_time_seconds

Field Details
Description Time taken by NRF specific microservice to process the service operation (NfRegister/NfUpdate-Partial/NfUpdate-Complete/NfDeregister/NfProfileRetrieval/NfListRetrieval/NfHeartBeat/NfDiscover/NFStatusSubscribe/NFStatusUnSubscribe/NfAccessToken) Note: Latency calculated by this metric does not include time taken by NRF API gateway.
Type Histogram
Dimensions NrfLevel, NfFqdn, RequesterNfType, ServiceOperation

Note: The NfFqdnss dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Recommended legend to see dimension level data (as applicable) Avg NRF Latency {{ ServiceOperation }} {{ RequesterNfType }}

Table 6-113 ocnrf_dbmetrics_total

Field Details
Description Database operation count corresponding to every service operation.
Type Counter
Dimensions method, dbOperation, NrfLevel, HttpStatusCode

Table 6-114 ocnrf_dbmetrics_round_trip_time_seconds

Field Details
Description

Time (in microseconds) taken by database operation corresponding to every service operation

(NfRegister/NfUpdate/NfDeregister/NfProfileRetrieval/NfListRetrieval/NfHeartBeat/NfDiscover/NfSubscribe/NfUnsubscribe/NfStatusNotify/NfAccessToken/NrfConfiguration/InternalConfigurationCache)

Type Histogram
Dimensions method, dbOperation, serviceOperation, tableName: (NRF Table Names), NrfLevel, HttpStatusCode

Table 6-115 ocnrf_nf_suspended_total

Field Details
Description The number of profiles that have been marked as SUSPENDED when a profile has missed nfHeartBeatMissAllowed.
Type Counter
Dimensions NrfLevel, NfInstanceId,NfStatus, HeartbeatTimer, NfFqdn

Note: The NfFqdn dimension contains the FQDN as present in the NfProfile.

Table 6-116 ocnrf_nfSubscriptions_expired_total

Field Details
Description The number of NfSubscriptions whose validityTime has expired.
Type Counter
Dimensions NrfLevel

Table 6-117 ocnrf_nfDiscover_emptyList_total

Field Details
Description

This metric is pegged:

  • When feature flag is DISABLED and discovery request processing resulted in EMPTY LIST.
  • When feature flag is ENABLED and discovery request processing resulted in all matching NFs in SUSPENDED state.
Type Counter
Dimensions NfType, FeatureStatus

Table 6-118 ocnrf_operational_state

Field Details
Description This metric is pegged when the operational state of NRF switches between NORMAL and COMPLETE_SHUTDOWN.
  • 0 - Indicates the operational state is NORMAL.
  • 1 - Indicates the operational state is COMPLETE_SHUTDOWN.
The metric is pegged in the NrfAuditor service, if any one of the NrfAuditor pod shows the operational state as COMPLETE_SHUTDOWN, then the state is considered as COMPLETE_SHUTDOWN.
Type Gauge
Dimensions NrfLevel

Table 6-119 ocnrf_audit_status

Field Details
Description This metric indicates whether the NRF Audit is in-progress or in paused state. The status of the audit procedures at .
  • 0 - Indicates the NRF audit is in-progress.
  • 1 - Indicates the NRF audit is paused.
The metric is pegged in the NrfAuditor service, if any one of the NrfAuditor pod shows the operational state as COMPLETE_SHUTDOWN, then the state is considered as COMPLETE_SHUTDOWN.

Note: NrfAuditor will continue to remain in the paused state for some time, even after OcnrfOperationalStateCompleteShutdown alarm is cleared. For more information, see "From CONTROLLED_SHUTDOWN to NORMAL" in Controlled Shutdown of NRF section.

Type Gauge
Dimensions NrfLevel

Table 6-120 ocnrf_nfDiscover_limiting_profile_count_for_nfSet_total

Field Details
Description This metric will be pegged when the "Limiting the Number of Producers Based on NF Set Ids and Extended Preferred Locality" features are enabled and the number of NF profiles sent in the discovery response is less than the profileCountInDiscoveryResponse configuration.
Type Counter
Dimensions TargetNfType, RequesterNfType, NrfLevel

Table 6-121 ocnrf_nfDiscover_limiting_profiles_not_applied_for_nfSet_total

Field Details
Description This metric will be pegged when "Limiting the Number of Producers Based on NF Set Ids" feature could not be applied due to the unavailability of nfSetIdList in any one of the NF profiles selected with the first matching location(s) from targetPreferredLocations configuration in extendedPreferredLocality.
Type Counter
Dimensions TargetNfType, RequesterNfType, NrfLevel

Table 6-122 ocnrf_nfDiscover_tx_response_size_bytes

Field Details
Description

The size of the NfDiscover response.

The size is pegged in bytes and is published in buckets of 1KB, 3KB, 7KB, 10KB, 15KB, 20KB, 30KB, 40KB, 50KB, 60KB, 70KB, and 80KB.

Type Histogram
Dimensions TargetNfType

Table 6-123 ocnrf_nf_profile_size

Field Details
Description

The size of the registered NfProfiles.

Note:The size of the metric is calculated as per the payload received during registration or update of the profile. To calculate the size of the payload, save the payload in a text file without spaces, and verify the size of the file using Linux tools like wc.

Type Gauge
Dimensions NfInstanceId, NfType

Table 6-124 ocnrf_nfProfile_size_limit_breached

Field Details
Description

Indicates the number of NF profiles that get rejected due to profile size limit during registration or update service operations.

Type Counter
Dimensions NfInstanceId, NfType, ServiceOperation

6.1.4 NF Screening Metrics

This section provides details about the NF screening metrics.

Table 6-125 ocnrf_nfScreening_nfFqdn_requestFailed_total

Field Details
Description The total number of requests for which screening failed against NF FQDN screening list.
Type Counter
Service Operation NFRegister, NFUpdate
Dimensions NrfLevel, RequesterNfType, NfFqdn

Note: The NfFqdn dimension contains the FQDN as present in the NfProfile.

Table 6-126 ocnrf_nfScreening_nfFqdn_requestRejected_total

Field Details
Description The total number of requests rejected for which screening failed against NF FQDN screening list.
Type Counter
Service Operation NFRegister, NFUpdate
Dimensions NrfLevel, RequesterNfType, NfFqdn

Note: The NfFqdn dimension contains the FQDN as present in the NfProfile.

Table 6-127 ocnrf_nfScreening_nfIpEndPoint_requestFailed_total

Field Details
Description The total number of requests for which screening failed against NF IP endpoint screening list.
Type Counter
Service Operation NFRegister, NFUpdate
Dimensions NrfLevel, RequesterNfType, NfFqdn

Table 6-128 ocnrf_nfScreening_nfIpEndPoint_requestRejected_total

Field Details
Description The total number of requests rejected because screening failed against NF IP endpoint screening list.
Type Counter
Service Operation NFRegister, NFUpdate
Dimensions NrfLevel, RequesterNfType, NfFqdn

Note: The NfFqdn dimension contains the FQDN as present in the NfProfile.

Table 6-129 ocnrf_nfScreening_callbackUri_requestFailed_total

Field Details
Description The total number of requests for which screening failed against Callback URI screening list.
Type Counter
Service Operation NFRegister, NFUpdate, NFStatusSubscribe
Dimensions NrfLevel, RequesterNfType, NfFqdn

Note: The NfFqdn dimension contains the FQDN as present in the NfProfile.

Table 6-130 ocnrf_nfScreening_callbackUri_requestRejected_total

Field Details
Description The total number of requests rejected because screening failed against Callback URI screening list.
Type Counter
Service Operation NFRegister, NFUpdate, NFStatusSubscribe
Dimensions NrfLevel, RequesterNfType, NfFqdn

Note: The NfFqdn dimension contains the FQDN as present in the NfProfile.

Table 6-131 ocnrf_nfScreening_plmnId_requestFailed_total

Field Details
Description The total number of requests for which screening failed against PLMN id screening list.
Type Counter
Service Operation NFRegister, NFUpdate
Dimensions NrfLevel, RequesterNfType, NfFqdn

Note: The NfFqdn dimension contains the FQDN as present in the NfProfile.

Table 6-132 ocnrf_nfScreening_nfFqdn_requestRejected_total

Field Details
Description The total number of requests rejected because screening failed against PLMN id screening list.
Type Counter
Service Operation NFRegister, NFUpdate
Dimensions NrfLevel, RequesterNfType, NfFqdn

Note: The NfFqdn dimension contains the FQDN as present in the NfProfile.

Table 6-133 ocnrf_nfScreening_nfTypeRegister_requestFailed_total

Field Details
Description The total number of NFRegister requests rejected as NF type was not allowed to register with NRF.
Type Counter
Service Operation NFRegister
Dimensions NrfLevel, RequesterNfType, NfFqdn

Note: The NfFqdn dimension contains the FQDN as present in the NfProfile.

Table 6-134 ocnrf_nfScreening_nfTypeRegister_requestRejected_total

Field Details
Description The total number of NFRegister requests for which screening failed against NF type screening list.
Type Counter
Service Operation NFRegister
Dimensions NrfLevel, RequesterNfType, NfFqdn

Note: The NfFqdn dimension contains the FQDN as present in the NfProfile.

Table 6-135 ocnrf_nfScreening_notApplied_InternalError_total

Field Details
Description The total number of times screening not applied due to internal error.
Type Counter
Service Operation NFRegister, NFUpdate, NFStatusSubscribe
Dimensions NrfLevel, RequesterNfType, NfFqdn

Note: The NfFqdn dimension contains the FQDN as present in the NfProfile.

6.1.5 NF Access token Metrics

This section provides details about the NF access token metrics.

Table 6-136 ocnrf_accessToken_rx_requests_total

Field Details
Description The total number of access token requests received.
Type Counter
Service Operation AccessToken
Dimensions TargetNfType, ClientNfType, TargetNfInstanceId, ClientNfInstanceId, ServiceName, NrfLevel, NfFqdn

Note: The NfFQDN dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-137 ocnrf_accessToken_tx_responses_total

Field Details
Description The total number of access token responses sent.
Type Counter
Service Operation AccessToken
Dimensions

TargetNfType, RequesterNfType, TargetNfInstanceId, ClientNfInstanceId, Scope, NrfLevel, HttpStatusCode, NfFqdn, KeyId, RejectionReason

Note: The NfFQDN dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

6.1.6 NRF Configuration Metrics

This section provides details about the NRF configuration metrics.

Table 6-138 ocnrf_oauth_keyData_healthStatus

Field Details
Description Oauth Token Signing keys health status

Value 0 - Healthy

Value 1 - Unhealthy

Type Gauge
Service Operation Configuration
Dimensions KeyId, KeyType, isCurrentKeyId, NrfLevel

Table 6-139 ocnrf_oauth_currentKeyId_configuredStatus

Field Details
Description Oauth Current Key Id Configuration Status

Value 0 - Healthy

Value 1 - Unhealthy

Type Gauge
Service Operation Configuration
Dimensions NrfLevel

Table 6-140 ocnrf_oauth_keyData_expiryStatus

Field Details
Description

Oauth Token Signing keys Expiry Status

(Value is expiry time in epoch time)

Type Gauge
Service Operation Configuration
Dimensions KeyId, isCurrentKeyId, NrfLevel

6.1.7 NRF SLF Metrics

This section provides details about the NRF SLF metrics.

Table 6-141 ocnrf_nfDiscover_forSLF_rx_requests_total

Field Details
Description The total number of NF Discover request received for SLF.
Type Counter
Service Operation NFDiscover
Dimensions TargetNfType, NrfLevel, NfFqdn

Note: The NfFQDN dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-142 ocnrf_nfDiscover_forSLF_tx_responses_total

Field Details
Metric Name ocnrf_nfDiscover_forSLF_tx_responses_total
Description The total number of NF Discover responses sent for SLF.
Type Counter
Service Operation NFDiscover
Dimensions TargetNfType, NrfLevel, HttpStatusCode, ResponseReason, NfFqdn

Note: The NfFQDN dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-143 ocnrf_SLF_tx_requests_total

Field Details
Description The total number of SLF query request sent.
Type Counter
Service Operation NFDiscover
Dimensions TargetNfType, NrfLevel, SubscriptionIdType, NfFqdn, slfFqdn

Note: The NfFQDN dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-144 ocnrf_SLF_rx_responses_total

Field Details
Description The total number of SLF query response received.
Type Counter
Service Operation NFDiscover
Dimensions TargetNfType, NrfLevel, SubscriptionIdType, HttpStatusCode, GroupId, NfFqdn, slfFqdn

Note: The NfFQDN dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-145 ocnrf_nfDiscover_SLFlookup_skipped_total

Field Details
Description The total number of NF Discover requests received for SLF but SLF lookup is skipped.
Type Counter
Service Operation NFDiscover
Dimensions TargetNfType, NrfLevel, NfFqdn, SkipSLFLookupParameter, SkipSLFLookupValue
Note:
  • The NfFQDN dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.
  • If the value of enableValueBasedSkipSLFLookup is set as false, the value of SkipSLFLookupValue dimension is set as NotApplicable.

Table 6-146 ocnrf_nfDiscover_continue_mandatoryAttributes_missing_total

Field Details
Description The total number of NF Discover requests processed while SLF is enabled but SLF mandatory attributes are missing in Search query.
Type Counter
Service Operation NFDiscover
Dimensions TargetNfType, NrfLevel, NfFqdn, ExceptionAttribute

Note: The NfFQDN dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-147 ocnrf_max_slf_attempts_exhausted_total

Field Details
Description The maximum number of SLF attempts to the hosts present in the SLF configuration.
This metric is pegged when either of the following reasons:
  • when maxslfattempts is configured to a value > 0 and the maxslfattempts is exhausted.
  • when maxslfattempts is configured to a value =0, and the number of SLF attempts have exceeded maximumHopCount.
  • when the available SLF hosts are exhausted.
Type Counter
Service Operation NFDiscover
Dimensions TargetNfType, NfFqdn

Note: The NfFQDN dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-148 ocnrf_slf_jetty_latency_seconds

Field Details
Description Time (in microseconds) after sending query to SLF and getting response from SLF.
Type Histogram
Service Operation NFDiscover
Dimensions Host, InstanceIdentifier, Method, NrfLevel, ServiceOperation

Table 6-149 ocnrf_SLF_reroutes_total

Field Details
Description The total number of SLF query which is rerouted to alternate SLFs.
Type Counter
Service Operation NFDiscover
Dimensions RequesterNfType, TargetNfType, TargetSLFFqdn, and PreviousSLFFqdn

6.1.8 NRF Forwarding Metrics

This section provides details about the NRF forwarding metrics.

Table 6-150 ocnrf_forward_accessToken_tx_requests_total

Field Details
Description The total number of Access Token Request forwarded to Primary or Secondary NRF.
Type Counter
Service Operation AccessToken
Dimensions TargetNfType, RequesterNfType, TargetNfInstanceId, ClientNfInstanceId, Scope, NrfLevel, NfFqdn

Note: The NfFQDN dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-151 ocnrf_forward_accessToken_rx_responses_total

Field Details
Description The total number of Access Token Responses for request forwarded to Primary/Secondary NRF
Type Counter
Service Operation AccessToken
Dimensions TargetNfType,RequesterNfType, TargetNfInstanceId, ClientNfInstanceId, Scope, NrfLevel, HttpStatusCode, RejectionReason, NfFqdn

Note:

The NfFqdn dimension indicates the FQDN of the consumer NF. This dimension will contain the FQDN if the service mesh sends the FQDN of the consumer NF in the XFCC header, else the dimension contains the value as UNKNOWN.
Rejection reason with meaning
  • InternalError: Request not forwarded because failure occurred at NRF due to internal error.
  • NRFCommunicationFailure: Request not forwarded because NRF is not able to connect with another NRF.
  • ErrorFromNRF: Error response received from another NRF.
  • NRFForwardingConfigurationMissing: Request not forwarded due to missing forwarding configuration.
  • LoopDetected: Received request message is already processed by NRF during forwarding mechanism.
  • *NotApplicable is applicable for 2xx Status code

Table 6-152 ocnrf_forward_nfProfileRetrieval_tx_requests_total

Field Details
Description The total number of Profile Retrieval Request forwarded to Primary/Secondary NRF.
Type Counter
Service Operation NFProfileRetrieval
Dimensions NrfLevel, NfInstanceId, NfFqdn

Note: The NfFQDN dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-153 ocnrf_forward_nfProfileRetrieval_rx_responses_total

Field Details
Description The total number of Profile Retrieval Responses for Request forwarded to Primary/Secondary NRF.
Type Counter
Service Operation NFProfileRetrieval
Dimensions NrfLevel, NfInstanceId, HttpStatusCode, RejectionReason, NfFqdn

Note: The NfFQDN dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-154 ocnrf_forward_nfStatusSubscribe_tx_requests_total

Field Details
Description The total number of Status Subscribe Request forwarded to Primary/Secondary NRF.
Type Counter
Service Operation NFStatusSubscribe, NFStatusUnsubscribe
Dimensions NrfLevel, RequesterNfType, OperationType, NfFqdn

Note: The NfFQDN dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-155 ocnrf_forward_nfStatusSubscribe_rx_responses_total

Field Details
Description The total number of Responses for Status Subscribe Request forwarded to Primary/Secondary NRF.
Type Counter
Service Operation NFStatusSubscribe, NFStatusUnsubscribe
Dimensions NrfLevel, RequesterNfType, HttpStatusCode, OperationType, RejectionReason, NfFqdn

Note: The NfFQDN dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-156 ocnrf_forward_nfDiscover_tx_requests_total

Field Details
Description The total number of NF Discovery Request forwarded to Primary/Secondary NRF.
Type Counter
Service Operation NFDiscover
Dimensions NrfLevel, TargetNfType, RequesterNfType, NfFqdn

Note: The NfFQDN dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-157 ocnrf_forward_nfDiscover_rx_responses_total

Field Details
Description The total number of Responses for NF Discovery Request forwarded to Primary/Secondary NRF.
Type Counter
Service Operation NFDiscover
Dimensions NrfLevel, TargetNfType, RequesterNfType, HttpStatusCode, RejectionReason, NfFqdn

Note: The NfFQDN dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-158 ocnrf_forward_round_trip_time_seconds

Field Details
Description Time taken by NRF specific microservice to forward the message to other Primary or Secondary NRF with the service operation: NFProfileRetrieval/NFStatusSubscribe/NfStatusUnsubscribe/AccessToken
Type Histogram
Service Operation NFStatusSubscribe, NFStatusUnsubscribe, NFProfileRetrieval, AccessToken
Dimensions NrfLevel, RequesterNfType, serviceOperation, NfFqdn

Note: The NfFQDN dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-159 ocnrf_forward_nfDiscover_barred_total

Field Details
Description The total number of discovery requests barred from getting forwarded to another NRF.
Type Counter
Service Operation NFDiscover
Dimensions NrfLevel, TargetNfType, RequesterNfType, NfFqdn, ForwardingBarringReason

Note: The NfFQDN dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-160 ocnrf_forward_accessToken_barred_total

Field Details
Description The total number of access token requests barred from getting forwarded to another NRF.
Type Counter
Service Operation AccessToken
Dimensions TargetNfType, RequesterNfType, TargetNfInstanceId, ClientNfInstanceId, Scope, NrfLevel, NfFqdn, ForwardingBarringReason

Note: The NfFQDN dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-161 ocnrf_forward_nfStatusSubscribe_barred_total

Field Details
Description The total number of status subscribe requests barred from getting forwarded to another NRF.
Type Counter
Service Operation NFStatusSubscribe, NFStatusUnsubscribe
Dimensions NrfLevel, RequesterNfType, OperationType, NfFqdn

Note: The NfFQDN dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-162 ocnrf_forward_profileRetrieval_barred_total

Field Details
Description The total number of profile retrieval requests barred from getting forwarded to another NRF.
Type Counter
Service Operation NFProfileRetrieval
Dimensions NrfLevel, NfInstanceId, NfFqdn

Note: The NfFQDN dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-163 ocnrf_forward_jetty_latency_seconds

Field Details
Description Time (in microseconds) after sending query to SLF and getting response from SLF.
Type Histogram
Service Operation NFDiscover
Dimensions Host, InstanceIdentifier, Method, NrfLevel, ServiceOperation

6.1.9 Roaming Support Metrics

This section provides details about the NRF roaming metrics.

Table 6-164 ocnrf_roaming_nfStatusSubscribe_rx_requests_total

Field Details
Description Number of inter-PLMN subscription creation requests received by NRF from NF Consumers (in case of vNRF) and hSEPP (in case of hNRF).
Type Counter
Service Operation NFStatusSubscribe
Dimensions NrfLevel, RequesterPLMNId, TargetPLMNId, NfFqdn, NRFRole, OperationType

Note: The NfFQDN dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-165 ocnrf_roaming_nfStatusSubscribe_tx_responses_total

Field Details
Description Number of inter-PLMN subscription creation responses sent by NRF.
Type Counter
Service Operation NFStatusSubscribe
Dimensions NrfLevel, RequesterPLMNId, TargetPLMNId, NfFqdn, NRFRole, OperationType, HttpStatusCode, RejectionReason

Note: The NfFQDN dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-166 ocnrf_roaming_nfStatusSubscribe_tx_requests_total

Field Details
Description Number of inter-PLMN subscription creation requests sent by vNRF towards hNRF.
Type Counter
Service Operation NFStatusSubscribe
Dimensions NrfLevel, RequesterPLMNId, TargetPLMNId, NfFqdn, OperationType

Note: The NfFQDN dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-167 ocnrf_roaming_nfStatusSubscribe_rx_responses_total

Field Details
Description Number of inter-PLMN subscription creation response received by vNRF from hNRF for routed or forwarded requests.
Type Counter
Service Operation NFStatusSubscribe
Dimensions NrfLevel, RequesterPLMNId, TargetPLMNId, NfFqdn, OperationType, HttpStatusCode, FailureReason

Note: The NfFQDN dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-168 ocnrf_roaming_nfStatusSubscribe_rx_requests_total

Field Details
Description Number of inter-PLMN subscription update requests received by NRF from NF Consumers (in case of vNRF) and hSEPP (in case of hNRF).
Type Counter
Service Operation NFStatusSubscribe - Update
Dimensions NrfLevel, NfFqdn, NRFRole, OperationType

Note: The NfFQDN dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-169 ocnrf_roaming_nfStatusSubscribe_tx_responses_total

Field Details
Description Number of inter-PLMN subscription update responses sent by NRF.
Type Counter
Service Operation NFStatusSubscribe - Update
Dimensions NrfLevel, NfFqdn, NRFRole, OperationType, HttpStatusCode, RejectionReason

Note: The NfFQDN dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-170 ocnrf_roaming_nfStatusSubscribe_tx_requests_total

Field Details
Description Number of inter-PLMN subscription update requests routed or forwarded by vNRF towards hNRF.
Type Counter
Service Operation NFStatusSubscribe - Update
Dimensions NrfLevel, NfFqdn, OperationType

Note: The NfFQDN dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-171 ocnrf_roaming_nfStatusSubscribe_rx_responses_total

Field Details
Description Number of inter-PLMN subscription update response received by vNRF from hNRF for routed/forwarded requests.
Type Counter
Service Operation NFStatusSubscribe - Update
Dimensions NrfLevel, NfFqdn, OperationType, HttpStatusCode, FailureReason

Note: The NfFQDN dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-172 ocnrf_roaming_nfStatusUnSubscribe_rx_requests_total

Field Details
Description Number of inter-PLMN subscription unsubscribe requests received by NRF from NF Consumers (in case of vNRF) and hSEPP (in case of hNRF).
Type Counter
Service Operation NFStatusUnSubscribe
Dimensions NrfLevel, NfFqdn, NRFRole

Note: The NfFQDN dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-173 ocnrf_roaming_nfStatusUnSubscribe_tx_responses_total

Field Details
Description Number of inter-PLMN subscription unsubscribe responses sent by NRF.
Type Counter
Service Operation NF Status UnSubscribe
Dimensions NrfLevel, NfFqdn, NRFRole, HttpStatusCode, RejectionReason

Note: The NfFQDN dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-174 ocnrf_roaming_nfStatusUnSubscribe_tx_requests_total

Field Details
Description Number of inter-PLMN subscription unsubscribe requests routed or forwarded by vNRF towards hNRF.
Type Counter
Service Operation NFStatusUnSubscribe
Dimensions NrfLevel, NfFqdn

Note: The NfFQDN dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-175 ocnrf_roaming_nfStatusUnSubscribe_rx_responses_total

Field Details
Description Number of inter-PLMN subscription unsubscribe response received by vNRF from hNRF for routed or forwarded requests.
Type Counter
Service Operation NFStatusUnSubscribe
Dimensions NrfLevel, NfFqdn, HttpStatusCode, FailureReason

Note: The NfFQDN dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-176 ocnrf_roaming_nfDiscover_rx_requests_total

Field Details
Description Number of inter-PLMN NFDiscover requests received by NRF from NF Consumers (in case of vNRF) and hSEPP (in case of hNRF).
Type Counter
Service Operation NFDiscover
Dimensions NrfLevel, RequesterPLMNId, TargetPLMNId, NfFqdn, NRFRole

Note: The NfFQDN dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-177 ocnrf_roaming_nfDiscover_tx_responses_total

Field Details
Description Number of inter-PLMN NFDiscover response sent by NRF.
Type Counter
Service Operation NFDiscover
Dimensions NrfLevel, RequesterPLMNId, TargetPLMNId, NfFqdn, NRFRole, HttpStatusCode, RejectionReason

Note: The NfFQDN dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-178 ocnrf_roaming_nfDiscover_tx_requests_total

Field Details
Description Number of inter-PLMN NF Discover request routed or forwarded by vNRF towards hNRF
Type Counter
Service Operation NFDiscover
Dimensions NrfLevel, RequesterPLMNId, TargetPLMNId, NfFqdn

Note: The NfFQDN dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-179 ocnrf_roaming_nfDiscover_rx_responses_total

Field Details
Description Number of inter-PLMN NFDiscover response received by vNRF from hNRF for routed or forwarded requests.
Type Counter
Service Operation NFDiscover
Dimensions NrfLevel, RequesterPLMNId, TargetPLMNId, NfFqdn, HttpStatusCode, FailureReason

Note: The NfFQDN dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-180 ocnrf_roaming_accessToken_rx_requests_total

Field Details
Description Number of inter-PLMN Access Token requests received by NRF from NF Consumers (in case of vNRF) and hSEPP (in case of hNRF).
Type Counter
Service Operation AccessToken
Dimensions NrfLevel, RequesterPLMNId, TargetPLMNId, NfFqdn, NRFRole

Note: The NfFQDN dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-181 ocnrf_roaming_accessToken_tx_responses_total

Field Details
Description Number of inter-PLMN Access Token response sent by NRF
Type Counter
Service Operation AccessToken
Dimensions NrfLevel, RequesterPLMNId, TargetPLMNId, NfFqdn, NRFRole, HttpStatusCode, RejectionReason

Note: The NfFQDN dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-182 ocnrf_roaming_accessToken_tx_requests_total

Field Details
Description Number of inter-PLMN Access Token request routed or forwarded by vNRF towards hNRF.
Type Counter
Service Operation AccessToken
Dimensions NrfLevel, RequesterPLMNId, TargetPLMNId, NfFqdn

Note: The NfFQDN dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-183 ocnrf_roaming_accessToken_rx_responses_total

Field Details
Description Number of inter-PLMN Access Token response received by vNRF from hNRF for routed or forwarded requests.
Type Counter
Service Operation AccessToken
Dimensions NrfLevel, RequesterPLMNId, TargetPLMNId, NfFqdn, HttpStatusCode, FailureReason

Note: The NfFQDN dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-184 ocnrf_roaming_nfStatusNotify_tx_requests_total

Field Details
Description Number of NFStatusNotify requests sent for inter_PLMN cases
Type Counter
Service Operation NFNotify
Dimensions NrfLevel, NotificationEventType, TargetNfType, NfFqdn, SubscriptionId, SubscriberPLMNId

Note: The NfFQDN dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-185 ocnrf_roaming_nfStatusNotify_rx_responses_total

Field Details
Description Number of NFStatusNotify responses received for inter_PLMN cases.
Type Counter
Service Operation NFNotify
Dimensions NrfLevel, NotificationEventType, TargetNfType, NfFqdn, HttpStatusCode, SubscriptionId, SubscriberPLMNId

Note: The NfFQDN dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-186 ocnrf_roaming_round_trip_time_seconds

Field Details
Description Average Latency between messages sent by visited NRF towards home NRF and after receiving response from home NRF for NRF Roaming messages.
Type Counter
Service Operation NFStatusSubscribe, NFStatusUnSubscribe, NfAccessToken
Dimensions NrfLevel, RequesterPLMNId, TargetPLMNId, ServiceOperation, NfFqdn

Note: The NfFQDN dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-187 ocnrf_roaming_jetty_latency_seconds

Field Details
Description Time (in microseconds) after sending query to SLF and getting response from SLF.
Type Histogram
Service Operation NFDiscover
Dimensions Host, InstanceIdentifier, Method, NrfLevel, ServiceOperation

6.1.10 Georedundancy Metrics

This section provides details about the georedundancy metrics.

Table 6-188 ocnrf_dbreplication_status

Field Details
Description The current status of the replication channel between the given site and the remote site(s). This metric is pegged only if the georedundancy feature is enabled.

Value 0 - UP

Value 1 - DOWN

Type Gauge
Service Operation NA
Dimensions NrfLevel, RemoteSiteName, RemoteNrfInstanceId

Table 6-189 ocnrf_dbreplication_down_time_seconds

Field Details
Description Time taken for the replication status to change from "INACTIVE" to "ACTIVE". This metric is pegged only if the georedundancy feature is enabled.
Type Histogram
Service Operation NA
Dimensions NrfLevel, DbReplicationDownStartTime, DbReplicationDownEndTime, RemoteSiteName, RemoteNrfInstanceId

Table 6-190 ocnrf_nf_switch_over_total

Field Details
Description The number of NFInstances that got switched over from the mated site.
Type Counter
Service Operation NfRegister, NfUpdate,NfDeregister, NfHeartbeat
Dimensions NrfLevel, NfInstanceId, RemoteNrfInstanceId, Service_Operation,OperationType, NfFqdn

Note: The NfFqdn dimension contains the FQDN as present in the NfProfile.

Table 6-191 ocnrf_nfSubscriptions_switch_over_total

Field Details
Description The number of NfSubscriptions that got switched over from the mated site.
Type Counter
Service Operation NfStatusSubscribe, NfStatusUnsubscribe, NrfAuditor
Dimensions NrfLevel, RemoteNrfInstanceId, serviceOperation, OperationType

Table 6-192 ocnrf_stale_nf_deleted_total

Field Details
Description The number of NfInstances that get deleted by the NrfAuditor when it detects a record to be stale.
Type Counter
Service Operation NA
Dimensions NrfLevel, NfInstanceId, NfStatus, NfFqdn

Note: The NfFqdn dimension contains the FQDN as present in the NfProfile.

Table 6-193 ocnrf_stale_nfSubscriptions_deleted_total

Field Details
Description The number of NfSubscriptions that get deleted by the NrfAuditor when it detects a record to be stale.
Type Counter
Service Operation NA
Dimensions NrfLevel, SubscriptionStatus

Table 6-194 ocnrf_reported_dbreplication_status

Field Details
Description The current status of the replication channel between the given site and a remote site(s) as reported by the DB Monitor Service. This metric shall be pegged only if the georedundancy feature is enabled.

Value 0 - UP

Value 1 - DOWN

Type Gauge
Service Operation NA
Dimensions NrfLevel, nrfInstanceId,SiteName

Table 6-195 ocnrf_replication_status_check_total

Field Details
Description If the metric value remains constant over a period of time, an alert is raised.
Type Counter
Service Operation NA
Dimensions NrfLevel

Table 6-196 ocnrf_replication_status_check_total

Field Details
Description

This metric measures whether replication status monitoring thread is running in the following NRF microservices:

  • nfsubscription
  • nrfconfiguration
  • nfdiscovery
  • nfregistration
  • nfaccesstoken
  • nrfartisan

This metric is pegged before the replication status monitoring performs the replication check as per the interval configured in monitorDBReplicationStatusInterval parameter under geoRedundancyOptions.

Type Counter
Service Operation NA
Dimensions NrfLevel

6.1.11 NF Authentication Metrics

This section provides details about the network function authentication metrics.

Table 6-197 ocnrf_nf_authentication_failure_total

Field Details
Description The total number of request for which FQDN based authentication failed at OCNRF.
Type Counter
Service Operation NFAccessToken/NFRegistration/NFSubscription/NFDiscovery/NfListRetrieval/NfProfileRetrieval

For NfListRetrieval and NfProfileRetrieval serviceOperations NfFqdn is filled as NotApplicable.

If OC-XFCC-DNS header is not received at NRF microservice then TLSFqdn is filled as "UNKNOWN".

Dimensions NrfLevel, Method, ServiceOperation, NfFqdn, TLSFqdn

Note: The NfFqdn dimension contains the FQDN as present in the NfProfile.

6.1.12 NF Instance and NF Services Status Change Metrics

This section provides details about the NF Instance and NF Services Status Change metrics.

Table 6-198 ocnrf_nfInstance_status_change_total

Field Details
Description

This metric indicates the total number of times the NfStatus changed for a given NfInstance. For each NfStatus change this metric will be pegged with a combination of NfInstanceId, PreviousStatus, and NewStatus (with other dimensions).

For example, NfInstanceId-1 changed its NfStatus from SUSPENDED to REGISTERED, then the metric will be pegged with a combination of NfInstanceId-1, PreviousStatus as SUSPENDED, and NewStatus as REGISTERED.

Similarly, NfInstanceId-1 changed its NfStatus from REGISTERED to UNDISCOVERABLE, then the metric will be pegged with a combination of NfInstanceId-1, PreviousStatus as REGISTERED, and NewStatus as UNDISCOVERABLE.

Type Counter
Service Operation NfRegister, NfUpdate, NfDeregister
Dimensions NrfLevel, NfInstanceId, NfProfileFqdn, NfType, PreviousStatus, NewStatus

Table 6-199 ocnrf_nfService_status_change_total

Field Details
Description

This metric indicates the total number of times the NfServiceStatus changed for a given NfServiceInstance of a NfProfile. For each NfServiceStatus change this metric will be pegged with a combination of NfInstanceId, NfServiceInstanceId, PreviousStatus, and NewStatus (with other dimensions).

For example, NfInstanceId-1's NfServiceInstanceId-1 changed its NfServiceStatus from SUSPENDED to REGISTERED, then the metric will be pegged with a combination of NfInstanceId-1, NfServiceInstanceId-1, PreviousStatus as SUSPENDED, and NewStatus as REGISTERED.

Similarly, NfInstanceId-1's NfServiceInstanceId-1 changed its NfServiceStatus from REGISTERED to UNDISCOVERABLE, then the metric will be pegged with a combination of NfInstanceId-1, NfServiceInstanceId-1, PreviousStatus as REGISTERED, and NewStatus as UNDISCOVERABLE.

Type Counter
Service Operation NfRegister, NfUpdate, NfDeregister
Dimensions NrfLevel, NfInstanceId, NfServiceName, NfServiceInstanceId, NfProfileFqdn, NfServiceFqdn, PreviousStatus, NewStatus

6.1.13 DNS NAPTR Update Metrics

This section provides details about the DNS NAPTR update metrics.

NRF Microservices Metrics

Table 6-200 ocnrf_dns_naptr_tx_requests_total

Field Details
Description Number of DNS record update requests sent.

Note: The value of OperationType dimension is Update.

Type Counter
Service Operation NFRegister, NFUpdate, NFDeregister, NRF Audit
Dimensions NrfLevel, NfInstanceId, NfFqdn, NfSetFqdn, Replacement, OperationType, TriggerMode
Possible Values:
  • OperationType:
    • Update: NF update request towards DNS Server
    • Delete: NF delete request towards DNS Server
  • TriggerMode:
    • Automatic: Triggers generated by 3GPP service operations or NRF Audit.
    • Manual: Triggers generated by the operator initiated retrigger API.

Note: The NfFqdn dimension contains the FQDN as present in the NfProfile.

Table 6-201 ocnrf_dns_naptr_rx_responses_total

Field Details
Description Number of DNS record update responses received.
Type Counter
Service Operation NFRegister, NFUpdate, NFDeregister, NRF Audit
Dimensions NrfLevel, NfInstanceId, NfFqdn, NfSetFqdn, Replacement, OperationType, HttpStatusCode, FailureReason, TriggerMode

Note: The NfFqdn dimension contains the FQDN as present in the NfProfile.

Table 6-202 ocnrf_dns_naptr_tx_requests_total

Field Details
Description Number of DNS record delete requests sent.

Note: The value of OperationType dimension is Delete.

Type Counter
Service Operation NFRegister, NFUpdate, NFDeregister, NRF Audit
Dimensions NrfLevel, NfInstanceId, NfFqdn, NfSetFqdn, Replacement, OperationType, HttpStatusCode, FailureReason, TriggerMode

Note: The NfFqdn dimension contains the FQDN as present in the NfProfile.

Table 6-203 ocnrf_dns_naptr_rx_responses_total

Field Details
Description Number of DNS record delete responses received.

Note: The value of OperationType dimension is Delete.

Type Counter
Service Operation None
Dimensions NrfLevel, NfInstanceId, NfFqdn, NfSetFqdn, Replacement, OperationType, HttpStatusCode, FailureReason, TriggerMode

Note: The NfFqdn dimension contains the FQDN as present in the NfProfile.

Table 6-204 ocnrf_dns_naptr_audit_tx_requests_total

Field Details
Description Number of DNS record audit requests sent.

Note: The value of OperationType dimension is Get.

Type Counter
Service Operation None
Dimensions NrfLevel, NFInstanceId, NfFqdn, NfSetFqdn, Replacement, OperationType

Note: The NfFqdn dimension contains the FQDN as present in the NfProfile.

Table 6-205 ocnrf_dns_naptr_audit_rx_responses_total

Field Details
Description Number of DNS record audit responses received.

Note: The value of OperationType dimension is Get.

Type Counter
Service Operation None
Dimensions NrfLevel, NFInstanceId, NfFqdn, NfSetFqdn, Replacement, OperationType, HttpStatusCode, FailureReason

Note: The NfFqdn dimension contains the FQDN as present in the NfProfile.

Table 6-206 ocnrf_dns_naptr_failure_rx_responses

Field Details
Metric Name ocnrf_dns_naptr_failure_rx_responses
Description Number of DNS record failed responses received.
Type Gauge
Service Operation None
Dimensions NrfLevel, NFInstanceId, NfFqdn, NfSetFqdn, Replacement

Note: The NfFqdn dimension contains the FQDN as present in the NfProfile.

Table 6-207 ocnrf_dns_naptr_round_trip_time_seconds

Field Details
Description Average Latency between messages sent by NRF towards DNS and after receiving response from DNS.
Type Histogram
Service Operation NFRegister, NFUpdate, NFDeregister, NRFAudit, DNS NAPTR Audit, Manual
Dimensions NrfLevel, NFInstanceId, NfFqdn, NfSetFqdn, Replacement, OperationType, TriggerMode

Note: The NfFqdn dimension contains the FQDN as present in the NfProfile.

Table 6-208 ocnrf_dns_naptr_nfRegistration_tx_requests_total

Field Details
Description Number of DNS record trigger sent by NFRegistration microservice to Artisan microservice.
Type Counter
Service Operation NFRegister, NFUpdate, NFDeregister
Dimensions NfInstanceId, TriggerType, NrfLevel

Table 6-209 ocnrf_dns_naptr_nfRegistration_rx_responses_total

Field Details
Description Number of DNS record trigger response received by NFRegistration microservice from Artisan microservice.
Type Counter
Service Operation NFRegister, NFUpdate, NFDeregister
Dimensions NfInstanceId, TriggerType, NrfLevel

Table 6-210 ocnrf_dns_naptr_nrfAuditor_tx_requests_total

Field Details
Description Number of DNS record trigger sent by NRFAuditor microservice to Artisan microservice.
Type Counter
Service Operation NRFAuditor
Dimensions NfInstanceId, TriggerType, NrfLevel

Table 6-211 ocnrf_dns_naptr_nrfAuditor_rx_responses_total

Field Details
Description Number of DNS record trigger response received by NRFAuditor microservice from Artisan microservice.
Type Counter
Service Operation NRFAuditor
Dimensions NfInstanceId, NrfLevel

Table 6-212 ocnrf_dns_naptr_trigger_rx_requests_total

Field Details
Description Number of DNS record trigger request received by Artisan microservice.
Type Counter
Service Operation None
Dimensions NfInstanceId, NrfLevel

Table 6-213 ocnrf_dns_naptr_trigger_tx_responses_total

Field Details
Description Number of DNS record trigger responses sent by Artisan microservice.
Type Counter
Service Operation None
Dimensions NfInstanceId, NrfLevel

NRF Alternate Route Service Metrics

Table 6-214 oc_alternate_route_upstream_dns_request_timeout_total

Field Details
Description Number of DNS record requests timeout total.
Type Counter
Service Operation Service towards DNS server
Dimensions amfFqdn, host, port, replacement

6.1.14 Pod Protection Metrics

This section provides details about the Pod Protection metrics.

Table 6-215 ocnrf_pod_congestion_state

Field Details
Description The metric is used to track the overall congestion state per nfSubscription pod. The values of the metric is as follow:
  • -1: NotApplicable
  • 0: Normal
  • 1: DangerOfCongestion
  • 2: Congested

Note: If the pod protection feature is disabled, this metric will not be available or will contain value as -1.

Type Gauge
Dimensions NrfLevel

Table 6-216 ocnrf_pod_cpu_congestion_state

Field Details
Description The metric is used to track the congestion state based on the CPU usage of the subscription pod. This metric is valid only when the nfSubscription pod protection feature is enabled. The values of the metric is as follow:
  • -1: NotApplicable
  • 0: Normal
  • 1: DangerOfCongestion
  • 2: Congested

Note: If the pod protection feature is disabled, this metric will not be available or will contain value as -1.

Type Gauge
Dimensions NrfLevel

Table 6-217 ocnrf_pod_pending_message_count_congestion_state

Field Details
Description The metric is used to track the congestion state based on the message pending count of the subscription pod. This metric is valid only when the nfSubscription pod protection feature is enabled. The values of the metric is as follow:
  • -1: NotApplicable
  • 0: Normal
  • 1: DangerOfCongestion
  • 2: Congested

Note: If the pod protection feature is disabled, this metric will not be available or will contain value as -1.

Type Gauge
Dimensions NrfLevel

Table 6-218 ocnrf_incoming_connections

Field Details
Metric Name ocnrf_incoming_connections
Description The metric is used to track the number of incoming connections. This metric is applicable only for nfsubscription service.
Type Gauge
Dimensions NrfLevel

Table 6-219 ocnrf_max_concurrent_streams

Field Details
Description The metric is used to track the maximum concurrent streams per connection. This metric is applicable only for nfsubscription service.
Type Gauge
Dimensions NrfLevel , connectionId

Table 6-220 ocnrf_pod_cpu_usage

Field Details
Description The CPU usage of the pod.

Note: If the pod protection feature is disabled, this metric will not be available or will contain value as 0.

Type Gauge
Dimensions NrfLevel

Table 6-221 ocnrf_pod_pending_message_count

Field Details
Description The Pending Message Count value of the pod.

Note: If the pod protection feature is disabled, this metric will not be available or will contain value as 0.

Type Gauge
Dimensions NrfLevel

Table 6-222 ocnrf_pod_incoming_connection_rejected_total

Field Details
Description The number of connections that have been rejected in the DoC or Congested state. This metric is applicable only for nfsubscription service.
Type Counter
Dimensions NrfLevel

Table 6-223 ocnrf_nfNotification_trigger_total

Field Details
Description The number of times a notification trigger is sent to nfSubscription service from the nfregistration and nrfauditor services.
Type Counter
Dimensions NotificationEventType, errorReason: The reason if nfNotification trigger failed from nfregistration or nrfauditor service pods to nfsubscription service pods.

6.1.15 Network Slice Specific Metrics

This section describes the Network Slice Specific metrics that are pegged based on Network Slice Instances (NSIs) and Single Network Slice Selection Assistance Information (SNSSAI).

Table 6-224 ocnrf_nfDiscover_rx_requests_perSnssai_total

Field Details
Description The total number of NFDiscover requests received at a slice that is identified by specific SNSSAI. This metric is pegged for each snssai present in the search query parameters. The search query attributes are snssais and plmn-specific-snssai-list.
Note:
  • snssais of NfService and NfServiceList are not considered for pegging.
  • The SNSSAI belongs to the Producer NF that is discovered.
  • The metric will not get pegged if any of the search query parameters are invalid.
Type Counter
Service Operation NFDiscover
Dimensions sNssai

Table 6-225 ocnrf_nfDiscover_tx_success_response_perSnssai_total

Field Details
Description The total number of success discovery responses with one or more matching NfProfiles sent per slice that is identified by SNSSAI. The metric is pegged for each unique snssai present in the profiles of discovery response. The search query attributes are snssais and plmn-specific-snssai-list. The NfProfile attributes are snssais, perPlmnSnssaiList, sNssaiSmfInfoList, and sNssaiUpfInfoList.
Note:
  • The SNSSAI belongs to the Producer NF that is discovered.
  • Only snssais of NfProfile and xxxInfo are considered for pegging.
  • Response metric may not get pegged for all SNSSAI that is being received in the request message, if there is no matching profiles sent in discovery response for some SNSSAIs.
Type Counter
Service Operation NFDiscover
Dimensions sNssai

Table 6-226 ocnrf_nfDiscover_tx_empty_response_perSnssai_total

Field Details
Description The total number of discovery responses sent with no matching NfProfiles for a slice identified by SNSSAI. This metric is pegged for each snssai present in the search query parameters. The search query attributes are snssais and plmn-specific-snssai-list.
Note:
  • The SNSSAI belongs to the Producer NF that is discovered.
  • In this case, response metric will get pegged for all SNSSAI that is being received in the request message.
Type Counter
Service Operation NFDiscover
Dimensions sNssai

Table 6-227 ocnrf_nfDiscover_tx_failure_response_perSnssai_total

Field Details
Description The total number of failure discovery responses sent per slice that is identified by specific SNSSAI. This metric is pegged for each snssai present in the search query parameters. The search query attributes are snssais and plmn-specific-snssai-list.
Note:
  • The SNSSAI belongs to the Producer NF that is discovered.
  • In this case, response metric will get pegged for all SNSSAI that is being received in the request message.
  • The metric will not get pegged if any of the search query parameters are invalid.
Type Counter
Service Operation NFDiscover
Dimensions sNssai, HttpStatusCode

Table 6-228 ocnrf_nfDiscover_rx_requests_perNsi_total

Field Details
Description The total number of NFDiscover requests received at a slice that is identified by NSI. This metric is pegged for each nsi present in the search query parameter. The search query attribute is nsi-list.
Note:
  • The NSI belongs to the Producer NF that is discovered.
  • The metric will not get pegged if any of the search query parameters are invalid.
Type Counter
Service Operation NFDiscover
Dimensions Nsi

Table 6-229 ocnrf_nfDiscover_tx_success_response_perNsi_total

Field Details
Description The total number of success discovery responses with one or more matching NfProfiles sent per slice that is identified by specific NSI. The metric is pegged for each nsi in the intersection of nsi-list search query parameter and nsiList attribute in the NfProfile present in the discovery response.
Note:
  • The NSI belongs to the Producer NF that is discovered.
  • The metric will not get pegged if any of the search query parameters are invalid.
  • Response metric may not get pegged for all NSI that is being received in the request message, if there is no matching profiles sent in discovery response for some NSIs.
Type Counter
Service Operation NFDiscover
Dimensions Nsi

Table 6-230 ocnrf_nfDiscover_tx_empty_response_perNsi_total

Field Details
Description The total number of discovery response with no matching NfProfiles for a slice identified by NSI. The metric is pegged for each nsi present in the search query parameter. The search query attribute is nsi-list.
Note:
  • The NSI belongs to the Producer NF that is discovered.
  • The metric will not get pegged if any of the search query parameters are invalid.
  • In this case, response metric will get pegged for all SNSSAI that is being received in the request message.
Type Counter
Service Operation NFDiscover
Dimensions Nsi

Table 6-231 ocnrf_nfDiscover_tx_failure_response_perNsi_total

Field Details
Description The total number of failure discovery response for a slice identified by NSI. The metric is pegged for each nsi present in the search query parameter. The search query attribute is nsi-list.
Note:
  • The NSI belongs to the Producer NF that is discovered.
  • The metric will not get pegged if any of the search query parameters are invalid.
  • In this case, response metric will get pegged for all SNSSAI that is being received in the request message.
Type Counter
Service Operation NFDiscover
Dimensions Nsi, HttpStatusCode

Table 6-232 ocnrf_nfDiscover_tx_forwarded_requests_perSnssai_total

Field Details
Description The total number of discovery requests forwarded to another NRF for a slice identified by SNSSAI. The metric is pegged for each snssai present in the search query parameters. The search query attributes are snssais and plmn-specific-snssai-list.
Note:
  • Only snssais of NfProfile and xxxInfo are considered for pegging.
  • The SNSSAI belongs to the Producer NF that is discovered.
Type Counter
Service Operation NFDiscover
Dimensions sNssai, TargetNrfFqdn, NfFqdn

Note: The NfFqdn dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-233 ocnrf_nfDiscover_rx_success_forwarded_responses_perSnssai_total

Field Details
Description The total number of success responses with one or more matching NfProfiles that is received for forwarded discovery request for a slice identified by SNSSAI. The metric is pegged for each snssai present in the intersection of the snssai present in the search query and in the profile. The search query attributes are snssais and plmn-specific-snssai-list. The NfProfile attributes are snssais, perPlmnSnssaiList, sNssaiSmfInfoList, and sNssaiUpfInfoList.
Note:
  • The SNSSAI is associated with producer NF being discovered.
  • Only snssais of NfProfile and xxxInfo are considered for pegging.
  • Response metric may not get pegged for all SNSSAI that is being received in the request message, if there is no matching profiles sent in discovery response for some SNSSAIs.
Type Counter
Service Operation NFDiscover
Dimensions sNssai, NfFqdn, TargetNrfFqdn

Note: The NfFqdn dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-234 ocnrf_nfDiscover_rx_empty_forwarded_responses_perSnssai_total

Field Details
Description The total number of responses that is received for forwarded discovery request with no matching NfProfiles for a slice identified by SNSSAI. The metric is pegged for each snssai present in the search query parameters. The search query attributes are snssais and plmn-specific-snssai-list.
Note:
  • The SNSSAI belongs to the Producer NF that is discovered.
  • The metric will not get pegged if any of the search query parameters are invalid.
  • In this case, response metric will get pegged for all SNSSAI that is being received in the request message.
Type Counter
Service Operation NFDiscover
Dimensions sNssai, NfFqdn, TargetNrfFqdn

Note: The NfFqdn dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-235 ocnrf_nfDiscover_rx_failure_forwarded_responses_perSnssai_total

Field Details
Description The total number of failure responses for forwarded discovery requests for a slice identified by SNSSAI. The metric is pegged for each snssai present in the search query parameters. The search query attributes are snssais and plmn-specific-snssai-list.
Note:
  • The SNSSAI belongs to the Producer NF that is discovered.
  • The metric will not get pegged if any of the search query parameters are invalid.
  • In this case, response metric will get pegged for all SNSSAI that is being received in the request message.
Type Counter
Service Operation NFDiscover
Dimensions sNssai, NfFqdn, HttpStatusCode, TargetNrfFqdn

Note: The NfFqdn dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-236 ocnrf_nfDiscover_tx_forwarded_requests_perNsi_total

Field Details
Description The total number of discovery requests forwarded to another NRF for a slice identified by NSI. The metric is pegged for each nsi present in the search query parameter. The search query attribute is nsi-list.

Note: The NSI belongs to the Producer NF that is discovered.

Type Counter
Service Operation NFDiscover
Dimensions Nsi, NfFqdn, TargetNrfFqdn

Note: The NfFqdn dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-237 ocnrf_nfDiscover_rx_success_forwarded_responses_perNsi

Field Details
Description The total number of success response for forwarded discovery requests for a slice identified by NSI. The NSI associated with producer NF being discovered. The metric is pegged for each nsi in the intersection of nsi-list search query parameter and nsiList attribute in the NfProfiles present in the discovery response.
Note:
  • The NSI is associated with producer NF being discovered.
  • Only nsi of NfProfile and xxxInfo are considered for pegging.
  • Response metric may not get pegged for all NSI that is being received in the request message, if there is no matching profiles sent in discovery response for some NSIs.
Type Counter
Service Operation NFDiscover
Dimensions Nsi, NfFqdn, TargetNrfFqdn

Note: The NfFqdn dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-238 ocnrf_nfDiscover_rx_empty_forwarded_responses_perNsi

Field Details
Description The total number of responses with no matching NfProfiles for forwarded discovery request for a slice identified by NSI. The NSI is associated with the producer NF being discovered. The metric is pegged for each nsi present in the search query parameter. The search query attribute is nsi-list.

Note:

  • The NSI belongs to the Producer NF that is discovered.
  • The metric will not get pegged if any of the search query parameters are invalid.
  • In this case, response metric will get pegged for all NSI that is being received in the request message.
Type Counter
Service Operation NFDiscover
Dimensions Nsi, NfFqdn, TargetNrfFqdn

Note: The NfFqdn dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-239 ocnrf_nfDiscover_rx_failure_forwarded_responses_perNsi_total

Field Details
Description The total number of failure response for forwarded discovery requests for a slice identified by NSI. The metric is pegged for each nsi present in the search query parameter. The search query attribute is nsi-list.
Note:
  • The NSI belongs to the Producer NF that is discovered.
  • The metric will not get pegged if any of the search query parameters are invalid.
  • In this case, response metric will get pegged for all NSI that is being received in the request message.
Type Counter
Service Operation NFDiscover
Dimensions Nsi, NfFqdn, HttpStatusCode, TargetNrfFqdn

Note: The NfFqdn dimension indicates the consumer NF FQDN. This dimension contains the NfFqdn if the service mesh sends the consumer NF FQDN in XFCC header, else the dimension will contain the value as UNKNOWN.

Table 6-240 ocnrf_nfRegister_requests_perSnssai_total

Field Details
Description The total number of NFRegister requests received at a slice that is identified by specific SNSSAI. The metric is pegged for each snssai present in the NfProfile being registered. The attributes considered are snssais, perPlmnSnssaiList, sNssaiSmfInfoList, and sNssaiUpfInfoList.
Note:
  • snssais of NfService and NfServiceList are not considered for pegging.
  • If the NFRegister request has an invalid body, the metric may not get pegged.
Type Counter
Service Operation NFRegister
Dimensions sNssai

Table 6-241 ocnrf_nfRegister_success_responses_perSnssai_total

Field Details
Description The total number of successful NFRegister responses with one or more matching NfProfiles sent per slice identified by SNSSAI. The metric is pegged for each snssai present in the NfProfile being registered. The attributes considered are snssais, perPlmnSnssaiList, sNssaiSmfInfoList, and sNssaiUpfInfoList.

Note: Only snssais of NfProfile and xxxInfo are considered for pegging.

Type Counter
Service Operation NFRegister
Dimensions sNssai

Table 6-242 ocnrf_nfRegister_failure_responses_perSnssai_total

Field Details
Description The total number of failure NFRegister responses sent per slice identified by SNSSAIs. The metric is pegged for each snssai present in the NfProfile being registered. The attributes considered are snssais, perPlmnSnssaiList, sNssaiSmfInfoList, and sNssaiUpfInfoList.
Note:
  • Only snssais of NfProfile and xxxInfo are considered for pegging.
  • The metric may not get pegged if the NFRegister request has an invalid body.
Type Counter
Service Operation NFRegister
Dimensions sNssai, HttpStatusCode

Table 6-243 ocnrf_nfRegister_requests_perNsi_total

Field Details
Description The total number of NFRegister requests received at a slice that is identified by NSI. The metric is pegged for each nsi present in the NfProfile being registered. The attribute considered is nsiList.

Note: The metric may not get pegged if the NFRegister request has an invalid body.

Type Counter
Service Operation NFRegister
Dimensions Nsi

Table 6-244 ocnrf_nfRegister_success_responses_perNsi_total

Field Details
Description The total number of successful NFRegister responses with one or more matching NfProfiles sent per slice that is identified by NSI. The metric is pegged for each nsi present in the NfProfile being registered. The attribute considered is nsiList.
Type Counter
Service Operation NFRegister
Dimensions Nsi

Table 6-245 ocnrf_nfRegister_failure_responses_perNsi_total

Field Details
Description The total number of failure NFRegister responses sent per slice that is identified by NSI. The metric is pegged for each nsi present in the NfProfile being registered. The attribute considered is nsiList.

Note: The metric may not get pegged if the NFRegister request has an invalid body.

Type Counter
Service Operation NFRegister
Dimensions Nsi, HttpStatusCode

Table 6-246 ocnrf_nfUpdate_requests_perSnssai_total

Field Details
Description The total number of NFUpdate requests for slices identified by SNSSAIs. The metric is pegged for Complete Update and Partial Update(PATCH) of a registered NfProfile and for each snssais present in the NfProfile registered. The attributes considered are snssais, perPlmnSnssaiList, sNssaiSmfInfoList, and sNssaiUpfInfoList.
Note:
  • Only snssais of NfProfile and xxxInfo are considered for pegging.
  • If the NFUpdate request has an invalid body, the metric may not get pegged.
  • In case of partial update (PATCH), the metric is pegged only based on the final list of SNSSAI updated in the profile.
  • In case of NfUpdate (PATCH), if the profile is not found, the metric will not be pegged.
Type Counter
Service Operation NFUpdate
Dimensions sNssai

Table 6-247 ocnrf_nfUpdate_success_responses_perSnssai_total

Field Details
Description The total number of successful NFUpdate responses with one or more matching NfProfiles sent per slice identified by SNSSAI. The metric is pegged for Complete Update and Partial Update(PATCH) of a registered NfProfile and for each snssais present in the NfProfile registered. The attributes considered are snssais, perPlmnSnssaiList, sNssaiSmfInfoList, and sNssaiUpfInfoList.
Note:
  • snssais of NfService and NfServiceList are not considered for pegging.
  • If the NFUpdate request has an invalid body, the metric may not get pegged.
  • In case of partial update (PATCH), the metric is pegged only based on the final list of SNSSAI updated in the profile.
  • In case of NfUpdate (PATCH), if the profile is not found, the metric will not be pegged.
Type Counter
Service Operation NFUpdate
Dimensions sNssai

Table 6-248 ocnrf_nfUpdate_failure_responses_perSnssai_total

Field Details
Description The total number of failure NFUpdate responses sent per slice identified by SNSSAIs. The metric is pegged for Complete Update and Partial Update(PATCH) of a registered NfProfile and for each snssais present in the NfProfile registered. The attributes considered are snssais, perPlmnSnssaiList, sNssaiSmfInfoList, and sNssaiUpfInfoList.
Note:
  • Only snssais of NfProfile and xxxInfo are considered for pegging.
  • If the NFUpdate request has an invalid body, the metric may not get pegged.
  • In case of partial update (PATCH), the metric is pegged only based on the final list of SNSSAI updated in the profile.
  • In case of NfUpdate (PATCH), if the profile is not found, the metric will not be pegged.
Type Counter
Service Operation NFUpdate
Dimensions sNssai, HttpStatusCode

Table 6-249 ocnrf_nfUpdate_requests_perNsi_total

Field Details
Description The total number of NFUpdate requests for slices identified by NSI. The metric is pegged for Complete Update and Partial Update (PATCH) of a registered NfProfile and for each nsi present in the NfProfile registered. The attribute considered is nsiList.
Note:
  • Only nsi of NfProfile and xxxInfo are considered for pegging.
  • If the NFUpdate request has an invalid body, the metric may not get pegged.
  • In case of partial update (PATCH), the metric is pegged only based on the updated profile.
  • In case of NfUpdate (PATCH), if the profile is not found, the metric will not be pegged.
Type Counter
Service Operation NFUpdate
Dimensions Nsi

Table 6-250 ocnrf_nfUpdate_success_responses_perNsi_total

Field Details
Description The total number of successful NFUpdate responses for slices identified by NSI. The metric is pegged for Complete Update and Partial Update (PATCH) of a registered NfProfile and for each nsi present in the NfProfile registered. The attribute considered is nsiList.
Note:
  • Only nsi of NfProfile and xxxInfo are considered for pegging.
  • If the NFUpdate request has an invalid body, the metric may not get pegged.
  • In case of partial update (PATCH), the metric is pegged only based on the final list of SNSSAI updated in the profile.
  • In case of NfUpdate (PATCH), if the profile is not found, the metric will not be pegged.
Type Counter
Service Operation NFUpdate
Dimensions Nsi

Table 6-251 ocnrf_nfUpdate_failure_responses_perNsi_total

Field Details
Description The total number of failure NFUpdate responses for slices identified by NSI. The metric is pegged for Complete Update and Partial Update (PATCH) of a registered NfProfile and for each nsi present in the NfProfile registered. The attribute considered is nsiList.
Note:
  • Only nsi of NfProfile and xxxInfo are considered for pegging.
  • If the NFUpdate request has an invalid body, the metric may not get pegged.
  • In case of partial update (PATCH), the metric is pegged only based on the final list of SNSSAI updated in the profile.
  • In case of NfUpdate (PATCH), if the profile is not found, the metric will not be pegged.
Type Counter
Service Operation NFUpdate
Dimensions Nsi, HttpStatusCode

Table 6-252 ocnrf_nfDeregister_requests_perSnssai_total

Field Details
Description The total number of NFDeregister requests received at a slice that is identified by SNSSAIs. The metric is pegged for each snssais present in the registered NfProfile. The attributes considered are snssais, perPlmnSnssaiList, sNssaiSmfInfoList, and sNssaiUpfInfoList.
Note:
  • Only snssais of NfProfile and xxxInfo are considered for pegging.
  • If the profile is not found in the database or if the profile is in deregistered state, the metric will not get pegged.
Type Counter
Service Operation NFDeregister
Dimensions sNssai

Table 6-253 ocnrf_nfDeregister_success_responses_perSnssai_total

Field Details
Description The total number of successful NFDeregister responses with one or more matching NfProfiles sent per slice that is identified by SNSSAI. The metric is pegged for each snssais present in the registered NfProfile. The attributes considered are snssais, perPlmnSnssaiList, sNssaiSmfInfoList, and sNssaiUpfInfoList.
Note:
  • Only snssais of NfProfile and xxxInfo are considered for pegging.
  • If the profile is not found in the database or if the profile is in deregistered state, the metric will not get pegged.
Type Counter
Service Operation NFDeregister
Dimensions sNssai

Table 6-254 ocnrf_nfDeregister_failure_responses_perSnssai_total

Field Details
Description The total number of failure NFDeregister responses sent per slice that is identified by SNSSAIs. The metric is pegged for each snssais present in the registered NfProfile. The attributes considered are snssais, perPlmnSnssaiList, sNssaiSmfInfoList, and sNssaiUpfInfoList.
Note:
  • Only snssais of NfProfile and xxxInfo are considered for pegging.
  • If the profile is not found in the database or if the profile is in deregistered state, the metric will not get pegged.
Type Counter
Service Operation NFDeregister
Dimensions sNssai, HttpStatusCode

Table 6-255 ocnrf_nfDeregister_requests_perNsi_total

Field Details
Description The total number of NFDeregister requests received at a slice that is identified by NSI. The metric is pegged for each nsi present in the registered NfProfile. The attribute considered is nsiList.
Note:
  • Only nsi of NfProfile and xxxInfo are considered for pegging.
  • If the profile is not found in the database or if the profile is in deregistered state, the metric will not get pegged.
Type Counter
Service Operation NFDeregister
Dimensions Nsi

Table 6-256 ocnrf_nfDeregister_success_responses_perNsi_total

Field Details
Description The total number of successful NFDeregister responses with one or more matching NfProfiles sent per slice that is identified by NSI. The metric is pegged for each nsi present in the registered NfProfile. The attribute considered is nsiList.
Note:
  • Only nsi of NfProfile and xxxInfo are considered for pegging.
  • If the profile is not found in the database or if the profile is in deregistered state, the metric will not get pegged.
Type Counter
Service Operation NFDeregister
Dimensions Nsi

Table 6-257 ocnrf_nfDeregister_failure_responses_perNsi_total

Field Details
Description The total number of failure NFDeregister responses sent per slice that is identified by NSI. The metric is pegged for each nsi present in the registered NfProfile. The attribute considered is nsiList.
Note:
  • Only nsi of NfProfile and xxxInfo are considered for pegging.
  • If the profile is not found in the database or if the profile is in deregistered state, the metric will not get pegged.
Type Counter
Service Operation NFDeregister
Dimensions Nsi, HttpStatusCode

Table 6-258 ocnrf_nfHeartBeat_requests_perSnssai_total

Field Details
Description The total number of NF HeartBeat requests received at a slice that is identified by SNSSAIs. The attributes considered are snssais, perPlmnSnssaiList, sNssaiSmfInfoList, and sNssaiUpfInfoList.
Note:
  • Only snssais of NfProfile and xxxInfo are considered for pegging.
  • The metric will not get pegged if the nfHeartBeat request has an invalid body.
Type Counter
Service Operation NfHeartBeat
Dimensions sNssai

Table 6-259 ocnrf_nfHeartBeat_success_responses_perSnssai_total

Field Details
Description The total number of success NF HeartBeat responses with one or more matching NfProfiles sent per slice that is identified by SNSSAIs. The attributes considered are snssais, perPlmnSnssaiList, sNssaiSmfInfoList, and sNssaiUpfInfoList.

Note: Only snssais of NfProfile and xxxInfo are considered for pegging.

Type Counter
Service Operation NfHeartBeat
Dimensions sNssai

Table 6-260 ocnrf_nfHeartBeat_failure_responses_perSnssai_total

Field Details
Description The total number of failure NF HeartBeat Update responses for slices identified by SNSSAIs. The attributes considered are snssais, perPlmnSnssaiList, sNssaiSmfInfoList, and sNssaiUpfInfoList.
Note:
  • snssais of NfService and NfServiceList are not considered for pegging.
  • The metric will not get pegged if the nfHeartBeat request has an invalid body.
Type Counter
Service Operation NfHeartBeat
Dimensions sNssai, HttpStatusCode

Table 6-261 ocnrf_nfHeartBeat_requests_perNsi_total

Field Details
Description The total number of NF HeartBeat requests received at a slice that is identified by Nsi. The attribute considered is nsiList.
Note:
  • Only nsi of NfProfile and xxxInfo are considered for pegging.
  • The metric will not get pegged if the nfHeartBeat request has an invalid body.
Type Counter
Service Operation NfHeartBeat
Dimensions Nsi

Table 6-262 ocnrf_nfHeartBeat_success_responses_perNsi_total

Field Details
Description The total number of successful NF HeartBeat responses with one or more matching NfProfiles sent per slice that is identified by Nsi. The attribute considered is nsiList.

Note: Only nsi of NfProfile and xxxInfo are considered for pegging.

Type Counter
Service Operation NfHeartBeat
Dimensions Nsi

Table 6-263 ocnrf_nfHeartBeat_failure_responses_perNsi_total

Field Details
Description The total number of failure NF HeartBeat responses sent per slice that is identified by Nsi. The attribute considered is nsiList.
Type Counter
Service Operation NfHeartBeat
Dimensions Nsi, HttpStatusCode

6.1.16 NRF Cache Data Metrics

Table 6-264 ocnrf_cds_rx_requests_total

Field Details
Description The number of requests received at Cache Data Service.
Type Counter
Dimensions NrfLevel, RequestType

Possible values for RequestType are RemoteAndLocalSetProfiles, ProfilesByQueryParam, and RemoteAndLocalSetSubscriptions

Table 6-265 ocnrf_cds_tx_responses_total

Field Details
Description The number of responses sent by the Cache Data Service.
Type Counter
Dimensions NrfLevel, RequestType, HttpStatusCode.

Possible values for RequestType are RemoteAndLocalSetProfiles, ProfilesByQueryParam, and RemoteAndLocalSetSubscriptions

Table 6-266 ocnrf_cds_round_trip_time_seconds

Field Details
Description The time taken to process the request at Cache Data Service in 50, 90, 95, and 99 percentiles.
Type Histogram
Dimensions NrfLevel, RequestType

Possible values for RequestType are RemoteAndLocalSetProfiles, ProfilesByQueryParam, and RemoteAndLocalSetSubscriptions

Table 6-267 ocnrf_query_remote_cds_requests_total

Field Details
Description The number of requests sent to the NRF of a remote NRF set by Cache Data Service.
Type Counter
Dimensions NrfLevel, QueryType, RemoteNrfFqdn, TargetNrfSetId.

Possible values of QueryType are NfProfiles and NfSubscriptions.

Table 6-268 ocnrf_query_remote_cds_responses_total

Field Details
Description The number of responses received from the NRF of a remote NRF set by Cache Data Service.
Type Counter
Dimensions NrfLevel, QueryType, HttpStatusCode, RemoteNrfFqdn, TargetNrfSetId.

Possible values of QueryType are NfProfiles and NfSubscriptions.

Table 6-269 ocnrf_query_remote_cds_round_trip_time_seconds

Field Details
Description The time taken between the request sent by Cache Data Service towards remote NRF set and response received.

It is measured in 50, 90, 95, and 99 percentiles.

Type Histogram
Dimensions NrfLevel, QueryType, HttpStatusCode, RemoteNrfFqdn, TargetNrfSetId.

Possible values of QueryType are NfProfiles and NfSubscriptions.

Table 6-270 ocnrf_query_remote_cds_message_size_bytes

Field Details
Description The size of the response received by the Cache Data Service from the remote NRF set. The size is pegged in bytes and is published in buckets of 1kB, 5KB, 10KB, 50KB, 100KB, 500KB, and 1MB.
Type Histogram
Dimensions NrfLevel, QueryType, RemoteNrfFqdn, HttpStatusCode, SourceNrfSetId, TargetNrfSetId.

Possible values of QueryType are NfProfiles and NfSubscriptions.

Table 6-271 ocnrf_cache_fallback_total

Field Details
Description The number of times the request was fulfilled from the in-memory cache of Cache Data Service due to cnDBTier query errors.
Type Counter
Dimensions NrfLevel, ErrorReason

Table 6-272 ocnrf_db_fallback_total

Field Details
Description The number of times a service request was fulfilled from the cnDBTier using local NRF set data as the query towards the Cache Data Service failed.
Type Counter
Dimensions NrfLevel, ServiceOperation

Possible values of ServiceOperation are NfProfileRetrieval, NfListRetrieval, NfAccessToken, NfDiscover, NfStatusSubscribe, NfStatusUnsubscribe, and NfStatusNotify

Table 6-273 ocnrf_query_cds_requests_total

Field Details
Description The number of requests to the Cache Data Service sent by the local NRF microservices for state data. For the list of local NRF microservices, see the Enhanced NRF Set Based Deployment (NRF Growth) section.
Type Counter
Dimensions NrfLevel, ServiceOperation

Possible values of ServiceOperation are NfProfileRetrieval, NfListRetrieval, NfAccessToken, NfDiscover, NfSubscribe, NfUnsubscribe, notifyProfileChange, notifyProfileDeregistration, notifyProfileRegistration, FindAllNfSubscription, NFInstanceFetch, CUSTOM_NRF_AUDIT_NF_COUNT, and CUSTOM_NRF_AUDIT_NF_SIZE.

Table 6-274 ocnrf_query_cds_responses_total

Field Details
Description The number of responses from the Cache Data Service to the local NRF microservices for state data. For the list of local NRF microservices, see the Enhanced NRF Set Based Deployment (NRF Growth) section.
Type Counter
Dimensions NrfLevel, HttpStatusCode, ServiceOperation

Possible values of ServiceOperation are NfProfileRetrieval, NfListRetrieval, NfAccessToken, NfDiscover, NfSubscribe, NfUnsubscribe, notifyProfileChange, notifyProfileDeregistration, notifyProfileRegistration, FindAllNfSubscription, NFInstanceFetch, CUSTOM_NRF_AUDIT_NF_COUNT, and CUSTOM_NRF_AUDIT_NF_SIZE.

Table 6-275 ocnrf_query_cds_round_trip_time_seconds

Field Details
Description The time taken between the request sent by local NRF set microservices to Cache Data Service and response received. It is measured in 50, 95, and 99 percentiles.
Type Histogram
Dimensions NrfLevel, ServiceOperation

Possible values of ServiceOperation are NfProfileRetrieval, NfListRetrieval, NfAccessToken, NfDiscover, NfSubscribe, NfUnsubscribe, notifyProfileChange, notifyProfileDeregistration, notifyProfileRegistration, FindAllNfSubscription, NFInstanceFetch, CUSTOM_NRF_AUDIT_NF_COUNT, and CUSTOM_NRF_AUDIT_NF_SIZE.

Table 6-276 ocnrf_dbmetrics_total

Field Details
Description The number of database operation counts corresponding to every service operation.
Type Counter
Dimensions method, dbOperation, ServiceOperation, NrfLevel, HttpStatusCode
Possible values for:
  • dbOperation: find
  • ServiceOperation: nrfCacheDataService

Table 6-277 ocnrf_nf_registered_count

Field Details
Description The total number of NFs registered in the segment.
Type Gauge
Dimensions NrfLevel, RequesterNfType

Table 6-278 ocnrf_cache_sync_count_total

Field Details
Description The number of in-memory cache entries synchronized. The metric is pegged at the at the Cache Data Service and Discovery Service.
Type Counter
Dimensions NrfLevel, NrfFqdn, SourceNrfSetId, TargetNrfSetId, DataType, CompleteSync

Possible values of DataType are NfProfiles and NfSubscriptions

Possible values of CompleteSync are true and false

Table 6-279 ocnrf_remote_set_unavailable_total

Field Details
Description All the NRFs of a remote NRF set are unavailable for synchronizing state data.
Type Counter
Dimensions NrfLevel,SourceNrfSetId, TargetNrfSetId

Table 6-280 ocnrf_all_remote_sets_unavailable_total

Field Details
Description All the NRFs of all remote NRF sets are unavailable for synchronizing state data.
Type Counter
Dimensions NrfLevel,SourceNrfSetId, TargetNrfSetId

Table 6-281 ocnrf_cds_rx_remote_requests_total

Field Details
Description The number of requests received at Cache Data Service from remote NRFs.
Type Counter
Dimensions QueryType

Table 6-282 ocnrf_cds_rx_remote_responses_total

Field Details
Description The number of responses sent by the Cache Data Service to the remote NRF.
Type Counter
Dimensions QueryType

Table 6-283 ocnrf_cds_remote_rx_request_round_trip_time

Field Details
Description The time taken to process the request received from the Remote NRF at Cache Data Service.
Type Histogram
Dimensions QueryType

6.1.17 Overload Control

Table 6-284 load_level

Field Details
Description The metric is used to track the load level as per the services.
Type Gauge
Dimensions service, isLeaderPod

Table 6-285 service_resource_stress

Field Details
Description This metric tracks CPU, memory, failure count, and pending requests on the basis of which the overload level of a service is calculated.
Type Gauge
Dimension type, service, isLeaderPod

Table 6-286 service_resource_overload_level

Field Details
Description This metric tracks an individual resource's overload level that is calculated based on the resource usage and configured threshold.
Type Gauge
Dimension type, service, isLeaderPod

6.2 NRF KPIs

This section includes information about KPIs for Oracle Communications Cloud Native Core, Network Repository Function (NRF).

Note:

Sample NRF dashboard for Grafana is delivered to the customer through NRF CSAR package. Metrics and functions used to achieve KPI are already covered in NRF CSAR package.

6.2.1 NRF Service KPIs

This section lists the service status, Gateway, Service latency, Database latency KPIs.

Table 6-287 Registration Service Success Ratio (2xx) %

Field Details
Description Measures the total number of successful registration service operations at NRF.

For more information about metric used, see NRF Gateways Metrics.

Expression Expression: sum(increase(oc_ingressgateway_http_responses_total{Status=~\"2.*\",Route_path=~\".*nnrf-nfm/v1/nf-instances.*\",kubernetes_namespace=\"$namespace\"}[5m]))/sum(increase(oc_ingressgateway_http_responses_total{Route_path=~\".*nnrf-nfm/v1/nf-instances.*\",kubernetes_namespace=\"$namespace\"}[5m]))*100

Table 6-288 Subscription Service Success Ratio (2xx) %

Field Details
Description Measures the total number of successful subscription service operations at NRF.

For more information about metric used, see NRF Gateways Metrics.

Expression sum(increase(oc_ingressgateway_http_responses_total{Status=~\"2.*\",Route_path=~\".*nnrf-nfm/v1/nf-instances.*\",kubernetes_namespace=\"$namespace\"}[5m]))/sum(increase(oc_ingressgateway_http_responses_total{Route_path=~\".*nnrf-nfm/v1/nf-instances.*\",kubernetes_namespace=\"$namespace\"}[5m]))*100

Table 6-289 Discover Service Success Ratio (2xx) %

Field Details
Description Measures the total number of successful discover service operations at NRF.

For more information about metric used, see NRF Gateways Metrics.

Expression sum(increase(oc_ingressgateway_http_responses_total{Status=~\"2.*\",Route_path=~\".*nnrf-disc/v1/nf-instances.*\",kubernetes_namespace=\"$namespace\"}[5m]))/sum(increase(oc_ingressgateway_http_responses_total{Route_path=~\".*nnrf-disc/v1/nf-instances.*\",kubernetes_namespace=\"$namespace\"}[5m]))*100

Table 6-290 AccessToken Service Success Ratio (2xx) %

Field Details
Description Measures the total number of successful Access Token service operations at NRF.

For more information about metric used, see NRF Gateways Metrics.

Expression sum(increase(oc_ingressgateway_http_responses_total{Status=~\"2.*\",Route_path=~".*oauth2/token.*",kubernetes_namespace=\"$namespace\"}[5m]))/sum(increase(oc_ingressgateway_http_responses_total{Route_path=~".*oauth2/token.*",kubernetes_namespace=\"$namespace\"}[5m]))*100

Table 6-291 SLF Query Success Ratio (2xx) %

Field Details
Description Measures the total number of SLF query response received.

For more information about metric used, see NRF SLF Metrics.

Expression sum(increase(ocnrf_SLF_rx_responses_total{HttpStatusCode=~\"2.*\",kubernetes_namespace=\"$namespace\"}[5m]))/sum(increase(ocnrf_SLF_rx_responses_total{kubernetes_namespace=\"$namespace\"}[5m]))*100

Table 6-292 Active Registrations

Field Details
Description Measures the total number of active registered NFs at any point of time to indicate that the data comes per NF type. This is based on [ NfType :- {{ RequesterNfType }} ]
Expression sum(ocnrf_active_registrations_count{namespace="$namespace"}) by(RequesterNfType)

Table 6-293 Suspended NFs

Field Details
Description Measures the difference in number of profiles that have been marked as suspended when a profile has missed nfHeartBeatMissAllowed. This is based on [NfInstance :- {{ NfInstanceId }}]
Expression increase(ocnrf_nf_suspended_total{namespace="$namespace"}[5m])

Table 6-294 Total NfSubscriptions expired

Field Details
Description Measures the total number of NfSubscriptions whose validityTime has expired.
Expression increase(ocnrf_nfSubscriptions_expired_total{namespace="$namespace"}[5m])

Table 6-295 NfDiscoveredProfiles

Field Details
Description Measures the rate of number of profiles returned in discovery response.

For more information about metric used, see NRF NF Metrics.

Expression sum(irate(ocnrf_nfDiscover_profiles_discovered_total{namespace="$namespace"}[2m])) by (Bucket,TargetNfType)

Table 6-296 NfRegister Responses

Field Details
Description Measures the rate of successful registration responses sent. This is based on [ HttpStatusCode:- {{HttpStatusCode}}, NfFqdn-{{ NfFqdn }}]

For more information about metric used, see NRF NF Metrics.

Expression sum(irate(ocnrf_nfRegister_tx_responses_total{namespace="$namespace"}[2m])) by (HttpStatusCode, NfFqdn)

Table 6-297 NfUpdate Response (Complete)

Field Details
Description Measures the rate of successful updates response sent. This is based on [ HttpStatusCode :- {{HttpStatusCode }}, NfFqdn :- {{ NfFqdn }} ]

For more information about metric used, see NRF NF Metrics.

Expression sum(irate(ocnrf_nfUpdate_tx_responses_total{namespace="$namespace",Updatetype="Complete"}[2m])) by (HttpStatusCode, NfFqdn)

Table 6-298 NfUpdate Response (Partial)

Field Details
Description Measures the rate of successful updates of an NF Profile which is previously registered at NRF. This is based on [ HttpStatusCode :- {{HttpStatusCode }}, NfFqdn :- {{ NfFqdn }} ]

For more information about metric used, see NRF NF Metrics.

Expression sum(irate(ocnrf_nfUpdate_tx_responses_total{namespace="$namespace",Updatetype="Partial"}[2m])) by (HttpStatusCode, NfFqdn)

Table 6-299 NfDeregister Responses

Field Details
Description Measures the rate of successful Deregistration of NFs at NRF. This is based on [ HttpStatusCode :- {{HttpStatusCode}},NfFqdn :- {{ NfFqdn }} ]

For more information about metric used, see NRF NF Metrics.

Expression sum(irate(ocnrf_nfDeregister_tx_responses_total{namespace="$namespace"}[2m])) by (HttpStatusCode, NfFqdn)

Table 6-300 NfProfileRetrieval Response

Field Details
Description Measures the rate at which NfProfileRetrieval service requests that NRF rejects due to various error reasons. This KPI considers all non success error codes. This is based on [HttpStatusCode :- {{HttpStatusCode}}]

For more information about metric used, see NRF NF Metrics.

Expression sum(irate(ocnrf_nfProfileRetrieval_tx_responses_total{namespace="$namespace"}[2m])) by(HttpStatusCode)

Table 6-301 NfHeartbeat Responses

Field Details
Description Measures the number of Heartbeat Responses sent. This is based on [HttpStatusCode :- {{HttpStatusCode}}]

For more information about metric used, see NRF NF Metrics.

Expression sum(irate(ocnrf_nfHeartBeat_tx_responses_total{namespace="$namespace"}[2m])) by(HttpStatusCode)

Table 6-302 NFStatusSubscribe

Field Details
Description Measures the total number of NfStatusSubscribe responses sent. This is based on [HttpStatusCode :- {{HttpStatusCode}} ]

For more information about metric used, see NRF NF Metrics.

Expression sum(irate(ocnrf_nfStatusSubscribe_tx_responses_total{namespace="$namespace",OperationType="Create"}[2m])) by (HttpStatusCode)

Table 6-303 NFStatusSubscribe (PATCH)

Field Details
Description Measures the total number of NfStatusSubscribe update responses sent. This is based on [HttpStatusCode :- {{HttpStatusCode}} ]

For more information about metric used, see NRF NF Metrics.

Expression sum(irate(ocnrf_nfStatusSubscribe_tx_responses_total{namespace="$namespace",OperationType="Update"}[2m])) by (HttpStatusCode)

Table 6-304 NFStatusUnsubscribe [HttpStatusCode :- {{HttpStatusCode}}]

Field Details
Description Measures the total number of NfStatusUnsubscribe responses sent.

For more information about metric used, see NRF NF Metrics.

Expression sum(irate(ocnrf_nfStatusUnsubscribe_tx_responses_total{namespace="$namespace"}[2m])) by (HttpStatusCode)

Table 6-305 NfStatusNotify Response

Field Details
Description Measures the total number of NfStatusNotify responses received. This is based on [HttpStatusCode :- {{HttpStatusCode}}]

For more information about metric used, see NRF NF Metrics.

Expression sum(irate(ocnrf_nfStatusNotify_rx_responses_total{namespace="$namespace"}[2m])) by(HttpStatusCode)

Table 6-306 NfDiscovery Responses

Field Details
Description Measures the total number of NfDiscover responses sent. This is based on [HttpStatusCode :- {{HttpStatusCode}}]

For more information about metric used, see NRF NF Metrics.

Expression sum(irate(ocnrf_nfDiscover_tx_responses_total{namespace="$namespace"}[2m])) by (HttpStatusCode)

Table 6-307 SLF Response

Field Details
Description Measures the total number of SLF query response received. This is based on [ HttpStatusCode :- {{HttpStatusCode}},TargetNfType :- {{TargetNfType}} ]
Expression sum(irate(ocnrf_SLF_rx_responses_total{namespace="$namespace"}[2m])) by(HttpStatusCode,TargetNfType)

Table 6-308 Forwarded Response

Field Details
Description Measures the total number of forwarded query response received. This is based on [ HttpStatusCode :- {{HttpStatusCode}}]
Expression sum(irate(ocnrf_forward_nfDiscover_rx_responses_total{namespace="$namespace"}[2m])) by(HttpStatusCode)

Table 6-309 Access Token Success

Field Details
Description Measures the total number of successful Access Token service operations at NRF.

For more information about metric used, see NRF Gateways Metrics.

Expression sum(irate(oc_ingressgateway_http_responses_total{Status="200 OK",Route_path=~".*/oauth2/token.*",Method="POST",namespace="$namespace"}[5m]))

Table 6-310 4xx Responses (AccessToken)

Field Details
Description Measures the rate of successful AccessToken requests with 4xx response at NRF.

For more information about metric used, see NRF Gateways Metrics.

Expression sum(irate(oc_ingressgateway_http_responses_total{Status=~"4.*",Route_path=~".*/oauth2/token*.",namespace="$namespace"}[5m]))

Table 6-311 5xx Responses (AccessToken)

Field Details
Description Measures the rate of successful AccessToken requests with 5xx response at NRF.

For more information about metric used, see NRF Gateways Metrics.

Expression sum(irate(oc_ingressgateway_http_responses_total{Status=~"5.*",Route_path=~".*/oauth2/token.*",namespace="$namespace"}[5m]))

Table 6-312 Current KeyId Health

Field Details
Description Measures the health status of Oauth Token Signing keys. This is based on [ KeyId : {{ KeyId }}, KeyType : {{ KeyType }}]

For more information about metric used, see NRF NF Metrics.

Expression ocnrf_oauth_keyData_healthStatus{app_kubernetes_io_name=\"nrfconfiguration\",isCurrentKeyId=\"true\",kubernetes_namespace=\"$namespace\"}

Table 6-313 NF AccessToken Failures

Field Details
Description Measures the rate at which NFAccesstoken service requests that NRF rejects due to various error reasons. This KPI considers all non success error codes.

For more information about metric used, see NRF Gateways Metrics.

Expression sum(irate(oc_ingressgateway_http_responses_total{Status!~"2.*",Route_path=~".*oauth2/token.*",kubernetes_namespace="$namespace"}[5m]))

Table 6-314 NF Discover Profile Discovered

Field Details
Description Measures the number of Profiles returned in discovery response. Depending on bucket size and corresponding value will tell how many profiles are returned in discovery response.

For more information about metric used, see NRF Gateways Metrics.

Expression sum(irate(ocnrf_nfDiscover_profiles_discovered_total{namespace="$namespace"}[2m])) by (Bucket,TargetNfType)

Table 6-315 Egress Gateway Response for Nrf Forward Response {{ Status }}

Field Details
Description Measures the rate of Nrf forward response received. This is based on {{ Status }} of Nrf Forward Response.

For more information about metric used, see NRF Gateways Metrics.

Expression sum(irate(oc_egressgateway_http_responses_total{namespace="$namespace",Method="GET",NFServiceType="nnrf-disc"}[2m])) by(Status)

Table 6-316 Egress Gateway Response for SLF Response {{ Status }}

Field Details
Description Measures the rate of SLF forward response received. This is based on {{ Status }} of SLF response.

For more information about metric used, see NRF Gateways Metrics.

Expression sum(irate(oc_egressgateway_http_responses_total{namespace="$namespace",Method="GET",NFServiceType="nudr-group-id-map"}[2m])) by(Status)

Table 6-317 Ingress Request Rate

Field Details
Description Measures the rate of incoming requests at NRF.

For more information about metric used, see NRF Gateways Metrics.

Expression sum(irate(oc_ingressgateway_http_requests_total{container="ingressgateway",namespace="$namespace"}[2m]))

Table 6-318 Response with 2xx status code

Field Details
Description Measures the rate of outgoing response with 2xx status code.

For more information about metric used, see NRF Gateways Metrics.

Expression sum(irate(oc_ingressgateway_http_responses_total{Status=~"2.*",container="ingressgateway",namespace="$namespace"}[5m]))

Table 6-319 Response with 4xx status code

Field Details
Description Measures the rate of outgoing response with 4xx status code.

For more information about metric used, see NRF Gateways Metrics.

Expression sum(irate(oc_ingressgateway_http_responses_total{Status=~"4.*",container="ingressgateway",namespace="$namespace"}[5m]))

Table 6-320 Response with 5xx status code

Field Details
Description Measures the rate of outgoing response with 5xx status code.

For more information about metric used, see NRF Gateways Metrics.

Expression sum(irate(oc_ingressgateway_http_responses_total{Status=~"5.*",container="ingressgateway",namespace="$namespace"}[5m]))

Table 6-321 NRF Outgoing Response

Field Details
Description Measures the rate of outgoing requests at NRF.

For more information about metric used, see NRF Gateways Metrics.

Expression sum(irate(oc_ingressgateway_http_responses_total{app_kubernetes_io_name=\"ingressgateway\",kubernetes_namespace=\"$namespace\"}[5m]))

Table 6-322 Egress Request Rate

Field Details
Description Measures the rate of outgoing requests at NRF.

For more information about metric used, see NRF Gateways Metrics.

Expression sum(irate(oc_egressgateway_http_requests_total{namespace="$namespace"}[5m]))

Table 6-323 Response with 2xx status code

Field Details
Description Measures the rate of outgoing response with 2xx status code.

For more information about metric used, see NRF Gateways Metrics.

Expression sum(irate(oc_egressgateway_http_responses_total{Status=~"2.*",namespace="$namespace",Direction="egress"}[5m]))

Table 6-324 Response with 4xx status code

Field Details
Description Measures the rate of outgoing response with 4xx status code.

For more information about metric used, see NRF Gateways Metrics.

Expression sum(irate(oc_egressgateway_http_responses_total{Status=~"4.*",namespace="$namespace",Direction="egress"}[5m]))

Table 6-325 Response with 5xx status code

Field Details
Description Measures the rate of outgoing response with 5xx status code.

For more information about metric used, see NRF Gateways Metrics.

Expression sum(irate(oc_egressgateway_http_responses_total{Status=~"5.*",namespace="$namespace",Direction="egress"}[5m]))

Table 6-326 Egress Response Rate

Field Details
Description Measures the rate of outgoing requests at NRF.

For more information about metric used, see NRF Gateways Metrics.

Expression sum(irate(oc_egressgateway_http_responses_total{namespace="$namespace",Direction="egressOut"}[5m]))

Table 6-327 Ingress Request Rate

Field Details
Description This metric is pegged for every event occurred when a request is sent to Ingress Gateway.

For more information about metric used, see NRF Gateways Metrics.

Expression sum(irate(oc_ingressgateway_jetty_request_stat_metrics_total{event="onCommit",app_kubernetes_io_name="ingressgateway",namespace="$namespace"}[2m])) by (pod)

Table 6-328 Ingress Response Rate

Field Details
Description This metric is pegged for every event occurred when a response is received from Ingress Gateway.

For more information about metric used, see NRF Gateways Metrics.

Expression sum(irate(oc_ingressgateway_jetty_response_stat_metrics_total{event="onComplete",app_kubernetes_io_name="ingressgateway",namespace="$namespace"}[2m])) by (pod)

Table 6-329 Total Incoming Connections at Pod

Field Details
Description Measures the total number of active incoming connections per Egress Gateway pod.

For more information about metric used, see NRF Gateways Metrics.

Expression sum by (pod) (oc_egressgateway_incoming_connections{namespace="$namespace"})

Table 6-330 Total Incoming Connections

Field Details
Description Measures the total number of active incoming connections from client to Egress Gateway.

For more information about metric used, see NRF Gateways Metrics.

Expression sum (oc_egressgateway_incoming_connections{namespace="$namespace"})

Table 6-331 Total Outgoing Connections at pod

Field Details
Description Measures the total number of active outgoing connections per Egress Gateway pod. For more information about metric used, see NRF Gateways Metrics.
Expression sum by (pod) (oc_egressgateway_outgoing_connections{namespace="$namespace"})

Table 6-332 Total Outgoing Connections

Field Details
Description Measures the total number of active outgoing connections from Egress Gateway. For more information about metric used, see NRF Gateways Metrics.
Expression sum (oc_egressgateway_outgoing_connections{namespace="$namespace"})

Table 6-333 Total Incoming Connections at Pod

Field Details
Description Measures the total number of active incoming connections per Ingress Gateway pod.

For more information about metric used, see NRF Gateways Metrics.

Expression sum by (pod) (oc_ingressgateway_incoming_connections{namespace="$namespace"})

Table 6-334 Total Incoming Connections

Field Details
Description Measures the total number of active incoming connections from client to Ingress Gateway.

For more information about metric used, see NRF Gateways Metrics.

Expression sum (oc_ingressgateway_incoming_connections{namespace="$namespace"})

Table 6-335 Total Outgoing Connections at pod

Field Details
Description Measures the total number of active outgoing connections per Ingress Gateway pod. For more information about metric used, see NRF Gateways Metrics.
Expression sum by (pod) (oc_ingressgateway_outgoing_connections{namespace="$namespace"})

Table 6-336 Total Outgoing Connections

Field Details
Description Measures the total number of active outgoing connections from Ingress Gateway. For more information about metric used, see NRF Gateways Metrics.
Expression sum (oc_ingressgateway_outgoing_connections{namespace="$namespace"})

Table 6-337 SLF Egress Gateway Latency 99%

Field Details
Description Measures the number of SLF request falling in 99 percentile of the latency value at Egress Gateway.
Expression avg(oc_egressgateway_request_latency_seconds{namespace="$namespace",Method="GET",quantile="0.99"})

Table 6-338 SLF Egress Gateway Latency 95%

Field Details
Description Measures the number of SLF request falling in 95 percentile of the latency value at Egress Gateway.
Expression avg(oc_egressgateway_request_latency_seconds{namespace="$namespace",Method="GET",quantile="0.95"})

Table 6-339 SLF Egress Gateway Latency 90%

Field Details
Description Measures the number of SLF request falling in 90 percentile of the latency value at Egress Gateway.
Expression avg(oc_egressgateway_request_latency_seconds{namespace="$namespace",Method="GET",quantile="0.90"})

Table 6-340 SLF Egress Gateway Latency 50%

Field Details
Description Measures the number of SLF request falling in 50 percentile of the latency value at Egress Gateway.
Expression avg(oc_egressgateway_request_latency_seconds{namespace="$namespace",Method="GET",quantile="0.50"})

Table 6-341 NfAccess Token Latency 99%

Field Details
Description Measures the average amount of time taken for processing NfAccess token latency falling in 99 percentile of the latency value.
Expression avg(oc_ingressgateway_request_processing_latency_seconds{namespace="$namespace",Route_path="/oauth2/token",Method="POST",quantile="0.99"})

Table 6-342 NfAccess Token Latency 95%

Field Details
Description Measures the average amount of time taken for processing NfAccess token latency falling in 95 percentile of the latency value.
Expression avg(oc_ingressgateway_request_processing_latency_seconds{namespace="$namespace",Route_path="/oauth2/token",Method="POST",quantile="0.95"})

Table 6-343 NfAccess Token Latency 90%

Field Details
Description Measures the average amount of time taken for processing NfAccess token latency falling in 90 percentile of the latency value.
Expression avg(oc_ingressgateway_request_processing_latency_seconds{namespace="$namespace",Route_path="/oauth2/token",Method="POST",quantile="0.90"})

Table 6-344 NfAccess Token Latency 50%

Field Details
Description Measures the average amount of time taken for processing NfAccess token latency falling in 50 percentile of the latency value.
Expression avg(oc_ingressgateway_request_processing_latency_seconds{namespace="$namespace",Route_path="/oauth2/token",Method="POST",quantile="0.50"})

Table 6-345 Discovery SLF Latency 99%

Field Details
Description Measures the number of SLF discovery request falling in 99 percentile of the latency value.
Expression avg(ocnrf_slf_jetty_latency_seconds{namespace="$namespace",ServiceOperation="NfDiscover",quantile="0.99"})

Table 6-346 Discovery SLF Latency 90%

Field Details
Description Measures the number of SLF discovery request falling in 90 percentile of the latency value.
Expression avg(ocnrf_slf_jetty_latency_seconds{namespace="$namespace",ServiceOperation="NfDiscover",quantile="0.9"})

Table 6-347 Discovery SLF Latency 50%

Field Details
Description Measures the number of SLF discovery request falling in 50 percentile of the latency value.
Expression avg(ocnrf_slf_jetty_latency_seconds{namespace="$namespace",ServiceOperation="NfDiscover",quantile="0.5"})

Table 6-348 Discovery SLF Latency 95%

Field Details
Description Measures the number of SLF discovery request falling in 95 percentile of the latency value.
Expression avg(ocnrf_slf_jetty_latency_seconds{namespace="$namespace",ServiceOperation="NfDiscover",quantile="0.95"})

Table 6-349 Discovery Latency 99%

Field Details
Description Measures the number of discovery request falling in 99 percentile of the latency value.
Expression avg(ocnrf_message_processing_time_seconds{namespace="$namespace",ServiceOperation="NfDiscover",quantile="0.99"})

Table 6-350 Discovery Latency 90%

Field Details
Description Measures the number of discovery request falling in 90 percentile of the latency value.
Expression avg(ocnrf_message_processing_time_seconds{namespace="$namespace",ServiceOperation="NfDiscover",quantile="0.9"})

Table 6-351 Discovery Latency 50%

Field Details
Description Measures the number of discovery request falling in 50 percentile of the latency value.
Expression avg(ocnrf_message_processing_time_seconds{namespace="$namespace",ServiceOperation="NfDiscover",quantile="0.5"})

Table 6-352 Discovery Latency 95%

Field Details
Description Measures the number of discovery request falling in 95 percentile of the latency value.
Expression avg(ocnrf_message_processing_time_seconds{namespace="$namespace",ServiceOperation="NfDiscover",quantile="0.95"})

Table 6-353 Ingress Gateway Discovery Latency 99%

Field Details
Description Measures the number of discovery request falling in 99 percentile of the latency value at Ingress Gateway.
Expression avg(oc_ingressgateway_request_processing_latency_seconds{namespace="$namespace",Route_path="/nnrf-disc/v1/nf-instances/**",quantile="0.99"})

Table 6-354 Ingress Gateway Discovery Latency 90%

Field Details
Description Measures the number of discovery request falling in 90 percentile of the latency value at Ingress Gateway.
Expression avg(oc_ingressgateway_request_processing_latency_seconds{namespace="$namespace",Route_path="/nnrf-disc/v1/nf-instances/**",quantile="0.9"})

Table 6-355 Ingress Gateway Discovery Latency 50%

Field Details
Description Measures the number of discovery request falling in 50 percentile of the latency value at Ingress Gateway.
Expression avg(oc_ingressgateway_request_processing_latency_seconds{namespace="$namespace",Route_path="/nnrf-disc/v1/nf-instances/**",quantile="0.5"})

Table 6-356 Ingress Gateway Discovery Latency 95%

Field Details
Description Measures the number of discovery request falling in 95 percentile of the latency value at Ingress Gateway.
Expression avg(oc_ingressgateway_request_processing_latency_seconds{namespace="$namespace",Route_path="/nnrf-disc/v1/nf-instances/**",quantile="0.95"})

Table 6-357 Ingress Gateway Backend Latency 99%

Field Details
Description Measures the number of request falling in 99 percentile of the latency value at Ingress Gateway backend.
Expression avg(oc_ingressgateway_server_latency_seconds{namespace="$namespace",quantile="0.99",Method="GET"})

Table 6-358 Ingress Gateway Backend Latency 95%

Field Details
Description Measures the number of request falling in 95 percentile of the latency value at Ingress Gateway backend.
Expression avg(oc_ingressgateway_server_latency_seconds{namespace="$namespace",quantile="0.95",Method="GET"})

Table 6-359 Ingress Gateway Backend Latency 90%

Field Details
Description Measures the number of request falling in 90 percentile of the latency value at Ingress Gateway backend.
Expression avg(oc_ingressgateway_server_latency_seconds{namespace="$namespace",quantile="0.9",Method="GET"})

Table 6-360 Discovery Cache Sync

Field Details
Description Measures the rate at which in-memory cache entries in the nfdiscovery are synched with Cache Data Service.
Expression sum(rate(ocnrf_cache_sync_count_total{namespace="$namespace",container="nfdiscovery"}[2m]))

Table 6-361 Ingress Gateway Backend Latency 50%

Field Details
Description Measures the number of request falling in 50 percentile of the latency value at Ingress Gateway backend.
Expression avg(oc_ingressgateway_server_latency_seconds{namespace="$namespace",quantile="0.5",Method="GET"})

Table 6-362 Ingress Gateway Latency 99%

Field Details
Description Measures the number of request falling in 99 percentile of the latency value at Ingress Gateway.
Expression avg(oc_ingressgateway_request_latency_seconds{namespace="$namespace",quantile="0.99",Method="GET"})

Table 6-363 Ingress Gateway Latency 95%

Field Details
Description Measures the number of request falling in 95 percentile of the latency value at Ingress Gateway.
Expression avg(oc_ingressgateway_request_latency_seconds{namespace="$namespace",quantile="0.95",Method="GET"})

Table 6-364 Ingress Gateway Latency 90%

Field Details
Description Measures the number of request falling in 90 percentile of the latency value at Ingress Gateway.
Expression avg(oc_ingressgateway_request_latency_seconds{namespace="$namespace",quantile="0.9",Method="GET"})

Table 6-365 Ingress Gateway Latency 50%

Field Details
Description Measures the number of request falling in 50 percentile of the latency value at Ingress Gateway.
Expression avg(oc_ingressgateway_request_latency_seconds{namespace="$namespace",quantile="0.5",Method="GET"})

Table 6-366 Forward Latency 99%

Field Details
Description Measures the number of forward request falling in 99 percentile of the latency value.
Expression avg(ocnrf_forward_jetty_latency_seconds{namespace="$namespace",ServiceOperation="NfDiscover",quantile="0.99"})

Table 6-367 Forward Latency 95%

Field Details
Description Measures the number of forward request falling in 95 percentile of the latency value.
Expression avg(ocnrf_forward_jetty_latency_seconds{namespace="$namespace",ServiceOperation="NfDiscover",quantile="0.95"})

Table 6-368 Forward Latency 90%

Field Details
Description Measures the number of forward request falling in 90 percentile of the latency value.
Expression avg(ocnrf_forward_jetty_latency_seconds{namespace="$namespace",ServiceOperation="NfDiscover",quantile="0.9"})

Table 6-369 Forward Latency 50%

Field Details
Description Measures the number of forward request falling in 50 percentile of the latency value.
Expression avg(ocnrf_forward_jetty_latency_seconds{namespace="$namespace",ServiceOperation="NfDiscover",quantile="0.5"})

Table 6-370 NfStatusSubscribe Latency 99%

Field Details
Description Measures the number of NF status subscription request falling in 99 percentile of the latency value.
Expression avg(oc_ingressgateway_request_processing_latency_seconds{namespace="$namespace",Route_path="/nnrf-nfm/v1/subscriptions/**",Method="POST",quantile="0.99"})

Table 6-371 NfStatusSubscribe Latency 95%

Field Details
Description Measures the number of NF status subscription request falling in 95 percentile of the latency value.
Expression avg(oc_ingressgateway_request_processing_latency_seconds{namespace="$namespace",Route_path="/nnrf-nfm/v1/subscriptions/**",Method="POST",quantile="0.95"})

Table 6-372 NfStatusSubscribe Latency 90%

Field Details
Description Measures the number of NF status subscription request falling in 90 percentile of the latency value.
Expression avg(oc_ingressgateway_request_processing_latency_seconds{namespace="$namespace",Route_path="/nnrf-nfm/v1/subscriptions/**",Method="POST",quantile="0.9"})

Table 6-373 NfStatusSubscribe Latency 50%

Field Details
Description Measures the number of NF status subscription request falling in 50 percentile of the latency value.
Expression avg(oc_ingressgateway_request_processing_latency_seconds{namespace="$namespace",Route_path="/nnrf-nfm/v1/subscriptions/**",Method="POST",quantile="0.5"})

Table 6-374 NfStatusSubscribe Latency (PATCH) 99%

Field Details
Description Measures the number of NF status subscription (PATCH) request falling in 99 percentile of the latency value.
Expression avg(oc_ingressgateway_request_processing_latency_seconds{namespace="$namespace",Route_path="/nnrf-nfm/v1/subscriptions/**",Method="PATCH",quantile="0.99"})

Table 6-375 NfStatusSubscribe Latency (PATCH) 95%

Field Details
Description Measures the number of NF status subscription (PATCH) request falling in 95 percentile of the latency value.
Expression avg(oc_ingressgateway_request_processing_latency_seconds{namespace="$namespace",Route_path="/nnrf-nfm/v1/subscriptions/**",Method="PATCH",quantile="0.95"})

Table 6-376 NfStatusSubscribe Latency (PATCH) 90%

Field Details
Description Measures the number of NF status subscription (PATCH) request falling in 90 percentile of the latency value.
Expression avg(oc_ingressgateway_request_processing_latency_seconds{namespace="$namespace",Route_path="/nnrf-nfm/v1/subscriptions/**",Method="PATCH",quantile="0.90"})

Table 6-377 NfStatusSubscribe Latency (PATCH) 50%

Field Details
Description Measures the number of NF status subscription (PATCH) request falling in 50 percentile of the latency value.
Expression avg(oc_ingressgateway_request_processing_latency_seconds{namespace="$namespace",Route_path="/nnrf-nfm/v1/subscriptions/**",Method="PATCH",quantile="0.50"})

Table 6-378 NfStatusUnsubscribe Latency 99%

Field Details
Description Measures the number of status unsubscription request falling in 99 percentile of the latency value.
Expression avg(oc_ingressgateway_request_processing_latency_seconds{namespace="$namespace",Route_path="/nnrf-nfm/v1/subscriptions/**",Method="DELETE",quantile="0.99"})

Table 6-379 NfStatusUnsubscribe Latency 95%

Field Details
Description Measures the number of status unsubscription request falling in 95 percentile of the latency value.
Expression avg(oc_ingressgateway_request_processing_latency_seconds{namespace="$namespace",Route_path="/nnrf-nfm/v1/subscriptions/**",Method="DELETE",quantile="0.95"})

Table 6-380 NfStatusUnsubscribe Latency 90%

Field Details
Description Measures the number of status unsubscription request falling in 90 percentile of the latency value.
Expression avg(oc_ingressgateway_request_processing_latency_seconds{namespace="$namespace",Route_path="/nnrf-nfm/v1/subscriptions/**",Method="DELETE",quantile="0.90"})

Table 6-381 NfStatusUnsubscribe Latency 50%

Field Details
Description Measures the number of status unsubscription request falling in 50 percentile of the latency value.
Expression avg(oc_ingressgateway_request_processing_latency_seconds{namespace="$namespace",Route_path="/nnrf-nfm/v1/subscriptions/**",Method="DELETE",quantile="0.50"})

Table 6-382 NfNotification trigger Success

Field Details
Description Measures the rate of success notification trigger sent to nfSubscription service from the nfregistration and nrfauditor services.
Expression sum(rate(ocnrf_nfNotification_trigger_total{errorReason="noError",namespace="$namespace"}[2m]))

Table 6-383 NfNotification trigger Failure

Field Details
Description Measures the rate of error notification trigger sent to nfSubscription service from the nfregistration and nrfauditor services.
Expression sum(rate(ocnrf_nfNotification_trigger_total{errorReason!="noError",namespace="$namespace"}[2m]))

Table 6-384 NfUpdate Latency 99%

Field Details
Description Measures the number of update request falling in 99 percentile of the latency value.
Expression avg(oc_ingressgateway_request_processing_latency_seconds{namespace="$namespace",Route_path="/nnrf-nfm/v1/nf-instances/**",Method="PATCH",quantile="0.99"})

Table 6-385 NfUpdate Latency 95%

Field Details
Description Measures the number of update request falling in 95 percentile of the latency value.
Expression avg(oc_ingressgateway_request_processing_latency_seconds{namespace="$namespace",Route_path="/nnrf-nfm/v1/nf-instances/**",Method="PATCH",quantile="0.95"})

Table 6-386 NfUpdate Latency 90%

Field Details
Description Measures the number of update request falling in 90 percentile of the latency value.
Expression avg(oc_ingressgateway_request_processing_latency_seconds{namespace="$namespace",Route_path="/nnrf-nfm/v1/nf-instances/**",Method="PATCH",quantile="0.9"})

Table 6-387 NfUpdate Latency 50%

Field Details
Description Measures the number of update request falling in 50 percentile of the latency value.
Expression avg(oc_ingressgateway_request_processing_latency_seconds{namespace="$namespace",Route_path="/nnrf-nfm/v1/nf-instances/**",Method="PATCH",quantile="0.5"})

Table 6-388 NfRegister Latency 99%

Field Details
Description Measures the number of register request falling in 99 percentile of the latency value.
Expression avg(oc_ingressgateway_request_processing_latency_seconds{namespace="$namespace",Route_path="/nnrf-nfm/v1/nf-instances/**",Method="PUT",quantile="0.99"})

Table 6-389 NfRegister Latency 95%

Field Details
Description Measures the number of register request falling in 95 percentile of the latency value.
Expression avg(oc_ingressgateway_request_processing_latency_seconds{namespace="$namespace",Route_path="/nnrf-nfm/v1/nf-instances/**",Method="PUT",quantile="0.95"})

Table 6-390 NfRegister Latency 90%

Field Details
Description Measures the number of register request falling in 90 percentile of the latency value.
Expression avg(oc_ingressgateway_request_processing_latency_seconds{namespace="$namespace",Route_path="/nnrf-nfm/v1/nf-instances/**",Method="PUT",quantile="0.9"})

Table 6-391 NfRegister Latency 50%

Field Details
Description Measures the number of register request falling in 50 percentile of the latency value.
Expression avg(oc_ingressgateway_request_processing_latency_seconds{namespace="$namespace",Route_path="/nnrf-nfm/v1/nf-instances/**",Method="PUT",quantile="0.5"})

Table 6-392 NfDeregister Latency 99%

Field Details
Description Measures the number of deregister request falling in 99 percentile of the latency value.
Expression avg(oc_ingressgateway_request_processing_latency_seconds{namespace="$namespace",Route_path="/nnrf-nfm/v1/nf-instances/**",Method="DELETE",quantile="0.99"})

Table 6-393 NfDeregister Latency 95%

Field Details
Description Measures the number of deregister request falling in 95 percentile of the latency value.
Expression avg(oc_ingressgateway_request_processing_latency_seconds{namespace="$namespace",Route_path="/nnrf-nfm/v1/nf-instances/**",Method="DELETE",quantile="0.95"})

Table 6-394 NfDeregister Latency 90%

Field Details
Description Measures the number of deregister request falling in 90 percentile of the latency value.
Expression avg(oc_ingressgateway_request_processing_latency_seconds{namespace="$namespace",Route_path="/nnrf-nfm/v1/nf-instances/**",Method="DELETE",quantile="0.90"})

Table 6-395 NfDeregister Latency 50%

Field Details
Description Measures the number of deregister request falling in 50 percentile of the latency value.
Expression avg(oc_ingressgateway_request_processing_latency_seconds{namespace="$namespace",Route_path="/nnrf-nfm/v1/nf-instances/**",Method="DELETE",quantile="0.50"})

Table 6-396 NfDiscovery Database Latency 99%

Field Details
Description Measures the number of discovery request falling in 99 percentile of the latency value.
Expression avg(ocnrf_dbmetrics_round_trip_time_seconds{namespace="$namespace",tableName="NfInstances",serviceOperation="NfDiscover",quantile="0.99"})

Table 6-397 NfDiscovery Database Latency 95%

Field Details
Description Measures the number of discovery request falling in 95 percentile of the latency value.
Expression avg(ocnrf_dbmetrics_round_trip_time_seconds{namespace="$namespace",tableName="NfInstances",serviceOperation="NfDiscover",quantile="0.95"})

Table 6-398 NfDiscovery Database Latency 90%

Field Details
Description Measures the number of discovery request falling in 90 percentile of the latency value.
Expression avg(ocnrf_dbmetrics_round_trip_time_seconds{namespace="$namespace",tableName="NfInstances",serviceOperation="NfDiscover",quantile="0.90"})

Table 6-399 NfDiscovery Database Latency 50%

Field Details
Description Measures the number of discovery request falling in 50 percentile of the latency value.
Expression avg(ocnrf_dbmetrics_round_trip_time_seconds{namespace="$namespace",tableName="NfInstances",serviceOperation="NfDiscover",quantile="0.50"})

Table 6-400 NfRegistration Database Latency 99%

Field Details
Description Measures the number of NfRegistration request falling in 99 percentile of the latency value.
Expression avg(ocnrf_dbmetrics_round_trip_time_seconds{namespace="$namespace",tableName="NfInstances",serviceOperation="NfRegister",quantile="0.99"})

Table 6-401 NfRegistration Database Latency 95%

Field Details
Description Measures the number of NfRegistration request falling in 95 percentile of the latency value.
Expression avg(ocnrf_dbmetrics_round_trip_time_seconds{namespace="$namespace",tableName="NfInstances",serviceOperation="NfRegister",quantile="0.95"})

Table 6-402 NfRegistration Database Latency 90%

Field Details
Description Measures the number of NfRegistration request falling in 90 percentile of the latency value.
Expression avg(ocnrf_dbmetrics_round_trip_time_seconds{namespace="$namespace",tableName="NfInstances",serviceOperation="NfRegister",quantile="0.90"})

Table 6-403 NfRegistration Database Latency 50%

Field Details
Description Measures the number of NfRegistration request falling in 50 percentile of the latency value.
Expression avg(ocnrf_dbmetrics_round_trip_time_seconds{namespace="$namespace",tableName="NfInstances",serviceOperation="NfRegister",quantile="0.50"})

Table 6-404 NfUpdate Database Latency 99%

Field Details
Description Measures the number of NfUpdate request falling in 99 percentile of the latency value.
Expression avg(ocnrf_dbmetrics_round_trip_time_seconds{namespace="$namespace",tableName="NfInstances",serviceOperation="NfUpdate",quantile="0.99"})

Table 6-405 NfUpdate Database Latency 95%

Field Details
Description Measures the number of NfUpdate request falling in 95 percentile of the latency value.
Expression avg(ocnrf_dbmetrics_round_trip_time_seconds{namespace="$namespace",tableName="NfInstances",serviceOperation="NfUpdate",quantile="0.95"})

Table 6-406 NfUpdate Database Latency 90%

Field Details
Description Measures the number of NfUpdate request falling in 90 percentile of the latency value.
Expression avg(ocnrf_dbmetrics_round_trip_time_seconds{namespace="$namespace",tableName="NfInstances",serviceOperation="NfUpdate",quantile="0.90"})

Table 6-407 NfUpdate Database Latency 50%

Field Details
Description Measures the number of NfUpdate request falling in 50 percentile of the latency value.
Expression avg(ocnrf_dbmetrics_round_trip_time_seconds{namespace="$namespace",tableName="NfInstances",serviceOperation="NfUpdate",quantile="0.50"})

Table 6-408 NfHeartBeat Database Latency 99%

Field Details
Description Measures the number of NfHeartBeat request falling in 99 percentile of the latency value.
Expression avg(ocnrf_dbmetrics_round_trip_time_seconds{namespace="$namespace",tableName="NfInstances",serviceOperation="NfHeartBeat",quantile="0.99"})

Table 6-409 NfHeartBeat Database Latency 95%

Field Details
Description Measures the number of NfHeartBeat request falling in 95 percentile of the latency value.
Expression avg(ocnrf_dbmetrics_round_trip_time_seconds{namespace="$namespace",tableName="NfInstances",serviceOperation="NfHeartBeat",quantile="0.95"})

Table 6-410 NfHeartBeat Database Latency 90%

Field Details
Description Measures the number of NfHeartBeat request falling in 90 percentile of the latency value.
Expression avg(ocnrf_dbmetrics_round_trip_time_seconds{namespace="$namespace",tableName="NfInstances",serviceOperation="NfHeartBeat",quantile="0.9"})

Table 6-411 NfHeartBeat Database Latency 50%

Field Details
Description Measures the number of NfHeartBeat request falling in 50 percentile of the latency value.
Expression avg(ocnrf_dbmetrics_round_trip_time_seconds{namespace="$namespace",tableName="NfInstances",serviceOperation="NfHeartBeat",quantile="0.5"})

Table 6-412 NfDeregister Database Latency 99%

Field Details
Description Measures the number of NfDeregister request falling in 99 percentile of the latency value.
Expression avg(ocnrf_dbmetrics_round_trip_time_seconds{namespace="$namespace",tableName="NfInstances",serviceOperation="NfDeregister",quantile="0.99"})

Table 6-413 NfDeregister Database Latency 95%

Field Details
Description Measures the number of NfDeregister request falling in 95 percentile of the latency value.
Expression avg(ocnrf_dbmetrics_round_trip_time_seconds{namespace="$namespace",tableName="NfInstances",serviceOperation="NfDeregister",quantile="0.95"})

Table 6-414 NfDeregister Database Latency 90%

Field Details
Description Measures the number of NfDeregister request falling in 90 percentile of the latency value.
Expression avg(ocnrf_dbmetrics_round_trip_time_seconds{namespace="$namespace",tableName="NfInstances",serviceOperation="NfDeregister",quantile="0.90"})

Table 6-415 NfDeregister Database Latency 50%

Field Details
Description Measures the number of NfDeregister request falling in 50 percentile of the latency value.
Expression avg(ocnrf_dbmetrics_round_trip_time_seconds{namespace="$namespace",tableName="NfInstances",serviceOperation="NfDeregister",quantile="0.50"})

Table 6-416 NfSubscribe Database Latency 99%

Field Details
Description Measures the number of NfSubscribe request falling in 99 percentile of the latency value.
Expression avg(ocnrf_dbmetrics_round_trip_time_seconds{namespace="$namespace",tableName="NfInstances",serviceOperation="NfSubscribe",quantile="0.99"})

Table 6-417 NfSubscribe Database Latency 95%

Field Details
Description Measures the number of NfSubscribe request falling in 95 percentile of the latency value.
Expression avg(ocnrf_dbmetrics_round_trip_time_seconds{namespace="$namespace",tableName="NfInstances",serviceOperation="NfSubscribe",quantile="0.95"})

Table 6-418 NfSubscribe Database Latency 90%

Field Details
Description Measures the number of NfSubscribe request falling in 90 percentile of the latency value.
Expression avg(ocnrf_dbmetrics_round_trip_time_seconds{namespace="$namespace",tableName="NfInstances",serviceOperation="NfSubscribe",quantile="0.90"})

Table 6-419 NfSubscribe Database Latency 50%

Field Details
Description Measures the number of NfSubscribe request falling in 50 percentile of the latency value.
Expression avg(ocnrf_dbmetrics_round_trip_time_seconds{namespace="$namespace",tableName="NfInstances",serviceOperation="NfSubscribe",quantile="0.50"})

Table 6-420 NfUnsubscribe Database Latency 99%

Field Details
Description Measures the number of NfUnsubscribe request falling in 99 percentile of the latency value.
Expression avg(ocnrf_dbmetrics_round_trip_time_seconds{namespace="$namespace",tableName="NfSubscriptions",serviceOperation="NfUnsubscribe",quantile="0.99"})

Table 6-421 NfStatusNotify Database Latency 99%

Field Details
Description Measures the number of NfStatusNotify request falling in 99 percentile of the latency value.
Expression avg(ocnrf_dbmetrics_round_trip_time_seconds{namespace="$namespace",tableName="NfSubscriptions",serviceOperation="NfStatusNotify",quantile="0.99"})

Table 6-422 NfStatusNotify Database Latency 95%

Field Details
Description Measures the number of NfStatusNotify request falling in 95 percentile of the latency value.
Expression avg(ocnrf_dbmetrics_round_trip_time_seconds{namespace="$namespace",tableName="NfSubscriptions",serviceOperation="NfStatusNotify",quantile="0.95"})

Table 6-423 NfStatusNotify Database Latency 90%

Field Details
Description Measures the number of NfStatusNotify request falling in 90 percentile of the latency value.
Expression avg(ocnrf_dbmetrics_round_trip_time_seconds{namespace="$namespace",tableName="NfSubscriptions",serviceOperation="NfStatusNotify",quantile="0.90"})

Table 6-424 NfStatusNotify Database Latency 50%

Field Details
Description Measures the number of NfStatusNotify request falling in 50 percentile of the latency value.
Expression avg(ocnrf_dbmetrics_round_trip_time_seconds{namespace="$namespace",tableName="NfSubscriptions",serviceOperation="NfStatusNotify",quantile="0.50"})

Table 6-425 NfAccessToken Database Latency 99%

Field Details
Description Measures the number of NfAccessToken request falling in 99 percentile of the latency value.
Expression avg(ocnrf_dbmetrics_round_trip_time_seconds{namespace="$namespace",tableName="NfInstances",serviceOperation="NfAccessToken",quantile="0.99"})

Table 6-426 NfAccessToken Database Latency 95%

Field Details
Description Measures the number of NfAccessToken request falling in 95 percentile of the latency value.
Expression avg(ocnrf_dbmetrics_round_trip_time_seconds{namespace="$namespace",tableName="NfInstances",serviceOperation="NfAccessToken",quantile="0.95"})

Table 6-427 NfAccessToken Database Latency 90%

Field Details
Description Measures the number of NfAccessToken request falling in 90 percentile of the latency value.
Expression avg(ocnrf_dbmetrics_round_trip_time_seconds{namespace="$namespace",tableName="NfInstances",serviceOperation="NfAccessToken",quantile="0.90"})

Table 6-428 NfAccessToken Database Latency 50%

Field Details
Description Measures the number of NfAccessToken request falling in 50 percentile of the latency value.
Expression avg(ocnrf_dbmetrics_round_trip_time_seconds{namespace="$namespace",tableName="NfInstances",serviceOperation="NfAccessToken",quantile="0.50"})

Note:

For example, if min is 0 and max is 100, the number of request falling in 95 percentile, which is quantile="0.95", is measured in the Latency 95% KPI.

Table 6-429 NF Profile Size Average

Field Details
Description Measures the average size of the NF profiles registered at NRF.

For more information about metric used, see NRF NF Metrics.
Expression avg by (NfType) (ocnrf_nf_profile_size{namespace="$namespace"}))

Table 6-430 NF Profile Size Max

Field Details
Description Measures the maximum size of the NF profiles registered at NRF.

For more information about metric used, see NRF NF Metrics.
Expression max by (NfType) (ocnrf_nf_profile_size{namespace="$namespace"})

Table 6-431 Discovery Response Size

Field Details
Description Measures the NfDiscovery response size.

For more information about metric used, see NRF NF Metrics.

Expression histogram_quantile(0.99,sum(rate(ocnrf_nfDiscover_tx_response_size_bytes_bucket{namespace="$namespace",TargetNfType="<NF>"}[2m])) by (TargetNfType,le))

Where, <NF>- Name of Network Function. (For example, AUSF, AMF, CHF)

For example,

histogram_quantile(0.99, sum(rate(ocnrf_nfDiscover_tx_response_size_bytes_bucket{namespace="$namespace",TargetNfType="AMF"}[2m])) by (TargetNfType,le))

Table 6-432 NF Profile Size Limit Breached

Field Details
Description Measures the rate of requests rejected due to breach in nfProfile size limit.
Expression sum(rate(ocnrf_nfProfile_size_limit_breached_total{namespace="$namespace"}[2m])) by (NfInstanceId, ServiceOperation)

6.2.2 Resource Usage KPIs

This section lists the KPIs to measure the CPU, Memory usage, and Kubernetes Horizontal Pod Autoscaling (HPA) counts at NRF. These KPIs are calculated based on Kubernetes metrics.

Table 6-433 nfregistration

Field Details
Description Measures the amount of CPU resources consumed by the containers for nfregistration service.
Expression sum(rate(container_cpu_usage_seconds_total{container="nfregistration",namespace="$namespace"}[2m]))

Table 6-434 nfsubscription

Field Details
Description Measures the amount of CPU resources consumed by the containers for nfsubscription service.
Expression sum(rate(container_cpu_usage_seconds_total{container="nfsubscription",namespace="$namespace"}[2m]))

Table 6-435 nfdiscovery

Field Details
Description Measures the amount of CPU resources consumed by the containers for nfdiscovery service.
Expression sum(rate(container_cpu_usage_seconds_total{container="nfdiscovery",namespace="$namespace"}[2m]))

Table 6-436 nrfauditor

Field Details
Description Measures the amount of CPU resources consumed by the containers for nrfauditor service.
Expression sum(rate(container_cpu_usage_seconds_total{container="nrfauditor",namespace="$namespace"}[2m]))

Table 6-437 nfaccesstoken

Field Details
Description Measures the amount of CPU resources consumed by the containers for nfaccesstoken service.
Expression sum(rate(container_cpu_usage_seconds_total{container="nfaccesstoken",namespace="$namespace"}[2m]))

Table 6-438 nrfconfiguration

Field Details
Description Measures the amount of CPU resources consumed by the containers for nrfconfiguration service.
Expression sum(rate(container_cpu_usage_seconds_total{container="nrfconfiguration",namespace="$namespace"}[2m]))

Table 6-439 ingress-gateway

Field Details
Description Measures the amount of CPU resources consumed by the containers for Ingress Gateway service.
Expression sum(rate(container_cpu_usage_seconds_total{container="ingressgateway",namespace="$namespace"}[2m]))

Table 6-440 egress-gateway

Field Details
Description Measures the amount of CPU resources consumed by the containers for Egress Gateway service.
Expression sum(rate(container_cpu_usage_seconds_total{container="egressgateway",namespace="$namespace"}[2m]))

Table 6-441 nfregistration

Field Details
Description Measures the amount of memory consumed by the containers for nfregistration service.
Expression sum (container_memory_usage_bytes{container="nfregistration",namespace="$namespace"})

Table 6-442 nfsubscription

Field Details
Description Measures the amount of memory consumed by the containers for nfsubscription service.
Expression sum (container_memory_usage_bytes{container="nfsubscription",namespace="$namespace"})

Table 6-443 nfdiscovery

Field Details
Description Measures the amount of memory consumed by the containers for nfdiscovery service.
Expression sum (container_memory_usage_bytes{container="nfdiscovery",namespace="$namespace"})

Table 6-444 nrfauditor

Field Details
Description Measures the amount of memory consumed by the containers for nrfauditor service.
Expression sum (container_memory_usage_bytes{container="nrfauditor",namespace="$namespace"})

Table 6-445 nfaccesstoken

Field Details
Description Measures the amount of memory consumed by the containers for nfaccesstoken service.
Expression sum (container_memory_usage_bytes{container="nfaccesstoken",namespace=$namespace"})

Table 6-446 nrfconfiguration

Field Details
Description Measures the amount of memory consumed by the containers for nrfconfiguration service.
Expression sum (container_memory_usage_bytes{container="nrfconfiguration",namespace="$namespace"})

Table 6-447 ingress-gateway

Field Details
Description Measures the amount of memory consumed by the containers for Ingress Gateway service.
Expression sum (container_memory_usage_bytes{container="ingressgateway",namespace="$namespace"})

Table 6-448 egress-gateway

Field Details
Description Measures the amount of memory consumed by the containers for Egress Gateway service.
Expression sum (container_memory_usage_bytes{container="egressgateway",namespace="$namespace"})

Table 6-449 ocnrf-ingressgateway

Field Details
Description Measures the number of Ingress Gateway replicas currently available and managed by the autoscaler.
Expression kube_horizontalpodautoscaler_status_current_replicas{namespace="$namespace",horizontalpodautoscaler=~".*-ingressgateway.*"}

Table 6-450 ocnrf-nfregistration

Field Details
Description Measures the number of nfregistration replicas currently available and managed by the autoscaler.
Expression kube_horizontalpodautoscaler_status_current_replicas{namespace="$namespace",horizontalpodautoscaler=~".*-nfregistration.*"}

Table 6-451 ocnrf-nfsubscription

Field Details
Description Measures the number of nfsubscription replicas currently available and managed by the autoscaler.
Expression kube_horizontalpodautoscaler_status_current_replicas{namespace="$namespace",horizontalpodautoscaler=~".*-nfsubscription.*"}

Table 6-452 ocnrf-nfdiscovery

Field Details
Description Measures the number of nfdiscovery replicas currently available and managed by the autoscaler.
Expression kube_horizontalpodautoscaler_status_current_replicas{namespace="$namespace",horizontalpodautoscaler=~".*-nfdiscovery.*"}

Table 6-453 ocnrf-nfaccesstoken

Field Details
Description Measures the number of nfaccesstoken replicas currently available and managed by the autoscaler.
Expression kube_horizontalpodautoscaler_status_current_replicas{namespace="$namespace",horizontalpodautoscaler=~".*-nfaccesstoken.*"}

Table 6-454 ocnrf-egressgateway

Field Details
Description Measures the number of egressgateway replicas currently available and managed by the autoscaler.
Expression kube_horizontalpodautoscaler_status_current_replicas{namespace="$namespace",horizontalpodautoscaler=~".*-egressgateway.*"}

6.2.3 Feature Specific KPIs

This section lists the KPIs related to Global Subscription Limit, Pod Protection, NF FQDN validation, Geo redundancy features at NRF. These KPIs are calculated based on Kubernetes metrics.

6.2.3.1 Global Subscription Limit Feature
6.2.3.1.1 Global Subscription Limit Level

Table 6-455 Active Subscriptions

Field Details
Description Measures the total number of active subscriptions.
Expression ocnrf_nfset_active_subscriptions{kubernetes_namespace=\"$namespace\"}

Table 6-456 Subscription Limit level

Field Details
Description Measures the subscription limit.
Expression ocnrf_nfset_limit_level{kubernetes_namespace=\"$namespace\"}
6.2.3.1.2 Subscription Limit Breached

Table 6-457 Total NfStatusSubscribe(Create) Rejected

Field Details
Description Measures the total number of create subscription requests that are rejected.
Expression sum(rate(ocnrf_nfStatusSubscribe_tx_responses_total{namespace="$namespace",RejectionReason="SubscriptionLimitExceeded",OperationType="Create"}[2m]))

Table 6-458 Total NfStatusSubscribe(Update) Rejected

Field Details
Description Measures the total number of update subscription requests that are rejected.
Expression sum(rate(ocnrf_nfStatusSubscribe_tx_responses_total{namespace="$namespace",RejectionReason="SubscriptionLimitExceeded",OperationType="Update"}[2m]))
6.2.3.2 NF FQDN Validation KPIs

This section lists the network function fully qualified domain name (FQDN) validation KPIs at NRF.

Table 6-459 NfRegister - FQDN Validation Failed

Field Details
Description Measures the total number of registration request for which FQDN based authentication failed at NRF. This is based on [ NfFqdn :- {{ NfFqdn}}].

For more information about metric used, see NF Authentication Metrics.

Expression increase(ocnrf_nf_authentication_failure_total{namespace=\"$namespace\",ServiceOperation=\"NfRegister\"}[5m])

Table 6-460 NfSubscribe - FQDN Validation Failed

Field Details
Description Measures the total number of subscription request for which FQDN based authentication failed at NRF. This is based on [ NfFqdn :- {{ NfFqdn}}].

For more information about metric used, see NF Authentication Metrics.

Expression increase(ocnrf_nf_authentication_failure_total{namespace=\"$namespace\",ServiceOperation=\"NfStatusSubscribe\"}[5m])

Table 6-461 NFDiscover - FQDN Validation Failed

Field Details
Description Measures the total number of discovery request for which FQDN based authentication failed at NRF. This is based on [ NfFqdn :- {{ NfFqdn}}].

For more information about metric used, see NF Authentication Metrics.

Expression increase(ocnrf_nf_authentication_failure_total{namespace=\"$namespace\",ServiceOperation=\"NFDiscover\"}[5m])

Table 6-462 NFAccessToken - FQDN Validation Failed

Field Details
Description Measures the total number of access token request for which FQDN based authentication failed at NRF. This is based on [ NfFqdn :- {{ NfFqdn}}].

For more information about metric used, see NF Authentication Metrics.

Expression increase(ocnrf_nf_authentication_failure_total{namespace=\"$namespace\",ServiceOperation=\"NFAccessToken\"}[5m])

Table 6-463 NFProfileRetrieval - FQDN Validation Failed

Field Details
Description Measures the total number of profile retrieval request for which FQDN based authentication failed at NRF. This is based on [ NfFqdn :- {{ NfFqdn}}].

For more information about metric used, see NF Authentication Metrics.

Expression increase(ocnrf_nf_authentication_failure_total{namespace=\"$namespace\",ServiceOperation=\"NFProfileRetrieval\"}[5m])

Table 6-464 NFListRetrieval - FQDN Validation Failed

Field Details
Description Measures the total number of NF list retrieval request for which FQDN based authentication failed at NRF. This is based on [ NfFqdn :- {{ NfFqdn}}].

For more information about metric used, see NF Authentication Metrics.

Expression increase(ocnrf_nf_authentication_failure_total{namespace=\"$namespace\",ServiceOperation=\"NFListRetrieval\"}[5m])
6.2.3.3 Georedundancy KPIs

This section lists the georedundancy KPIs at NRF.

Table 6-465 Total NFs switch over

Field Details
Description Measures the number of NFInstances that got switched over from the mated site. This is based on [ ServiceOperation :- {{ Service_Operation }} ,RemoteNrfInstanceId :- {{ RemoteNrfInstanceId }}].

For more information about metric used, see Georedundancy Metrics.

Expression increase(ocnrf_nf_switch_over_total{kubernetes_namespace=\"$namespace\"}[5m])

Table 6-466 Total Subscriptions switch over

Field Details
Description Measures the number of NfSubscriptions that got switched over from the mated site. This is based on [ ServiceOperation :- {{ ServiceOperation }} RemoteNrfInstanceId :- {{ RemoteNrfInstanceId }}].

For more information about metric used, see Georedundancy Metrics.

Expression increase(ocnrf_nfSubscriptions_switch_over_total{kubernetes_namespace=\"$namespace\"}[5m])

Table 6-467 Total Stale NFs deleted

Field Details
Description Measures the number of NfInstances that get deleted by the NrfAuditor when it detects a record to be stale.

For more information about metric used, see Georedundancy Metrics.

Expression increase(ocnrf_stale_nf_deleted_total{namespace="$namespace"}[5m])

Table 6-468 Total Stale Subscriptions deleted

Field Details
Description Measures the number of NfSubscriptions that get deleted by the NrfAuditor when it detects a record to be stale.

For more information about metric used, see Georedundancy Metrics.

Expression increase(ocnrf_stale_nfSubscriptions_deleted_total{namespace="$namespace"}[5m])
6.2.3.4 Subscription Pod Protection

Table 6-469 Subscription Pod Overall Congestion State

Field Details
Description Tracks the overall congestion state per nfSubscription pod.
Expression sum(ocnrf_pod_congestion_state{namespace='$namespace'}) by (pod)

Table 6-470 Subscription Pod CPU Congestion state

Field Details
Description Tracks the congestion state based on the CPU usage of the subscription pod.
Expression sum(ocnrf_pod_cpu_congestion_state{namespace='$namespace'}) by (pod)

Table 6-471 Subscription Pod CPU Usage

Field Details
Description Measures the CPU usage of the pod.
Expression sum(ocnrf_pod_cpu_usage{namespace="$namespace",container="nfsubscription"}) by (pod)

Table 6-472 Subscription Pod Pending Message Count Congestion state

Field Details
Description Tracks the congestion state based on the pending message count of the subscription pod.
Expression sum(ocnrf_pod_pending_message_count_congestion_state{namespace='$namespace'}) by (pod)

Table 6-473 Subscription Pod Pending Message Count

Field Details
Description Measures the Pending Message Count value of the pod.
Expression sum(ocnrf_pod_pending_message_count{namespace="$namespace",container="nfsubscription"}) by (pod)

Table 6-474 Subscription Pod Incoming Connections Rejected

Field Details
Description Measures the number of connections that have been rejected in the DoC or Congested state. This is based on {{pod }}.
Expression sum(rate(ocnrf_pod_incoming_connection_rejected_total{namespace="$namespace"}[2m])) by (pod)

Table 6-475 Incoming Connections

Field Details
Description Tracks the number of incoming connections. This is based on {{pod }}.
Expression sum(irate(ocnrf_incoming_connections{namespace="$namespace"}[2m])) by (pod)

Table 6-476 Max Streams

Field Details
Description Tracks the maximum concurrent streams per connection. This is based on {{ pod }} : {{ connectionId }}.
Expression sum(ocnrf_max_concurrent_streams{namespace="$namespace"}) by(pod,connectionId)
6.2.3.5 Controlled Shutdown of NRF

This section lists the controlled shutdown KPIs at NRF.

Table 6-477 Operational State {{ pod }}

Field Details
Description Measures the Operational State of NRF.

The metric is pegged in the NrfAuditor microservice. If any one of the NrfAuditor pod shows the operational state as COMPLETE_SHUTDOWN, then the state shall be considered as Complete Shutdown.

For more information about metric used, see NRF NF Metrics.

Expression sum(ocnrf_operational_state{namespace="$namespace"}) by (pod)

Table 6-478 NRF Audit status

Field Details
Description Measures the audit status of NRF.

The metric is pegged in the NrfAuditor microservice. If any one of the NrfAuditor pod shows the audit state as paused then the audit status is considered as paused.

For more information about metric used, see NRF NF Metrics.
Expression sum(ocnrf_audit_status{namespace="$namespace"})
6.2.3.6 Network Slice Specific KPIs

This section lists the network slice specific KPIs at NRF.

Table 6-479 Request [sNssai: {{ sNssai }}]

Field Details
Description Measures the total number of NfRegister requests received at a slice that is identified by specific SNSSAI.

For more information about metric used, see Network Slice Specific Metrics.

Expression sum(irate(ocnrf_nfRegister_requests_perSnssai_total{namespace="$namespace"}[2m])) by(sNssai)

Table 6-480 Success [sNssai:{{ sNssai }}]

Field Details
Description Measures the total number of NfRegister successful response sent per slice that is identified by specific SNSSAI.

For more information about metric used, see Network Slice Specific Metrics.

Expression sum(irate(ocnrf_nfRegister_success_responses_perSnssai_total{namespace="$namespace"}[5m])) by (sNssai)

Table 6-481 Failures [sNssai: {{ sNssai }}]

Field Details
Description Measures the total number of NfRegister failure response sent per slice that is identified by specific SNSSAI.

For more information about metric used, see Network Slice Specific Metrics.

Expression sum(irate(ocnrf_nfRegister_failure_responses_perSnssai_total{namespace="$namespace"}[2m])) by (sNssai)

Table 6-482 Request [sNssai: {{ sNssai }}]

Field Details
Description Measures the total number of NfDeregister requests received at a slice that is identified by specific SNSSAI.

For more information about metric used, see Network Slice Specific Metrics.

Expression sum(irate(ocnrf_nfDeregister_requests_perSnssai_total{namespace="$namespace"}[2m])) by(sNssai)

Table 6-483 Success [sNssai:{{ sNssai }}]

Field Details
Description Measures the total number of NfDeregister successful response sent per slice that is identified by specific SNSSAI.

For more information about metric used, see Network Slice Specific Metrics.

Expression sum(irate(ocnrf_nfDeregister_success_responses_perSnssai_total{namespace="$namespace"}[5m])) by (sNssai)

Table 6-484 Failures [sNssai: {{ sNssai }}]

Field Details
Description Measures the total number of NfDeregister failure response sent per slice that is identified by specific SNSSAI.

For more information about metric used, see Network Slice Specific Metrics.

Expression sum(irate(ocnrf_nfDeregister_failure_responses_perSnssai_total{namespace="$namespace"}[2m])) by (sNssai)

Table 6-485 Success [Nsi :{{ Nsi }}]

Field Details
Description Measures the total number of NfDeregister successful response sent per slice that is identified by specific NSI.

For more information about metric used, see Network Slice Specific Metrics.

Expression sum(irate(ocnrf_nfDeregister_success_responses_perNsi_total{namespace="$namespace"}[5m])) by (Nsi)

Table 6-486 Failures [Nsi :{{ Nsi }}]

Field Details
Description Measures the total number of NfDeregister failure response sent per slice that is identified by specific NSI.

For more information about metric used, see Network Slice Specific Metrics.

Expression sum(irate(ocnrf_nfDeregister_failure_responses_perNsi_total{namespace="$namespace"}[2m])) by (Nsi)

Table 6-487 Requests [sNssai: {{ sNssai }}]

Field Details
Description Measures the total number of NfUpdate requests received at a slice that is identified by specific SNSSAI.

For more information about metric used, see Network Slice Specific Metrics.

Expression sum(irate(ocnrf_nfUpdate_requests_perSnssai_total{namespace="$namespace"}[2m])) by(sNssai)

Table 6-488 Success [sNssai:{{ sNssai }}]

Field Details
Description Measures the total number of NfUpdate successful response sent per slice that is identified by specific SNSSAI.

For more information about metric used, see Network Slice Specific Metrics.

Expression sum(irate(ocnrf_nfUpdate_success_responses_perSnssai_total{namespace="$namespace"}[5m])) by (sNssai)

Table 6-489 Failures [sNssai: {{ sNssai }}]

Field Details
Description Measures the total number of NfUpdate failure response sent per slice that is identified by specific SNSSAI.

For more information about metric used, see Network Slice Specific Metrics.

Expression sum(irate(ocnrf_nfUpdate_failure_responses_perSnssai_total{namespace="$namespace"}[2m])) by (sNssai)

Table 6-490 Requests [Nsi: {{ Nsi }}]

Field Details
Description Measures the total number of NfUpdate requests received at a slice that is identified by specific NSI.

For more information about metric used, see Network Slice Specific Metrics.

Expression sum(irate(ocnrf_nfUpdate_requests_perNsi_total{namespace="$namespace"}[2m])) by(Nsi)

Table 6-491 Success [Nsi :{{ Nsi }}]

Field Details
Description Measures the total number of NfUpdate successful response sent per slice that is identified by specific NSI.

For more information about metric used, see Network Slice Specific Metrics.

Expression sum(irate(ocnrf_nfUpdate_success_responses_perNsi_total{namespace="$namespace"}[5m])) by (Nsi)

Table 6-492 Failures [Nsi :{{ Nsi }}]

Field Details
Description Measures the total number of NfUpdate failure response sent per slice that is identified by specific NSI.

For more information about metric used, see Network Slice Specific Metrics.

Expression sum(irate(ocnrf_nfUpdate_failure_responses_perNsi_total{namespace="$namespace"}[2m])) by (Nsi)

Table 6-493 Requests [sNssai: {{ sNssai }}]

Field Details
Description Measures the total number of NF HeartBeat requests received at a slice that is identified by specific SNSSAI.

For more information about metric used, see Network Slice Specific Metrics.

Expression sum(irate(ocnrf_nfHeartBeat_requests_perSnssai_total{namespace="$namespace"}[2m])) by(sNssai)

Table 6-494 Success [sNssai:{{ sNssai }}]

Field Details
Description Measures the total number of NF HeartBeat successful response sent per slice that is identified by specific SNSSAI.

For more information about metric used, see Network Slice Specific Metrics.

Expression sum(irate(ocnrf_nfHeartBeat_success_responses_perSnssai_total{namespace="$namespace"}[5m])) by (sNssai)

Table 6-495 Failures [sNssai: {{ sNssai }}]

Field Details
Description Measures the total number of NF HeartBeat failure response sent per slice that is identified by specific SNSSAI.

For more information about metric used, see Network Slice Specific Metrics.

Expression sum(irate(ocnrf_nfHeartBeat_failure_responses_perSnssai_total{namespace="$namespace"}[2m])) by (sNssai)

Table 6-496 Requests [Nsi: {{ Nsi }}]

Field Details
Description Measures the total number of NF HeartBeat requests received at a slice that is identified by specific NSI.

For more information about metric used, see Network Slice Specific Metrics.

Expression sum(irate(ocnrf_nfHeartBeat_requests_perNsi_total{namespace="$namespace"}[2m])) by(Nsi)

Table 6-497 Success [Nsi :{{ Nsi }}]

Field Details
Description Measures the total number of NF HeartBeat successful response sent per slice that is identified by specific NSI.

For more information about metric used, see Network Slice Specific Metrics.

Expression sum(irate(ocnrf_nfHeartBeat_success_responses_perNsi_total{namespace="$namespace"}[5m])) by (Nsi)

Table 6-498 Failures [Nsi :{{ Nsi }}]

Field Details
Description Measures the total number of NF HeartBeat failure response sent per slice that is identified by specific NSI.

For more information about metric used, see Network Slice Specific Metrics.

Expression sum(irate(ocnrf_nfHeartBeat_failure_responses_perNsi_total{namespace="$namespace"}[2m])) by (Nsi)

Table 6-499 Requests [sNssai: {{ sNssai }}]

Field Details
Description Measures the total number of NfDiscovery requests received at a slice that is identified by specific SNSSAI.

For more information about metric used, see Network Slice Specific Metrics.

Expression sum(irate(ocnrf_nfDiscover_rx_requests_perSnssai_total{namespace="$namespace"}[2m])) by(sNssai)

Table 6-500 Success [sNssai:{{ sNssai }}]

Field Details
Description Measures the total number of NfDiscovery successful response sent per slice that is identified by specific SNSSAI.

For more information about metric used, see Network Slice Specific Metrics.

Expression sum(irate(ocnrf_nfDiscover_tx_success_response_perSnssai_total{namespace="$namespace"}[5m])) by (sNssai)

Table 6-501 Failures [sNssai: {{ sNssai }}]

Field Details
Description Measures the total number of NfDiscovery failure response sent per slice that is identified by specific SNSSAI.

For more information about metric used, see Network Slice Specific Metrics.

Expression sum(irate(ocnrf_nfDiscover_tx_failure_response_perSnssai_total{namespace="$namespace"}[2m])) by (sNssai)

Table 6-502 Empty [sNssai: {{ sNssai }}]

Field Details
Description Measures the total number of NfDiscovery empty response sent per slice that is identified by specific SNSSAI.

For more information about metric used, see Network Slice Specific Metrics.

Expression sum(irate(ocnrf_nfDiscover_tx_empty_response_perSnssai_total{namespace="$namespace"}[2m])) by (sNssai)

Table 6-503 Requests [Nsi: {{ Nsi }}]

Field Details
Description Measures the total number of NfDiscovery requests received at a slice that is identified by specific NSI.

For more information about metric used, see Network Slice Specific Metrics.

Expression sum(irate(ocnrf_nfDiscover_rx_requests_perNsi_total{namespace="$namespace"}[2m])) by(Nsi)

Table 6-504 Success [Nsi :{{ Nsi }}]

Field Details
Description Measures the total number of nfDiscovery successful response sent per slice that is identified by specific NSI.

For more information about metric used, see Network Slice Specific Metrics.

Expression sum(irate(ocnrf_nfDiscover_tx_success_response_perNsi_total{namespace="$namespace"}[5m])) by (Nsi)

Table 6-505 Failures [Nsi :{{ Nsi }}]

Field Details
Description Measures the total number of NfDiscovery failure response sent per slice that is identified by specific NSI.

For more information about metric used, see Network Slice Specific Metrics.

Expression sum(irate(ocnrf_nfDiscover_tx_failure_response_perNsi_total{namespace="$namespace"}[2m])) by (Nsi)

Table 6-506 Empty [Nsi: {{ Nsi }}]

Field Details
Description Measures the total number of NfDiscovery empty response sent per slice that is identified by specific NSI.

For more information about metric used, see Network Slice Specific Metrics.

Expression sum(irate(ocnrf_nfDiscover_tx_empty_response_perNsi_total{namespace="$namespace"}[2m])) by (Nsi)
6.2.3.7 SCP Health Status

This section lists the controlled shutdown KPIs at NRF.

Table 6-507 Available Peers {{peerset}}

Field Details
Description Measures the total number of available peers in a peerset.

For more information about metric used, see NRF Gateways Metrics.

Expression sum(oc_egressgateway_peer_available_count{namespace="$namespace"}) by (peerset)

Table 6-508 Ping Request

Field Details
Description Measures the rate of Ping Requests to the peers.

For more information about metric used, see NRF Gateways Metrics.

Expression sum(irate(oc_egressgateway_peer_health_ping_request_total{namespace="$namespace"}[2m]))

Table 6-509 Ping Response {{ status }}

Field Details
Description Measures the rate of Ping Responses to the peers.

For more information about metric used, see NRF Gateways Metrics.

Expression sum(irate(oc_egressgateway_peer_health_ping_response_total{namespace="$namespace"}[2m])) by (status)

Table 6-510 SCP health status {{ peer }}

Field Details
Description Measures the health status of the peer.

For more information about metric used, see NRF Gateways Metrics.

Expression sum(oc_egressgateway_peer_health_status{namespace="$namespace"}) by (peer)

Table 6-511 Total Peers {{peerset}}

Field Details
Description Measures the total number of peers in a peerset.

For more information about metric used, see NRF Gateways Metrics.

Expression sum(oc_egressgateway_peer_count{namespace="$namespace"}) by (peerset)
6.2.3.8 Ingress Gateway Pod Protection

Table 6-512 OCNRF Ingress-Gateway Pod Overall Congestion State

Field Details
Description Indicates the current state of the Ingress Gateway pod.
Expression sum(oc_ingressgateway_pod_congestion_state{namespace='$namespace'}) by (pod)

Table 6-513 OCNRF Ingress-Gateway Pod CPU Congestion State

Field Details
Description Tracks the CPU utilization based on which Ingress Gateway pod is calculating its congestion state.
Expression sum(oc_ingressgateway_pod_resource_state{type="CPU",namespace='$namespace'}) by (pod)

Table 6-514 OCNRF Ingress-Gateway Pod CPU Usage

Field Details
Description Tracks the CPU utilization based on which Ingress Gateway pod is calculating its congestion state.
Expression sum(oc_ingressgateway_pod_resource_stress{type="CPU",namespace='$namespace'}) by (pod)

Table 6-515 OCNRF Ingress-Gateway Incoming Pod Connections Rejected

Field Details
Description Tracks the number of connections dropped at Congested or DOC state.
Expression sum(irate(oc_ingressgateway_incoming_pod_connections_rejected_total{namespace="$namespace"}[5m])) by (pod)

Table 6-516 OCNRF Ingress-Gateway Pod Pending Message Congestion State

Field Details
Description Tracks the congestion state based on the pending message count of the Ingress Gateway pod.
Expression sum(oc_ingressgateway_pod_resource_state{type="PENDING_REQUEST",namespace='$namespace'}) by (pod)

Table 6-517 OCNRF Ingress Gateway Pod Pending Messages

Field Details
Description Measures the pending message count usage of the Ingress Gateway pod.
Expression sum(oc_ingressgateway_pod_resource_stress{type="PENDING_REQUEST",namespace='$namespace'}) by (pod)
6.2.3.9 NRF Growth Specific KPIs

Table 6-518 Total Number of CDS Requests

Field Details
Description Measures the rate of incoming requests at Cache Data Service.
Expression sum(rate(ocnrf_cds_rx_requests_total{namespace="$namespace"}[2m]))

Table 6-519 Total Number of CDS Responses

Field Details
Description Measures the rate of responses from Cache Data Service.
Expression sum(rate(ocnrf_cds_tx_responses_total{namespace="$namespace"}[2m])) by (HttpStatusCode)

Table 6-520 Total Number of CDS Requests per Service Operation

Field Details
Description Measures the rate of outgoing requests by local NRF microservices to Cache Data Service for state data.
Expression sum(rate(ocnrf_query_cds_requests_total{namespace="$namespace"}[2m])) by (ServiceOperation)

Table 6-521 Total Number of CDS Responses per Service Operation

Field Details
Description Measures the rate of response received by local NRF microservices from Cache Data Service for state data.
Expression sum(rate(ocnrf_query_cds_responses_total{namespace="$namespace"}[2m])) by (ServiceOperation,HttpStatusCode)

Table 6-522 CDS Latency 50%

Field Details
Description Measures the average amount of time taken to process the requests by Cache Data Service at the 50 percentile of the latency value.
Expression avg(ocnrf_cds_round_trip_time_seconds{namespace="$namespace",quantile="0.5"})

Table 6-523 CDS Latency 90%

Field Details
Description Measures the average amount of time taken to process the requests by Cache Data Service at the 90 percentile of the latency value.
Expression avg(ocnrf_cds_round_trip_time_seconds{namespace="$namespace",quantile="0.9"})

Table 6-524 CDS Latency 95%

Field Details
Description Measures the average amount of time taken to process the requests by Cache Data Service at the 95 percentile of the latency value.
Expression avg(ocnrf_cds_round_trip_time_seconds{namespace="$namespace",quantile="0.95"})

Table 6-525 CDS Latency 99%

Field Details
Description Measures the average amount of time taken to process the requests by Cache Data Service at the 99 percentile of the latency value.
Expression avg(ocnrf_cds_round_trip_time_seconds{namespace="$namespace",quantile="0.99"})

Table 6-526 CDS Request Latency 99% for NfAccessToken Service Operation

Field Details
Description Measures the average amount of time taken for querying state data from Cache Data Service for NfAccessToken service operation at the 99 percentile of the latency value.
Expression avg(ocnrf_query_cds_round_trip_time_seconds{namespace="$namespace",quantile="0.99",ServiceOperation="NfAccessToken"})

Table 6-527 CDS Request Latency 99% for NfDiscover Service Operation

Field Details
Description Measures the average amount of time taken for querying state data from Cache Data Service for NfDiscover service operation at the 99 percentile of the latency value.
Expression avg(ocnrf_query_cds_round_trip_time_seconds{namespace="$namespace",quantile="0.99",ServiceOperation="NfDiscover"})

Table 6-528 CDS Request Latency 99% for NfListRetrieval Service Operation

Field Details
Description Measures the average amount of time taken for querying state data from Cache Data Service for NfListRetrieval service operation at the 99 percentile of the latency value.
Expression avg(ocnrf_query_cds_round_trip_time_seconds{namespace="$namespace",quantile="0.99",ServiceOperation="NfListRetrieval"})

Table 6-529 CDS Request Latency 99% for NfProfileRetrieval Service Operation

Field Details
Description Measures the average amount of time taken for querying state data from Cache Data Service for NfProfileRetrieval service operation at the 99 percentile of the latency value.
Expression avg(ocnrf_query_cds_round_trip_time_seconds{namespace="$namespace",quantile="0.99",ServiceOperation="NfProfileRetrieval"})

Table 6-530 CDS Request Latency 99% for NfSubscribe Service Operation

Field Details
Description Measures the average amount of time taken for querying state data from Cache Data Service for NfSubscribe service operation at the 99 percentile of the latency value.
Expression avg(ocnrf_query_cds_round_trip_time_seconds{namespace="$namespace",quantile="0.99",ServiceOperation="NfSubscribe"})

Table 6-531 CDS Request Latency 99% for NfUnsubscribe Service Operation

Field Details
Description Measures the average amount of time taken for querying state data from Cache Data Service for NfUnsubscribe service operation at the 99 percentile of the latency value.
Expression avg(ocnrf_query_cds_round_trip_time_seconds{namespace="$namespace",quantile="0.99",ServiceOperation="NfUnsubscribe"})

Table 6-532 CDS Request Latency 99% for notifyProfileDeregistration Service Operation

Field Details
Description Measures the average amount of time taken for querying state data from Cache Data Service for notifyProfileDeregistration service operation at the 99 percentile of the latency value.
Expression avg(ocnrf_query_cds_round_trip_time_seconds{namespace="$namespace",quantile="0.99",ServiceOperation="notifyProfileDeregistration"})

Table 6-533 CDS Request Latency 99% for notifyProfileRegistration Service Operation

Field Details
Description Measures the average amount of time taken for querying state data from Cache Data Service for notifyProfileRegistration service operation at the 99 percentile of the latency value.
Expression avg(ocnrf_query_cds_round_trip_time_seconds{namespace="$namespace",quantile="0.99",ServiceOperation="notifyProfileRegistration"})

Table 6-534 CDS Request Latency 99% for notifyProfileChange Service Operation

Field Details
Description Measures the average amount of time taken for querying state data from Cache Data Service for notifyProfileChange service operation at the 99 percentile of the latency value.
Expression avg(ocnrf_query_cds_round_trip_time_seconds{namespace="$namespace",quantile="0.99",ServiceOperation="notifyProfileChange"})

Table 6-535 CDS Request Latency 99% for nrfauditor Service Operation

Field Details
Description Measures the average amount of time taken for querying state data from Cache Data Service for nrfauditor service operation at the 99 percentile of the latency value.
Expression avg(ocnrf_query_cds_round_trip_time_seconds{namespace="$namespace",quantile="0.99",ServiceOperation="nrfauditor"})

Table 6-536 Total Number of CDS Requests per Request Type

Field Details
Description Measures the rate of incoming requests at Cache Data Service per request type.
Expression sum(rate(ocnrf_cds_rx_requests_total{namespace="$namespace"}[2m])) by (RequestType)

Table 6-537 Total Number of CDS Responses per Request Type

Field Details
Description Measures the rate of responses from Cache Data Service per request type.
Expression sum(rate(ocnrf_cds_tx_responses_total{namespace="$namespace"}[2m])) by (RequestType, HttpStatusCode)

Table 6-538 Total Number of Remote CDS Requests

Field Details
Description Measures the rate of requests sent to the NRF of a remote NRF set by Cache Data Service.
Expression sum(rate(ocnrf_query_remote_cds_requests_total{namespace="$namespace"}[2m])) by (TargetNrfSetId)

Table 6-539 Total Number of Remote CDS Responses

Field Details
Description Indicates the total number of responses received from the NRF in the remote set.
Expression sum(rate(ocnrf_query_remote_cds_responses_total{namespace="$namespace"}[2m])) by (TargetNrfSetId, HttpStatusCode)

Table 6-540 Remote CDS Query Latency 50%

Field Details
Description Measures the average amount of time taken to process the requests sent by Cache Data Service towards remote NRF set and response received at the 50 percentile of the latency value.
Expression avg(ocnrf_query_remote_cds_round_trip_time_seconds{namespace="$namespace",quantile="0.5"})

Table 6-541 Remote CDS Query Latency 90%

Field Details
Description Measures the average amount of time taken to process the requests sent by Cache Data Service towards remote NRF set and response received at the 90 percentile of the latency value.
Expression avg(ocnrf_query_remote_cds_round_trip_time_seconds{namespace="$namespace",quantile="0.9"})

Table 6-542 Remote CDS Query Latency 95%

Field Details
Description Measures the average amount of time taken to process the requests sent by Cache Data Service towards remote NRF set and response received at the 95 percentile of the latency value.
Expression avg(ocnrf_query_remote_cds_round_trip_time_seconds{namespace="$namespace",quantile="0.95"})

Table 6-543 Remote CDS Query Latency 99%

Field Details
Description Measures the average amount of time taken to process the requests sent by Cache Data Service towards remote NRF set and response received at the 99 percentile of the latency value.
Expression avg(ocnrf_query_remote_cds_round_trip_time_seconds{namespace="$namespace",quantile="0.99"})

Table 6-544 Database Fallback

Field Details
Description Measures the rate at which the service request was fulfilled from the database by the NRF microservices as the query towards the Cache Data Service failed.
Expression sum(rate(ocnrf_db_fallback_total{namespace="$namespace"}[2m])) by (ServiceOperation)

Table 6-545 CDS Cache Sync

Field Details
Description Measures the rate at which state data entries are synched from the local database at CDS.
Expression sum(rate(ocnrf_cache_sync_count_total{namespace="$namespace",container="nrfcachedata"}[2m]))
6.2.3.10 Egress Gateway Pod Throttling

Table 6-546 Egress Gateway Discards Due To Rate Limit

Field Details
Description Measures the requests discarded by Egress Gateway due to Egress Gateway Pod Throttling feature.

For more information about metric used, see Egress Gateway Metrics.

Expression sum(rate(oc_egressgateway_podlevel_throttling_discarded_total{namespace="$namespace"}[2m])) by (pod)
6.2.3.11 Ingress Gateway Pod Protection Using Rate Limiting

Table 6-547 Allowed Request Rate Per Route Id

Field Details
Description Measures the request rate allowed per Route Id.

For more information about metric used, see Ingress Gateway Metrics.

Expression sum(irate(oc_ingressgateway_http_request_ratelimit_values_total{Allowed="true",namespace="$namespace"}[2m])) by (Id)

Table 6-548 Total Rejections Chain Length

Field Details
Description Measures the number of consecutive rejects before a successful accept. The metric indicates rejections due to traffic burst.

For more information about metric used, see Ingress Gateway Metrics.

Expression sum(rate(oc_ingressgateway_http_request_ratelimit_reject_chain_length_histogram_bucket{namespace="$namespace"}[2m])) by (le)

Table 6-549 Discard Request Action Traffic Rate

Field Details
Description Measures the rate of requests rejected or processed based on the discard request action.

For more information about metric used, see Ingress Gateway Metrics.

Expression sum(irate(oc_ingressgateway_http_request_ratelimit_denied_count_total{namespace="$namespace"}[2m])) by (Action)

Table 6-550 Pod Congestion Level

Field Details
Description Measures the congestion level of the pod.

For more information about metric used, see Ingress Gateway Metrics.

Expression sum(rate(oc_ingressgateway_congestion_level_bucket_total{namespace="$namespace"}[2m])) by (le)

6.3 NRF Alerts

This section includes information about the NRF alerts.

The following table describes the various alert levels generated by NRF:

Table 6-551 Alerts Levels or Severity Types

Alerts Levels/Severity Types Definition
Critical Indicates a severe issue that poses a significant risk to safety, security, or operational integrity. It requires immediate response to address the situation and prevent serious consequences. Raised for conditions may affect the service of NRF.
Major Indicates a more significant issue that has an impact on operations or poses a moderate risk. It requires prompt attention and action to mitigate potential escalation. Raised for conditions may affect the service of NRF.
Minor Indicates a situation that is low in severity and does not pose an immediate risk to safety, security, or operations. It requires attention but does not demand urgent action. Raised for conditions may affect the service of NRF.
Info or Warn (Informational) Provides general information or updates that are not related to immediate risks or actions. These alerts are for awareness and do not typically require any specific response. WARN and INFO alerts may not impact the service of NRF.

Note:

  • Summary or dimensions may vary based on deployment.
  • The alert triggering time varies as per the environment in which it is deployed.
  • The performance and capacity of the NRF system may vary based on the call model, Feature or Interface configuration, and underlying CNE and hardware environment.

6.3.1 System Level Alerts

This section lists the system level alerts.

6.3.1.1 OcnrfNfStatusUnavailable

Table 6-552 OcnrfNfStatusUnavailable

Field Details
Description 'OCNRF services unavailable'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : All OCNRF services are unavailable.'
Severity Critical
Condition When all the NRF services are unavailable, either because the NRF is getting deployed or purged. The NRF services considered are nfregistration, nfsubscription, nrfauditor, nrfconfiguration, nfaccesstoken, nfdiscovery, appinfo, ingressgateway, and egressgateway.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7016
Metric Used

'up'

Note: This is a Prometheus metric used for instance availability monitoring.

If this metric is not available, use a similar metric as exposed by the monitoring system.

Recommended Actions The alert is cleared automatically when the NRF services restart.

Steps:

  1. Check for service-specific alerts which may be causing the issues with service exposure.
  2. Run the following command to check the pod status:
    $ kubectl get po -n <namespace>
    1. Run the following command to analyze the error condition of the pod that is not in the Running state:
      $ kubectl describe pod <pod name not in Running state> -n <namespace>

      Where <pod name not in Running state> indicates the pod that is not in the Running state.

  3. Refer to the application logs on Kibana and check for database related failures such as connectivity and invalid secrets. The logs can be filtered based on the services.
  4. Check for helm status to make sure there are no errors:
    $ helm status <helm release name of the desired NF> -n <namespace>

    If it is not in “STATUS : DEPLOYED”, then capture logs and event again.

  5. In case the issue persists, capture all the outputs for the above steps and contact My Oracle Support.

    Note: Use CNC NF Data Collector tool for capturing logs. For more information on the Data Collector tool, see Oracle Communications Cloud Native Core, Network Function Data Collector User Guide.

Available in OCI No
6.3.1.2 OcnrfPodsRestart

Table 6-553 OcnrfPodsRestart

Field Details
Description 'Pod <Pod Name> has restarted.
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, podname: {{$labels.kubernetes_pod_name}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : A Pod has restarted'
Severity Major
Condition A pod belonging to any of the NRF services have restarted.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7017
Metric Used 'kube_pod_container_status_restarts_total'

Note: This is a Kubernetes metric. If this metric is not available, use a similar metric as exposed by the monitoring system.

Recommended Actions

The alert is cleared automatically if the specific pod is up.

Steps:

  1. Refer to the application logs on Kibana and filter based on pod name, check for database related failures such as connectivity and Kubernetes secrets.
  2. To check the orchestration logs for liveness or readiness probe failures, do the following:
    1. Run the following command to check the pod status:
      $ kubectl get po -n <namespace>
    2. Run the following command to analyze the error condition of the pod that is not in the Running state:
      $ kubectl describe pod <pod name not in Running state> -n <namespace>

      Where <pod name not in Running state> indicates the pod that is not in the Running state.

  3. Check the database status. For more information, see Oracle Communications Cloud Native Core, cnDBTier User Guide.
  4. In case the issue persists, capture all the outputs for the above steps and contact My Oracle Support.

    Note: Use CNC NF Data Collector tool for capturing logs. For more information on the Data Collector tool, see Oracle Communications Cloud Native Core, Network Function Data Collector User Guide.

Available in OCI No
6.3.1.3 NnrfNFManagementServiceDown

Table 6-554 NnrfNFManagementServiceDown

Field Details
Description 'OCNRF Nnrf_Management service <nfregistration|nfsubscription|nrfauditor> is down'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : NFManagement service is down'
Severity Critical
Condition This alert is raised when either NFRegistration, NFSubscription, or NrfAuditor services are unavailable.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7018
Metric Used ''up'

Note: This is a Prometheus metric used for instance availability monitoring. If this metric is not available, use a similar metric as exposed by the monitoring system.

Recommended Actions The alert is cleared when all the Nnrf_NFManagement services nfregistration, nfsubscription, and nrfauditor are available.

Steps:

  1. Check if NfService specific alerts are generated to understand which service is down.

    Either some or all of the following alerts are generated based on which services are down

    • OcnrfRegistrationServiceDown
    • OcnrfSubscriptionServiceDown
    • OcnrfAuditorServiceDown
  2. To check the orchestration logs for liveness or readiness probe failures, do the following:
    1. Run the following command to check the pod status:
      $ kubectl get po -n <namespace>
    2. Run the following command to analyze the error condition of the pod that is not in the Running state:
      $ kubectl describe pod <pod name not in Running state> -n <namespace>

      Where <pod name not in Running state> indicates the pod that is not in the Running state.

  3. Check for the POD’s status if they are in “Running” state using the following command:
    $ kubectl get pod –n <namespace> 
    If it is not in “Running” state, capture the pod logs and events by running the following command:
    $ kubectl get events --sort-by=.metadata.creationTimestamp -n <namespace>
  4. Refer to the application logs on Kibana and filter based on aforementioned service names. Check for ERROR WARNING logs for each of these services.
  5. Check the database status. For more information on how to check the database status, see Oracle Communications Cloud Native Core, cnDBTier User Guide.
  6. Refer to the application logs on Kibana and filter the service appinfo, check for the service status of the nfregistration, nfsubscription, and nrfauditor services.
  7. In case the issue persists, capture all the outputs for the above steps and contact My Oracle Support.

    Note: Use CNC NF Data Collector tool for capturing logs. For more information on how to collect logs using Data Collector tool, see Oracle Communications Cloud Native Core, Network Function Data Collector User Guide.

Available in OCI No
6.3.1.4 NnrfAccessTokenServiceDown

Table 6-555 NnrfAccessTokenServiceDown

Field Details
Description 'OCNRF Nnrf_NFAccessToken service nfaccesstoken is down'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : NFAccessToken service down'
Severity Critical
Condition This alert is raised when NFAccessToken service is unavailable.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7020
Metric Used ''up''

Note: This is a Prometheus metric used for instance availability monitoring. If this metric is not available use a similar metric as exposed by the monitoring system.

Recommended Actions The alert is cleared when the Nnrf_AccessToken service is available.

Steps:

  1. To check the orchestration logs of nfaccesstoken service and check for liveness or readiness probe failures, do the following:
    1. Run the following command to check the pod status:
      $ kubectl get po -n <namespace>
    2. Run the following command to analyze the error condition of the pod that is not in the Running state:
      $ kubectl describe pod <pod name not in Running state> -n <namespace>

      Where <pod name not in Running state> indicates the pod that is not in the Running state.

  2. Refer to the application logs on Kibana and filter based on nfaccesstoken service names. Check for ERROR WARNING logs.
  3. Check the DB status. For more information on how to check the DB status, see Oracle Communications Cloud Native Core, cnDBTier User Guide.
  4. Depending on the failure reason, take the resolution steps.
  5. In case the issue persists, capture all the outputs for the above steps and contact My Oracle Support.

    Note: Use CNC NF Data Collector tool for capturing logs. For more information on how to collect logs using Data Collector tool, see Oracle Communications Cloud Native Core, Network Function Data Collector User Guide.

Available in OCI No
6.3.1.5 NnrfNFDiscoveryServiceDown

Table 6-556 NnrfNFDiscoveryServiceDown

Field Details
Description 'OCNRF Nnrf_NFDiscovery service nfdiscovery is down'
Applicable in OCI No
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : NFDiscovery service down'
Severity Critical
Condition NFDiscovery is unavailable.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7019
Metric Used 'up'

Note: This is a Prometheus metric used for instance availability monitoring. If this metric is not available, use a similar metric as exposed by the monitoring system.

Recommended Actions

The alert is cleared when the Nnrf_NFDiscovery service is available.

Steps:

  1. To check the orchestration logs of nfdiscovery service and check for liveness or readiness probe failures, do the following:
    1. Run the following command to check the pod status:
      $ kubectl get po -n <namespace>
    2. Run the following command to analyze the error condition of the pod that is not in the Running state:
      $ kubectl describe pod <pod name not in Running state> -n <namespace>

      Where <pod name not in Running state> indicates the pod that is not in the Running state.

  2. Refer to the application logs on Kibana and filter based on nfdiscovery service names. Check for ERROR WARNING logs.
  3. Check the DB status. For more information on how to check the DB status, see Oracle Communications Cloud Native Core, cnDBTier User Guide.
  4. Depending on the failure reason, take the resolution steps.
  5. In case the issue persists, capture all the outputs for the above steps and contact My Oracle Support.

    Note: Use CNC NF Data Collector tool for capturing logs. For more information on how to collect logs using Data Collector tool, see Oracle Communications Cloud Native Core, Network Function Data Collector User Guide.

Available in OCI No
6.3.1.6 OcnrfRegistrationServiceDown

Table 6-557 OcnrfRegistrationServiceDown

Field Details
Description 'OCNRF NFRegistration service nfregistration is down'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : NFRegistration service is down'
Severity Critical
Condition None of the pods of the NFRegistration microservice is available.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7021
Metric Used 'up'

Note: This is a Prometheus metric used for instance availability monitoring. If this metric is not available, use a similar metric as exposed by the monitoring system.

Recommended Actions

The alert is cleared when the nfregistration service is available.

Steps:

  1. To check the orchestration logs of nfregistration service and check for liveness or readiness probe failures, do the following:
    1. Run the following command to check the pod status:
      $ kubectl get po -n <namespace>
    2. Run the following command to analyze the error condition of the pod that is not in the Running state:
      $ kubectl describe pod <pod name not in Running state> -n <namespace>

      Where <pod name not in Running state> indicates the pod that is not in the Running state.

  2. Refer to the application logs on Kibana and filter based on nfregistration service names. Check for ERROR WARNING logs.
  3. Check the DB status. For more information on how to check the DB status, see Oracle Communications Cloud Native Core, cnDBTier User Guide. Depending on the failure reason, take the resolution steps.
  4. In case the issue persists, capture all the outputs for the above steps and contact My Oracle Support.

    Note: Use CNC NF Data Collector tool for capturing logs. For more information on how to collect logs using Data Collector tool, see Oracle Communications Cloud Native Core, Network Function Data Collector User Guide.

Available in OCI No
6.3.1.7 OcnrfSubscriptionServiceDown

Table 6-558 OcnrfSubscriptionServiceDown

Field Details
Description 'OCNRF NFSubscription service nfsubscription is down.
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : NFSubscription service is down'
Severity Critical
Condition None of the pods of the NFSubscription microservice is available.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7022
Metric Used 'up'

Note: This is a Prometheus metric used for instance availability monitoring. If this metric is not available, use a similar metric as exposed by the monitoring system.

Recommended Actions The alert is cleared when the nfsubscription service is available.

Steps:

  1. To check the orchestration logs of nfsubscription service and check for liveness or readiness probe failures, do the following:
    1. Run the following command to check the pod status:
      $ kubectl get po -n <namespace>
    2. Run the following command to analyze the error condition of the pod that is not in the Running state:
      $ kubectl describe pod <pod name not in Running state> -n <namespace>

      Where <pod name not in Running state> indicates the pod that is not in the Running state.

  2. Refer to the application logs on Kibana and filter based on nfsubcription service names. Check for ERROR WARNING logs.
  3. Check the DB status. For more information on how to check the DB status, see Oracle Communications Cloud Native Core, cnDBTier User Guide.
  4. Depending on the failure reason, take the resolution steps.
  5. In case the issue persists, capture all the outputs for the above steps and contact My Oracle Support.

    Note: Use CNC NF Data Collector tool for capturing logs. For more information on how to collect logs using Data Collector tool, see Oracle Communications Cloud Native Core, Network Function Data Collector User Guide.

Available in OCI No
6.3.1.8 OcnrfDiscoveryServiceDown

Table 6-559 OcnrfDiscoveryServiceDown

Field Details
Description 'OCNRF NFDiscovery service nfdiscovery is down'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : NFDiscovery service down'
Severity Critical
Condition None of the pods of the NFDiscovery microservice is available.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7023
Metric Used 'up'

Note: This is a Prometheus metric used for instance availability monitoring. If this metric is not available, use a similar metric as exposed by the monitoring system.

Recommended Actions The alert is cleared when the nfdiscovery service is available.

Steps:

  1. To check the orchestration logs of nfregistration service and check for liveness or readiness probe failures, do the following:
    1. Run the following command to check the pod status:
      $ kubectl get po -n <namespace>
    2. Run the following command to analyze the error condition of the pod that is not in the Running state:
      $ kubectl describe pod <pod name not in Running state> -n <namespace>

      Where <pod name not in Running state> indicates the pod that is not in the Running state.

  2. Refer to the application logs on Kibana and filter based on nfdiscovery service names. Check for ERROR WARNING logs.
  3. Check the DB status. For more information on how to check the DB status, see Oracle Communications Cloud Native Core, cnDBTier User Guide.
  4. In case the issue persists, capture all the outputs for the above steps and contact My Oracle Support.

    Note: Use CNC NF Data Collector tool for capturing logs. For more information on how to collect logs using Data Collector tool, see Oracle Communications Cloud Native Core, Network Function Data Collector User Guide.

Available in OCI No
6.3.1.9 OcnrfAccessTokenServiceDown

Table 6-560 OcnrfAccessTokenServiceDown

Field Details
Description 'OCNRF NFAccessToken service nfaccesstoken is down
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : NFAccesstoken service down'
Severity Critical
Condition None of the pods of the NFAccessToken microservice is available.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7024
Metric Used 'up'

Note: This is a Prometheus metric used for instance availability monitoring. If this metric is not available, use a similar metric as exposed by the monitoring system.

Recommended Actions The alert is cleared when the nfaccesstoken service is available.

Steps:

  1. To check the orchestration logs of nfaccesstoken service and check for liveness or readiness probe failures, do the following:
    1. Run the following command to check the pod status:
      $ kubectl get po -n <namespace>
    2. Run the following command to analyze the error condition of the pod that is not in the Running state:
      $ kubectl describe pod <pod name not in Running state> -n <namespace>

      Where <pod name not in Running state> indicates the pod that is not in the Running state.

  2. Refer to the application logs on Kibana and filter based on nfaccesstoken service names. Check for ERROR WARNING logs.
  3. Check the DB status. For more information on how to check the DB status, see Oracle Communications Cloud Native Core, cnDBTier User Guide.
  4. Depending on the failure reason, take the resolution steps.
  5. In case the issue persists, capture all the outputs for the above steps and contact My Oracle Support.

    Note: Use CNC NF Data Collector tool for capturing logs. For more information on how to collect logs using Data Collector tool, see Oracle Communications Cloud Native Core, Network Function Data Collector User Guide.

Available in OCI No
6.3.1.10 OcnrfAuditorServiceDown

Table 6-561 OcnrfAuditorServiceDown

Field Details
Description 'OCNRF NrfAuditor service nrfauditor is down'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : NrfAuditor service down'
Severity Critical
Condition None of the pods of the NrfAuditor microservice is available.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7026
Metric Used 'up' Note: This is a Prometheus metric used for instance availability monitoring. If this metric is not available, use a similar metric as exposed by the monitoring system.
Recommended Actions

The alert is cleared when the nrfauditor service is available.

Steps:

  1. To check the orchestration logs of nrfauditor service and check for liveness or readiness probe failures, do the following:
    1. Run the following command to check the pod status:
      $ kubectl get po -n <namespace>
    2. Run the following command to analyze the error condition of the pod that is not in the Running state:
      $ kubectl describe pod <pod name not in Running state> -n <namespace>

      Where <pod name not in Running state> indicates the pod that is not in the Running state.

  2. Refer to the application logs on Kibana and filter based on nrfauditor service names. Check for ERROR WARNING logs related to thread exceptions.
  3. Check the DB status. For more information on how to check the DB status, see Oracle Communications Cloud Native Core, cnDBTier User Guide.
  4. Depending on the failure reason, take the resolution steps.
  5. In case the issue persists, capture all the outputs for the above steps and contact My Oracle Support.

    Note: Use CNC NF Data Collector tool for capturing logs. For more information on how to collect logs using Data Collector tool, see Oracle Communications Cloud Native Core, Network Function Data Collector User Guide.

Available in OCI No
6.3.1.11 OcnrfConfigurationServiceDown

Table 6-562 OcnrfConfigurationServiceDown

Field Details
Description 'OCNRF NrfConfiguration service nrfconfiguration is down'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : NrfConfiguration service down'
Severity Critical
Condition None of the pods of the NrfConfiguration microservice is available.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7025
Metric Used 'up'

Note: This is a Prometheus metric used for instance availability monitoring. If this metric is not available, use a similar metric as exposed by the monitoring system.

Recommended Actions

The alert is cleared when the nrfconfiguration service is available.

Steps:

  1. To check the orchestration logs of nrfconfiguration service and check for liveness or readiness probe failures, do the following:
    1. Run the following command to check the pod status:
      $ kubectl get po -n <namespace>
    2. Run the following command to analyze the error condition of the pod that is not in the Running state:
      $ kubectl describe pod <pod name not in Running state> -n <namespace>

      Where <pod name not in Running state> indicates the pod that is not in the Running state.

  2. Refer to the application logs on Kibana and filter based on nrfconfiguration service names. Check for ERROR WARNING logs.
  3. Check the DB status. For more information on how to check the DB status, see Oracle Communications Cloud Native Core, cnDBTier User Guide.
  4. Depending on the failure reason, take the resolution steps.
  5. In case the issue persists, capture all the outputs for the above steps and contact My Oracle Support.

    Note: Use CNC NF Data Collector tool for capturing logs. For more information on how to collect logs using Data Collector tool, see Oracle Communications Cloud Native Core, Network Function Data Collector User Guide.

Available in OCI No
6.3.1.12 OcnrfAppInfoServiceDown

Table 6-563 OcnrfAppInfoServiceDown

Field Details
Description 'OCNRF Appinfo service appinfo is down'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : Appinfo service down'
Severity Critical
Condition None of the pods of the appinfo microservice is available.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7027
Metric Used 'up'

Note: This is a Prometheus metric used for instance availability monitoring. If this metric is not available, use a similar metric as exposed by the monitoring system.

Recommended Actions

The alert is cleared when the appinfo service is available.

Steps:

  1. To check the orchestration logs of appinfo service and check for liveness or readiness probe failures, do the following:
    1. Run the following command to check the pod status:
      $ kubectl get po -n <namespace>
    2. Run the following command to analyze the error condition of the pod that is not in the Running state:
      $ kubectl describe pod <pod name not in Running state> -n <namespace>

      Where <pod name not in Running state> indicates the pod that is not in the Running state.

  2. Refer to the application logs on Kibana and filter based on appinfo service names. Check for ERROR WARNING logs related to thread exceptions.
  3. Depending on the failure reason, take the resolution steps.
  4. In case the issue persists, capture all the outputs for the above steps and contact My Oracle Support.

    Note: Use CNC NF Data Collector tool for capturing logs. For more information on how to collect logs using Data Collector tool, see Oracle Communications Cloud Native Core, Network Function Data Collector User Guide.

Available in OCI No
6.3.1.13 OcnrfArtisanServiceDown

Table 6-564 OcnrfArtisanServiceDown

Field Details
Description 'OCNRF NrfArtisan service {{$labels.app_kubernetes_io_name}} is down'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : NrfArtisan service is down'
Severity Critical
Condition NrfArtisan is unavailable.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7056
Metric Used 'up'

Note: This is a Prometheus metric used for instance availability monitoring. If this metric is not available, use the similar metric as exposed by the monitoring system.

Recommended Actions

The alert is cleared when the NrfArtisan service is available.

Steps:

  1. To check the orchestration logs of NrfArtisan service and check for liveness or readiness probe failures, do the following:
    1. Run the following command to check the pod status:
      $ kubectl get pod -n <namespace>
    2. Run the following command to analyze the error condition of the pod that is not in the Running state:
      $ kubectl describe pod <pod name not in Running state> -n <namespace>

      Where <pod name not in Running state> indicates the pod that is not in the Running state.

  2. Refer to the application logs on Kibana and filter the logs based on NrfArtisan service names. Check for ERROR and WARNING logs related to thread exceptions.
  3. Check the database status. For more information, see the Oracle Communications Cloud Native Core, cnDBTier User Guide.
  4. In case the issue persists, capture all the outputs for the above steps and contact My Oracle Support.

    Note: Use CNC NF Data Collector tool for capturing logs. For more information on how to collect logs using Data Collector tool, see Oracle Communications Cloud Native Core, Network Function Data Collector User Guide.

Available in OCI No
6.3.1.14 OcnrfAlternateRouteServiceDown

Table 6-565 OcnrfAlternateRouteServiceDown

Field Details
Description 'OCNRF AlternateRoute service {{$labels.app_kubernetes_io_name}} is down'
Applicable in OCI No
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : AlternateRoute service is down'
Severity Critical
Condition AlternateRoute is unavailable.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7057
Metric Used

'up'

Note: This is a Prometheus metric used for instance availability monitoring. If this metric is not available, use the similar metric as exposed by the monitoring system.
Recommended Actions

The alert is cleared when the alternate-route service is available.

Steps:

  1. To check the orchestration logs of alternate-route service and check for liveness or readiness probe failures, do the following:
    1. Run the following command to check the pod status:
      $ kubectl get pod -n <namespace>
    2. Run the following command to analyze the error condition of the pod that is not in the Running state:
      $ kubectl describe pod <pod name not in Running state> -n <namespace>

      Where <pod name not in Running state> indicates the pod that is not in the Running state.

  2. Refer to the application logs on Kibana and filter the logs based on Alternate-Route service names. Check for ERROR and WARNING logs related to thread exceptions.
  3. Check the database status. For more information, see the Oracle Communications Cloud Native Core, cnDBTier User Guide.
  4. In case the issue persists, capture all the outputs for the above steps and contact My Oracle Support.

    Note: Use CNC NF Data Collector tool for capturing logs. For more information on how to collect logs using Data Collector tool, see Oracle Communications Cloud Native Core, Network Function Data Collector User Guide.

6.3.1.15 OcnrfPerfInfoServiceDown

Table 6-566 OcnrfPerfInfoServiceDown

Field Details
Description 'OCNRF Perfinfo service {{$labels.app_kubernetes_io_name}} is down'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : Perfinfo service down'
Severity Critical
Condition Perfinfo is unavailable.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7058
Metric Used

'up'

Note: This is a Prometheus metric used for instance availability monitoring. If this metric is not available, use the similar metric as exposed by the monitoring system.
Recommended Actions

The alert is cleared when the Perfinfo service is available.

Steps:

  1. To check the orchestration logs of Perfinfo service and check for liveness or readiness probe failures, do the following:
    1. Run the following command to check the pod status:
      $ kubectl get pod -n <namespace>
    2. Run the following command to analyze the error condition of the pod that is not in the Running state:
      $ kubectl describe pod <pod name not in Running state> -n <namespace>

      Where <pod name not in Running state> indicates the pod that is not in the Running state.

  2. Refer to the application logs on Kibana and filter the logs based on Perf-Info service names. Check for ERROR and WARNING logs related to thread exceptions.
  3. Check the database status. For more information, see the Oracle Communications Cloud Native Core, cnDBTier User Guide.
  4. In case the issue persists, capture all the outputs for the above steps and contact My Oracle Support.

    Note: Use CNC NF Data Collector tool for capturing logs. For more information on how to collect logs using Data Collector tool, see Oracle Communications Cloud Native Core, Network Function Data Collector User Guide.

Available in OCI No
6.3.1.16 OcnrfIngressGatewayServiceDown

Table 6-567 OcnrfIngressGatewayServiceDown

Field Details
Description 'OCNRF Ingress-Gateway service ingressgateway is down'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : Ingress-gateway service down'
Severity Critical
Condition None of the pods of the Ingress Gateway microservice is available.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7028
Metric Used 'up'

Note: This is a Prometheus metric used for instance availability monitoring. If this metric is not available, use a similar metric as exposed by the monitoring system.

Recommended Actions

The alert is cleared when the Ingress Gateway service is available.

Steps:

  1. To check the orchestration logs of Ingress Gateway service and check for liveness or readiness probe failures, do the following:
    1. Run the following command to check the pod status:
      $ kubectl get po -n <namespace>
    2. Run the following command to analyze the error condition of the pod that is not in the Running state:
      $ kubectl describe pod <pod name not in Running state> -n <namespace>

      Where <pod name not in Running state> indicates the pod that is not in the Running state.

  2. Refer to the application logs on Kibana and filter based on Ingress Gateway service names. Check for ERROR WARNING logs related to thread exceptions.
  3. Depending on the failure reason, take the resolution steps.
  4. In case the issue persists, capture all the outputs for the above steps and contact My Oracle Support.

    Note: Use CNC NF Data Collector tool for capturing logs. For more information on how to collect logs using Data Collector tool, see Oracle Communications Cloud Native Core, Network Function Data Collector User Guide.

Available in OCI No
6.3.1.17 OcnrfEgressGatewayServiceDown

Table 6-568 OcnrfEgressGatewayServiceDown

Field Details
Description 'OCNRF Egress-Gateway service egressgateway is down'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, podname: {{$labels.kubernetes_pod_name}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : Egress-Gateway service down'
Severity Critical
Condition None of the pods of the Egress Gateway microservice is available.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7029
Metric Used 'up'

Note: This is a Prometheus metric used for instance availability monitoring. If this metric is not available, use a similar metric as exposed by the monitoring system.

Recommended Actions

The alert is cleared when the Egress Gateway service is available.

Steps:

  1. To check the orchestration logs of Egress Gateway service and check for liveness or readiness probe failures, do the following:
    1. Run the following command to check the pod status:
      $ kubectl get po -n <namespace>
    2. Run the following command to analyze the error condition of the pod that is not in the Running state:
      $ kubectl describe pod <pod name not in Running state> -n <namespace>

      Where <pod name not in Running state> indicates the pod that is not in the Running state.

  2. Refer to the application logs on Kibana and filter based on Egress Gateway service names. Check for ERROR WARNING logs related to thread exceptions.
  3. Depending on the failure reason, take the resolution steps.
  4. In case the issue persists, capture all the outputs for the above steps and contact My Oracle Support.

    Note: Use CNC NF Data Collector tool for capturing logs. For more information on how to collect logs using Data Collector tool, see Oracle Communications Cloud Native Core, Network Function Data Collector User Guide.

Available in OCI No
6.3.1.18 OcnrfTotalIngressTrafficRateAboveMinorThreshold

Table 6-569 OcnrfTotalIngressTrafficRateAboveMinorThreshold

Field Details
Description 'Total Ingress traffic Rate is above configured minor threshold. (current value is: {{ $value }})'
Summary 'timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }}: Traffic Rate is above 80 Percent of Max requests per second'
Severity Minor
Condition

The total NRF Ingress Message rate has crossed the configured minor threshold of 800 TPS.

Default value of this alert trigger point in alert file is when NRF Ingress Rate crosses 80 % of 1000 (Maximum ingress request rate).

OID 1.3.6.1.4.1.323.5.3.36.1.2.7001
Metric Used 'oc_ingressgateway_http_requests_total'
Recommended Actions

The alert is cleared either when the total Ingress Traffic rate falls below the minor threshold or when the total traffic rate crosses the major threshold, in which case the OcnrfTotalIngressTrafficRateAboveMajorThreshold alert is raised.

Note: The threshold is configurable in the alert file.

Reassess why the NRF is receiving additional traffic (for example, Mated site NRF is unavailable in georedundancy scenario). If this alert is unexpected, contact My Oracle Support.
Steps:
  1. Refer Grafana to determine which service is receiving high traffic.
  2. Refer Ingress gateway section in Grafana to determine the increase in 4xx and 5xx error codes.
  3. Check Ingress gateway logs on Kibana to determine the reason for the errors.
Available in OCI No
6.3.1.19 OcnrfTotalIngressTrafficRateAboveMajorThreshold

Table 6-570 OcnrfTotalIngressTrafficRateAboveMajorThreshold

Field Details
Description 'Total Ingress traffic Rate is above major threshold. (current value is: {{ $value }})'
Summary 'timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }}: Traffic Rate is above 90 Percent of Max requests per second'
Severity Major
Condition

The total NRF Ingress Message rate has crossed the configured major threshold of 900 TPS.

Default value of this alert trigger point in the alert file is when NRF Ingress Rate crosses 90 % of 1000 (Maximum ingress request rate).

OID 1.3.6.1.4.1.323.5.3.36.1.2.7002
Metric Used 'oc_ingressgateway_http_requests_total'
Recommended Actions

The alert is cleared when the total Ingress Traffic rate falls below the major threshold or when the total traffic rate crosses the critical threshold, in which case the OcnrfTotalIngressTrafficRateAboveCriticalThreshold alert is raised.

Note: The threshold is configurable in the alert file.

Reassess why the NRF is receiving additional traffic (for example, Mated site NRF is unavailable in georedundancy scenario). If this alert is unexpected, contact My Oracle Support.
Steps:
  1. Refer Grafana to determine which service is receiving high traffic.
  2. Refer Ingress gateway section in Grafana to determine the increase in 4xx and 5xx error codes.
  3. Check Ingress gateway logs on Kibana to determine the reason for the errors.
Available in OCI No
6.3.1.20 OcnrfTotalIngressTrafficRateAboveCriticalThreshold

Table 6-571 OcnrfTotalIngressTrafficRateAboveCriticalThreshold

Field Details
Description 'Total Ingress traffic Rate is above critical threshold.(current value is: {{ $value }})'
Summary 'timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }}: Traffic Rate is more than 52000 requests per second'
Severity Critical
Condition

The total NRF Ingress Message rate has crossed the configured critical threshold of 52000 TPS.

Default value of this alert trigger point in the alert file is when NRF Ingress Rate crosses 52000 TPS.

OID 1.3.6.1.4.1.323.5.3.36.1.2.7003
Metric Used 'oc_ingressgateway_http_requests_total'
Recommended Actions

The alert is cleared when the Ingress traffic rate falls below the critical threshold.

Note: The threshold is configurable in the alert file.

Reassess why the NRF is receiving additional traffic (for example, Mated site NRF is unavailable in georedundancy scenario). If this alert is unexpected, contact My Oracle Support.
Steps:
  1. Refer Grafana to determine which service is receiving high traffic.
  2. Refer Ingress gateway section in Grafana to determine the increase in 4xx and 5xx error codes.
  3. Check Ingress gateway logs on Kibana to determine the reason for the errors.
Available in OCI No
6.3.1.21 OcnrfTransactionErrorRateAbove0Dot1Percent

Table 6-572 OcnrfTransactionErrorRateAbove0Dot1Percent

Field Details
Description 'Transaction Error rate is above 0.1 Percent of Total Transactions (current value is {{ $value }})'
Summary 'timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }}: Transaction Error Rate detected above 0.1 Percent of Total Transactions'
Severity Warning
Condition The number of failed transactions is above 0.1 percent of the total transactions.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7004
Metric Used 'oc_ingressgateway_http_responses_total'
Recommended Actions

The alert is cleared when the number of failure transactions is below 0.1 percent of the total transactions or when the number of failed transactions crosses the 1% threshold, in which case the OcnrfTransactionErrorRateAbove1Percent is raised.

Steps:

  1. Check the service specific metrics to understand the specific service request errors.

    For example: ocnrf_nfDiscover_tx_responses_total with statusCode ~= 2xx.

  2. Check metrics per service, per method:

    For example, discovery requests can be determined from the following metrics:

    Metrics="oc_ingressgateway_http_responses_total"

    Method="GET"

    NFServiceType="nnrf-disc"

    Route_path="/nnrf-disc/v1/nf-instances/**"

    Status="503 SERVICE_UNAVAILABLE"

  3. If guidance is required, contact My Oracle Support.
Available in OCI No
6.3.1.22 OcnrfTransactionErrorRateAbove1Percent

Table 6-573 OcnrfTransactionErrorRateAbove1Percent

Field Details
Description 'Transaction Error rate is above 1 Percent of Total Transactions (current value is {{ $value }})'
Summary 'timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }}: Transaction Error Rate detected above 1 Percent of Total Transactions'
Severity Warning
Condition When the number of failed transactions is above 1 percent of the total transactions.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7005
Metric Used 'oc_ingressgateway_http_responses_total'
Recommended Actions

The alert is cleared when the number of failure transactions is below 1% of the total transactions or when the number of failed transactions crosses the 10% threshold, in which case the OcnrfTransactionErrorRateAbove10Percent is raised.

Steps:

  1. Check the service specific metrics to understand the specific service request errors.

    For example: ocnrf_nfDiscover_tx_responses_total with statusCode ~= 2xx.

  2. Check metrics per service, per method:

    For example, discovery requests can be determined from the following metrics:

    Metrics="oc_ingressgateway_http_responses_total"

    Method="GET"

    NFServiceType="nnrf-disc"

    Route_path="/nnrf-disc/v1/nf-instances/**"

    Status="503 SERVICE_UNAVAILABLE"

  3. If guidance is required, contact My Oracle Support.
Available in OCI No
6.3.1.23 OcnrfTransactionErrorRateAbove10Percent

Table 6-574 OcnrfTransactionErrorRateAbove10Percent

Field Details
Description 'Transaction Error rate is above 10 Percent of Total Transactions (current value is {{ $value }})'
Summary 'timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }}: Transaction Error Rate detected above 10 Percent of Total Transactions'
Severity Minor
Condition The number of failed transactions has crossed the minor threshold of 10 percent of the total transactions.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7006
Metric Used 'oc_ingressgateway_http_responses_total'
Recommended Actions

The alert is cleared when the number of failure transactions is below 10 percent of the total transactions or when the number of failed transactions crosses the 25 percent threshold, in which case the OcnrfTransactionErrorRateAbove25Percent is raised.

Steps:

  1. Check the service specific metrics to understand the specific service request errors.

    For example: ocnrf_nfDiscover_tx_responses_total with statusCode ~= 2xx.

  2. Check metrics per service, per method:

    For example, discovery requests can be determined from the following metrics:

    Metrics="oc_ingressgateway_http_responses_total"

    Method="GET"

    NFServiceType="nnrf-disc"

    Route_path="/nnrf-disc/v1/nf-instances/**"

    Status="503 SERVICE_UNAVAILABLE"

  3. If guidance is required, contact My Oracle Support.
Available in OCI No
6.3.1.24 OcnrfTransactionErrorRateAbove25Percent

Table 6-575 OcnrfTransactionErrorRateAbove25Percent

Field Details
Description 'Transaction Error rate is above 25 Percent of Total Transactions (current value is {{ $value }})'
Summary 'timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }}: Transaction Error Rate detected above 25 Percent of Total Transactions'
Severity Major
Condition The number of failed transactions has crossed the minor threshold of 25 percent of the total transactions.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7007
Metric Used 'oc_ingressgateway_http_responses_total'
Recommended Actions

The alert is cleared when the number of failure transactions is below 25 percent of the total transactions or when the number of failed transactions crosses the 50 percent threshold, in which case the OcnrfTransactionErrorRateAbove50Percent is raised.

Steps:

  1. Check the service specific metrics to understand the specific service request errors.

    For example: ocnrf_nfDiscover_tx_responses_total with statusCode ~= 2xx.

  2. Check metrics per service, per method:

    For example, discovery requests can be determined from the following metrics:

    Metrics="oc_ingressgateway_http_responses_total"

    Method="GET"

    NFServiceType="nnrf-disc"

    Route_path="/nnrf-disc/v1/nf-instances/**"

    Status="503 SERVICE_UNAVAILABLE"

  3. If guidance is required, contact My Oracle Support.
Available in OCI No
6.3.1.25 OcnrfTransactionErrorRateAbove50Percent

Table 6-576 OcnrfTransactionErrorRateAbove50Percent

Field Details
Description 'Transaction Error rate is above 50 Percent of Total Transactions (current value is {{ $value }})'
Summary 'timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }}: Transaction Error Rate detected above 50 Percent of Total Transactions'
Severity Critical
Condition The number of failed transactions has crossed the minor threshold of 50 percent of the total transactions.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7008
Metric Used 'oc_ingressgateway_http_responses_total'
Recommended Actions

The alert is cleared when the number of failure transactions is below 50 percent of the total transactions.

Steps:

  1. Check the service specific metrics to understand the specific service request errors.

    For example: ocnrf_nfDiscover_tx_responses_total with statusCode ~= 2xx.

  2. Check metrics per service, per method:

    For example, discovery requests can be determined from the following metrics:

    Metrics="oc_ingressgateway_http_responses_total"

    Method="GET"

    NFServiceType="nnrf-disc"

    Route_path="/nnrf-disc/v1/nf-instances/**"

    Status="503 SERVICE_UNAVAILABLE"

  3. If guidance is required, contact My Oracle Support.
Available in OCI No
6.3.1.26 OcnrfTotalEgressTrafficRateAboveCriticalThreshold

Table 6-577 OcnrfTotalEgressTrafficRateAboveCriticalThreshold

Field Details
Description 'Egress traffic rate is above the configured critical threshold. (current value is: {{ $value }})'
Summary ''kubernetes_namespace: {{$labels.kubernetes_namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }}: Traffic Rate is above 51600 requests per second'
Severity Critical
Condition This alarm is raised when the Egress traffic rate is greater than the critical configured threshold.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7109
Metric Used oc_egressgateway_http_requests_total
Recommended Actions The alert is cleared either when the total discovery rate falls below the critical threshold.

Note: The threshold is configurable in the alert file. Reassess why the NRF is receiving additional traffic (for example, Mated site NRF is unavailable in georedundancy scenario). If this alert is unexpected, contact My Oracle Support.

Steps:

  1. Refer Grafana to determine which service is receiving high traffic.
  2. Refer Egress Gateway section in Grafana to determine the increase in 4xx and 5xx error codes.
  3. Check Egress Gateway logs on Kibana to determine the reason for the errors.
Available in OCI No
6.3.1.27 OcnrfTotalForwardingTrafficRateAboveCriticalThreshold

Table 6-578 OcnrfTotalForwardingTrafficRateAboveCriticalThreshold

Field Details
Description 'NRF-NRF Forwarding Rate is above the configured critical threshold. (current value is: {{ $value }})'
Summary 'kubernetes_namespace: $labels.kubernetes_namespace, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }}: Traffic Rate is above 5200 requests per second.'
Severity Critical
Condition This alarm is raised when the rate between NRF and NRF Forwarding is greater than the critical configured threshold.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7110
Metric Used ocnrf_forward_nfDiscover_tx_requests_total
Recommended Actions The alert is cleared either when the total NRF Forwarding rate falls below the critical threshold.

Note: The threshold is configurable in the alert file. Reassess why the NRF is receiving additional traffic (for example, Mated site NRF is unavailable in georedundancy scenario). If this alert is unexpected, contact My Oracle Support.

Steps:

  1. Refer Grafana to determine which service is receiving high traffic.
  2. Refer NRF Forwarding section in Grafana to determine the increase in 4xx and 5xx error codes.
  3. Check NRF Forwarding logs on Kibana to determine the reason for the errors.
Available in OCI No
6.3.1.28 OcnrfHeapUsageCrossedMinorThreshold

Table 6-579 OcnrfHeapUsageCrossedMinorThreshold

Field Details
Description 'OCNRF Heap Usage for pod {{ $labels.pod }} has crossed the configured minor threshold (50%) (value={{ $value }}) of its limit.'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, podname: {{$labels.pod}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : Heap Usage of pod exceeded 50% of its limit.'
Severity Minor
Condition This alert is raised when the Java memory heap usage of pods exceeds the configured minor threshold.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7126
Metric Used jvm_memory_used_bytes
Recommended Actions

The alert is cleared when the heap usage of pods falls below the minor threshold.

Note: The threshold is configurable in the alert file. If this alert is unexpected, contact My Oracle Support.

Steps:

  1. Identify the pods which are raised in the alert.
  2. Refer Resource usage in Grafana dashboard to get the memory usage.
  3. Collect the pod logs and top output of the pods.
  4. Contact My Oracle Support.
Available in OCI No
6.3.1.29 OcnrfHeapUsageCrossedMajorThreshold

Table 6-580 OcnrfHeapUsageCrossedMajorThreshold

Field Details
Description 'OCNRF Heap Usage for pod {{ $labels.pod }} has crossed the configured major threshold (60%) (value={{ $value }}) of its limit.'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, podname: {{$labels.pod}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : Heap Usage of pod is more than or equal to 60% and less than 70% of its limit.'
Severity Major
Condition This alert is raised when the Java memory heap usage of pods exceeds the configured major threshold.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7127
Metric Used jvm_memory_used_bytes
Recommended Actions

The alert is cleared when the heap usage of pods falls below the major threshold.

Note: The threshold is configurable in the alert file. If this alert is unexpected, contact My Oracle Support.

Steps:

  1. Identify the pods which are raised in the alert.
  2. Refer Resource usage in Grafana dashboard to get the memory usage.
  3. Collect the pod logs and top output of the pods.
  4. Contact My Oracle Support.
Available in OCI No
6.3.1.30 OcnrfHeapUsageCrossedCriticalThreshold

Table 6-581 OcnrfHeapUsageCrossedCriticalThreshold

Field Details
Description 'OCNRF Heap Usage for pod {{ $labels.pod }} has crossed the configured critical threshold (70%) (value={{ $value }}) of its limit.'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, podname: {{$labels.pod}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : Heap Usage of pod is more than 70% of its limit.'
Severity Critical
Condition This alert is raised when the Java memory heap usage of pods exceeds the configured critical threshold.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7128
Metric Used jvm_memory_used_bytes
Recommended Actions

The alert is cleared when the heap usage of pods falls below the critical threshold.

Note: The threshold is configurable in the alert file. If this alert is unexpected, contact My Oracle Support.

Steps:

  1. Identify the pods which are raised in the alert.
  2. Refer Resource usage in Grafana dashboard to get the memory usage.
  3. Collect the pod logs and top output of the pods.
  4. Contact My Oracle Support.
Available in OCI No

6.3.2 Service Level Alerts

This section lists the service level alerts.

6.3.2.1 OcnrfAccessTokenRequestsRejected

Table 6-582 OcnrfAccessTokenRequestsRejected

Field Details
Description 'AccessToken request(s) have been rejected by OCNRF (current value is: {{ $value }})'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}},nrflevel:{{$labels.NrfLevel}}, podname: {{$labels.kubernetes_pod_name}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} AccessToken Request has been rejected by OCNRF.'
Severity Warning
Condition NRF rejected an AccessToken Request
OID 1.3.6.1.4.1.323.5.3.36.1.2.7014
Metric Used 'ocnrf_accessToken_tx_responses_total'
Recommended Actions The alert is cleared automatically.
Steps:
  1. The Rejection Reason is present in the alert.
  2. In case the RejectionReason is AuthScreeningFailed/ClientNotAuthorized, either the configurations need to be reevaluated or check the consumer NF that has requested for unauthorized token. For more information about token information, see Oracle Communications Cloud Native Core, Network Repository Function REST Specification Guide.
  3. For other reasons, follow the RejectionReason.
Available in OCI No
6.3.2.2 OcnrfAuditorMultiplePodUnavailable

Table 6-583 OcnrfAuditorMultiplePodUnavailable

Field Details
Description Ocnrf Auditor Multiple Pods are Unavailable in deployment
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : Ocnrf Auditor Multiple Pods are Unavailable'
Severity Critical
Condition Ocnrf Auditor Multiple Pods are Unavailable.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7075
Metric Used NA
Recommended Actions

This alert is raised due to auditor multiple pods are unavailable. This alert is cleared automatically when the pods are available.

Available in OCI No
6.3.2.3 OcnrfAppInfoMultiplePodUnavailable

Table 6-584 OcnrfAppInfoMultiplePodUnavailable

Field Details
Description Ocnrf AppInfo Multiple Pods are Unavailable in deployment
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : Ocnrf AppInfo Multiple Pods are Unavailable'
Severity Critical
Condition Ocnrf Auditor Multiple Pods are Unavailable.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7076
Metric Used NA
Recommended Actions

This alert is raised due to App-Info multiple pods are unavailable. This alert is cleared automatically when the pods are available.

Available in OCI No
6.3.2.4 OcnrfPerfInfoMultiplePodUnavailable

Table 6-585 OcnrfPerfInfoMultiplePodUnavailable

Field Details
Description Ocnrf PerfInfo Multiple Pods are Unavailable in deployment
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : Ocnrf PerfInfo Multiple Pods are Unavailable'
Severity Critical
Condition Ocnrf PerfInfo Multiple Pods are Unavailable.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7077
Metric Used NA
Recommended Actions

This alert is raised due to perf-Info multiple pods are unavailable. This alert is cleared automatically when the pods are available.

Available in OCI No
6.3.2.5 OcnrfTotalSLFRateAboveCriticalThreshold

Table 6-586 OcnrfTotalSLFRateAboveCriticalThreshold

Field Details
Description 'NRF-SLF Rate is above the configured critical threshold. (current value is: {{ $value }})'
Summary 'kubernetes_namespace: $labels.kubernetes_namespace, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }}: Traffic Rate is above 45600 requests per second.'
Severity Critical
Condition This alarm is raised when the rate between NRF and SLF reaches is greater than the critical configured threshold.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7111
Metric Used ocnrf_SLF_tx_requests_total
Recommended Actions The alert is cleared either when the total SLF rate falls below the critical threshold.

Note: The threshold is configurable in the alert file. Reassess why the NRF is receiving additional traffic (for example, Mated site NRF is unavailable in georedundancy scenario). If this alert is unexpected, contact My Oracle Support.

Steps:

  1. Refer Grafana to determine which service is receiving high traffic.
  2. Refer SLF section in Grafana to determine the increase in 4xx and 5xx error codes.
  3. Check SLF logs on Kibana to determine the reason for the errors.
Available in OCI No
6.3.2.6 OcnrfTotalDiscoveryRateAboveCriticalThreshold

Table 6-587 OcnrfTotalDiscoveryRateAboveCriticalThreshold

Field Details
Description 'Total Discovery Rate is above the configured critical threshold. (current value is: {{ $value }})'
Summary 'kubernetes_namespace: $labels.kubernetes_namespace, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }}: Traffic Rate is above 51600 requests per second.'
Severity Critical
Condition This alarm is raised when the total discovery rate is greater than the critical configured threshold.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7112
Metric Used ocnrf_nfDiscover_rx_requests_total
Recommended Actions The alert is cleared when the total discovery rate falls below the critical threshold.

Note: The threshold is configurable in the alert file. Reassess why the NRF is receiving additional traffic (for example, Mated site NRF is unavailable in georedundancy scenario). If this alert is unexpected, contact My Oracle Support.

Steps:

  1. Refer Grafana to determine which service is receiving high traffic.
  2. Refer Discovery section in Grafana to determine the increase in 4xx and 5xx error codes.
  3. Check Discovery logs on Kibana to determine the reason for the errors.
Available in OCI No
6.3.2.7 OcnrfAccessTokenRequestsAboveThreshold

Table 6-588 OcnrfAccessTokenRequestsAboveThreshold

Field Details
Description 'Total Access token request rate is above the configured critical threshold. (current value is: {{ $value }})'
Summary 'namespace: {{$labels.kubernetes_namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }}: Total Access token request rate is above 5'
Severity Critical
Condition The alert is raised when the rate of Access Token requests is greater than the configured threshold.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7115
Metric Used ocnrf_accessToken_rx_requests_total
Recommended Actions The alert is cleared when the total number of access token request rate falls below the critical threshold.

Note: The threshold is configurable in the alert file. Reassess why the NRF is receiving additional traffic (for example, Mated site NRF is unavailable in georedundancy scenario). If this alert is unexpected, contact My Oracle Support.

Steps:

  1. Refer the NfAccessToken Section in Grafana to determine increase in TPS.
  2. Refer the Grafana to determine increase in failure responses.
Available in OCI No
6.3.2.8 OcnrfNfUpdateRequestsAboveThreshold

Table 6-589 OcnrfNfUpdateRequestsAboveThreshold

Field Details
Description 'Total NfUpdate request rate is above the configured critical threshold. (current value is: {{ $value }})'
Summary 'namespace: {{$labels.kubernetes_namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }}: Total NfUpdate request rate is above 5'
Severity Critical
Condition This alert is raised when the total number of NfUpdate requests is greater than the configured threshold.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7116
Metric Used ocnrf_nfUpdate_rx_requests_total
Recommended Actions The alert is cleared when the total number of NfUpdate request falls below the critical threshold.

Note: The threshold is configurable in the alert file. Reassess why the NRF is receiving additional traffic (for example, Mated site NRF is unavailable in georedundancy scenario). If this alert is unexpected, contact My Oracle Support.

Steps:

  1. Refer the NfRegister Section in Grafana to determine increase in TPS.
  2. Refer the Grafana to determine increase in failure responses.
Available in OCI No
6.3.2.9 OcnrfRegisteredNfCountAboveThreshold

Table 6-590 OcnrfRegisteredNfCountAboveThreshold

Field Details
Description 'Total Number of active registrations in OCNRF is above critical threshold. (current value is: {{ $value }})'
Summary 'namespace: {{$labels.kubernetes_namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }}: Total Number of active registrations in OCNRF is above 260'
Severity Critical
Condition The alert is raised when the total number of NFs registered in the set is greater than the configured threshold.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7118
Metric Used ocnrf_nf_registered_count
Recommended Actions The alert is cleared when the total number active registrations in NRF falls below the critical threshold.

Note: The threshold is configurable in the alert file. Reassess why the NRF is receiving additional registrations. If this alert is unexpected, contact My Oracle Support.

Step:

  1. Refer Grafana to determine the number of NFs per nfType.
Available in OCI No
6.3.2.10 OcnrfNfHeartBeatRequestsAboveThreshold

Table 6-591 OcnrfNfHeartBeatRequestsAboveThreshold

Field Details
Description 'Total NfHeartBeat request rate is above the configured critical threshold. (current value is: {{ $value }})'
Summary 'namespace: {{$labels.kubernetes_namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }}: Total NfHeartBeat request rate is above 52'
Severity Critical
Condition This alert is raised when the total number of NfHeartBeat requests is greater than the configured threshold.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7117
Metric Used ocnrf_nfHeartBeat_rx_requests_total
Recommended Actions The alert is cleared when the total number of NfHeartBeat request falls below the critical threshold.

Note: The threshold is configurable in the alert file. Reassess why the NRF is receiving additional traffic (for example, Mated site NRF is unavailable in georedundancy scenario). If this alert is unexpected, contact My Oracle Support.

Steps:

  1. Refer the NfRegister Section in Grafana to determine increase in TPS.
  2. Refer the Grafana to determine increase in failure responses.
Available in OCI No
6.3.2.11 OcnrfRegisteredNfCountAboveThreshold

Table 6-592 OcnrfRegisteredNfCountAboveThreshold

Field Details
Description 'Total Number of active registrations in OCNRF is above critical threshold. (current value is: {{ $value }})'
Summary 'namespace: {{$labels.kubernetes_namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }}: Total Number of active registrations in OCNRF is above 260'
Severity Critical
Condition The alert is raised when the total number of NFs registered in the set is greater than the configured threshold.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7118
Metric Used ocnrf_nf_registered_count
Recommended Actions The alert is cleared when the total number active registrations in NRF falls below the critical threshold.

Note: The threshold is configurable in the alert file. Reassess why the NRF is receiving additional registrations. If this alert is unexpected, contact My Oracle Support.

Step:

  1. Refer Grafana to determine the number of NFs per nfType.
Available in OCI No
6.3.2.12 OcnrfTotalSubscriptionsAboveThreshold

Table 6-593 OcnrfTotalSubscriptionsAboveThreshold

Field Details
Description 'Total Number of active subscriptions in OCNRF is above the critical threshold. (current value is: {{ $value }})'
Summary 'namespace: {{$labels.kubernetes_namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }}: Total Number of active subscriptions in OCNRF is above 1000.'
Severity Critical
Condition This alert is raised when the total number of active subscriptions in NRF is greater than the configured threshold.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7121
Metric Used ocnrf_nfset_active_subscriptions
Recommended Actions The alert is cleared when the total number active subscriptions in NRF is less than the critical threshold.

Note: The threshold is configurable in the alert file. Reassess why the NRF has received additional subscriptions (for example, Mated site NRF is unavailable in georedundancy scenario). If this alert is unexpected, contact My Oracle Support.

Steps:

  1. Refer Grafana to determine the total number of subscriptions created.
  2. Verify if Subscription Limit feature has been enabled using subscriptionLimit.featureStatus parameter. For more information, see Oracle Communications Cloud Native Core, Network Repository Function User Guide.
  3. Assess which NFs are creating the additional subscriptions.
Available in OCI No
6.3.2.13 OcnrfDiscoveryRequestsForUDRAboveThreshold

Table 6-594 OcnrfDiscoveryRequestsForUDRAboveThreshold

Field Details
Description 'Total NfDiscover request rate for nfType UDR is above the configured critical threshold. (current value is: {{ $value }})'
Summary 'namespace: {{$labels.kubernetes_namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }}: Total NfDiscover request rate for nfType UDR is above above 700'
Severity Critical
Condition This alert is raised when the rate of nfDiscover requests for nfType UDR is greater than the configured threshold.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7122
Metric Used ocnrf_nfDiscover_rx_requests_total
Recommended Actions The alert is cleared when the rate of nfDiscover requests for nfType UDR is below than the critical threshold.

Note: The threshold is configurable in the alert file. Reassess why the NRF is receiving additional traffic for UDR. If this alert is unexpected, contact My Oracle Support.
Available in OCI No
6.3.2.14 OcnrfDiscoveryRequestsForUDMAboveThreshold

Table 6-595 OcnrfDiscoveryRequestsForUDMAboveThreshold

Field Details
Description 'Total NfDiscover request rate for nfType UDM is above the configured critical threshold. (current value is: {{ $value }})'
Summary 'namespace: {{$labels.kubernetes_namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }}: Total NfDiscover request rate for nfType UDM is above above 46000'
Severity Critical
Condition This alert is raised when the rate of nfDiscover requests for nfType UDM is greater than the configured threshold.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7123
Metric Used ocnrf_nfDiscover_rx_requests_total
Recommended Actions The alert is cleared when the rate of nfDiscover requests for nfType UDM is below than the critical threshold.

Note: The threshold is configurable in the alert file. Reassess why the NRF is receiving additional traffic for UDM. If this alert is unexpected, contact My Oracle Support.
Available in OCI No
6.3.2.15 OcnrfDiscoveryRequestsForAMFAboveThreshold

Table 6-596 OcnrfDiscoveryRequestsForAMFAboveThreshold

Field Details
Description 'Total NfDiscover request rate for nfType AMF is above the configured critical threshold. (current value is: {{ $value }})'
Summary 'namespace: {{$labels.kubernetes_namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }}: Total NfDiscover request rate for nfType AMF is above 2500'
Severity Critical
Condition This alert is raised when the rate of nfDiscover requests for nfType AMF is greater than the configured threshold.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7124
Metric Used ocnrf_nfDiscover_rx_requests_total
Recommended Actions The alert is cleared when the rate of nfDiscover requests for nfType AMF is below than the critical threshold.

Note: The threshold is configurable in the alert file. Reassess why the NRF is receiving additional traffic for AMF. If this alert is unexpected, contact My Oracle Support.
Available in OCI No
6.3.2.16 OcnrfDiscoveryRequestsForSMFAboveThreshold

Table 6-597 OcnrfDiscoveryRequestsForSMFAboveThreshold

Field Details
Description 'Total NfDiscover request rate for nfType SMF is above the configured critical threshold. (current value is: {{ $value }})'
Summary 'namespace: {{$labels.kubernetes_namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }}: Total NfDiscover request rate for nfType SMF is above 4500'
Severity Critical
Condition This alert is raised when the rate of nfDiscover requests for nfType SMF is greater than the configured threshold.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7125
Metric Used ocnrf_nfDiscover_rx_requests_total
Recommended Actions The alert is cleared when the rate of nfDiscover requests for nfType SMF is below than the critical threshold.

Note: The threshold is configurable in the alert file. Reassess why the NRF is receiving additional traffic for SMF. If this alert is unexpected, contact My Oracle Support.
Available in OCI No

6.3.3 NfProfile Status Change Alerts

This section lists the alerts raised when there is status change in NfProfile.

6.3.3.1 OcnrfRegisteredPCFsBelowCriticalThreshold

Table 6-598 OcnrfRegisteredPCFsBelowCriticalThreshold

Field Details
Description 'The number of registered NFs detected below critical threshold (current value is: {{ $value }})'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, nftype:{{$labels.RequesterNfType}}, nrflevel:{{$labels.NrfLevel}}, podname: {{$labels.kubernetes_pod_name}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }}: The number of registered NFs detected below critical threshold.'
Severity Critical
Condition

The number of NFs of the given NFType PCF currently registered with NRF is below the critical threshold.

Note: Operator can add similar alerts for each NfType and configure the corresponding thresholds as required.

Default value of this alert trigger point in the alert file is when registered PCFs count with NRF is below 2.

OID 1.3.6.1.4.1.323.5.3.36.1.2.7009
Metric Used 'ocnrf_active_registrations_count'
Recommended Actions

The alert is cleared when the number of registered PCFs is above the critical threshold.

Steps:
  1. Check if there is traffic for requests other than registration (for example, discovery requests). This ensures that NRF FQDN is reachable from other NFs and Ingress Gateway is up and running.
  2. Check if ingress gateway pod is up and running:
    kubectl get po -n <namespace>
  3. Check for registration pod logs on Kibana for ERROR WARN logs.
  4. In case the issue persists, capture all the outputs for the above steps and contact My Oracle Support.

    Note: Use CNC NF Data Collector tool for capturing logs. For more information on how to collect logs using Data Collector tool, see Oracle Communications Cloud Native Core, Network Function Data Collector User Guide.

Notes
  1. Operator can configure the threshold values to the number of NFs of type PCF expected within the network.
  2. PCFs with NFStatus as 'SUSPENDED' or "UNDISCOVERABLE' are considered as unregistered.
  3. Operator can configure the RequesterNfType expected within the network.
  4. Operator can add similar alerts for each NfType and configure the corresponding thresholds as required.
Available in OCI No
6.3.3.2 OcnrfRegisteredPCFsBelowMajorThreshold

Table 6-599 OcnrfRegisteredPCFsBelowMajorThreshold

Field Details
Description 'The number of registered NFs detected below major threshold (current value is: {{ $value }})'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, nftype:{{$labels.NfType}}, nrflevel:{{$labels.NrfLevel}}, podname: {{$labels.kubernetes_pod_name}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }}: The number of registered NFs detected below major threshold.'
Severity Major
Condition

The number of NFs of the given NFType PCF currently registered with NRF is below the major threshold.

Note: Operator can add similar alerts for each NfType and configure the corresponding thresholds as required.

Default value of this alert trigger point in the alert file is when Registered PCFs count with NRF is greater than or equal to 2 and below 10.

OID 1.3.6.1.4.1.323.5.3.36.1.2.7010
Metric Used 'ocnrf_active_registrations_count'
Recommended Actions

The alert is cleared when the number of registered PCFs is above the major threshold.

Steps:
  1. Check if there is traffic for requests other than registration (for example, discovery requests). This ensures that NRF FQDN is reachable from other NFs and Ingress Gateway is up and running.
  2. Check if Ingress Gateway pod is up and running:
    kubectl get po -n <namespace>
  3. Check for registration pod logs on Kibana for ERROR WARN logs.
  4. In case the issue persists, capture all the outputs for the above steps and contact My Oracle Support.

    Note: Use CNC NF Data Collector tool for capturing logs. For more information on how to collect logs using Data Collector tool, see Oracle Communications Cloud Native Core, Network Function Data Collector User Guide.

Notes
  1. Operator can configure the threshold values with respect to the number of NFs of type PCF expected within the network.
  2. PCFs with NFStatus as 'SUSPENDED' or "UNDISCOVERABLE' are considered as unregistered.
  3. Operator can configure the RequesterNfType expected within the network.
  4. Operator can add similar alerts for each NfType and configure the corresponding thresholds as required.
Available in OCI No
6.3.3.3 OcnrfRegisteredPCFsBelowMinorThreshold

Table 6-600 OcnrfRegisteredPCFsBelowMinorThreshold

Field Details
Description 'The number of registered NFs detected below minor threshold (current value is: {{ $value }})'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, nftype:{{$labels.NfType}}, nrflevel:{{$labels.NrfLevel}}, podname: {{$labels.kubernetes_pod_name}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }}: The number of registered NFs detected below minor threshold.'
Severity Minor
Condition

The number of NFs of the given NFType PCF currently registered with NRF is below the minor threshold.

Note: Operator can add similar alerts for each NfType and configure the corresponding thresholds as required.

Default value of this alert trigger point in the alert file is when registered PCFs count with NRF is greater than or equal to 10 and below 20.

OID 1.3.6.1.4.1.323.5.3.36.1.2.7011
Metric Used 'ocnrf_active_registrations_count'
Recommended Actions

The alert is cleared when the number of registered PCFs is above the minor threshold.

Steps:
  1. Check if there is traffic for requests other than registration (for example, discovery requests). This ensures that NRF FQDN is reachable from other NFs and Ingress Gateway is up and running.
  2. Check if ingress gateway pod is up and running:
    kubectl get po -n <namespace>
  3. Check for Registration pod logs on Kibana for ERROR WARN logs.
  4. In case the issue persists, capture all the outputs for the above steps and contact My Oracle Support.

    Note: Use CNC NF Data Collector tool for capturing logs. For more information on how to collect logs using Data Collector tool, see Oracle Communications Cloud Native Core, Network Function Data Collector User Guide.

Notes
  1. Operator can configure the threshold values with respect to the number of NFs of type PCF expected within the network.
  2. PCFs with NFStatus as 'SUSPENDED' or "UNDISCOVERABLE' are considered as unregistered.
  3. Operator can configure the RequesterNfType expected within the network.
  4. Operator can add similar alerts for each NfType and configure the corresponding thresholds as required.
Available in OCI No
6.3.3.4 OcnrfRegisteredPCFsBelowThreshold

Table 6-601 OcnrfRegisteredPCFsBelowThreshold

Field Details
Description 'The number of registered NFs is approaching minor threshold (current value is: {{ $value }})'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, nftype:{{$labels.NfType}}, nrflevel:{{$labels.NrfLevel}}, podname: {{$labels.kubernetes_pod_name}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }}: The number of registered NFs approaching minor threshold.'
Severity Warning
Condition

The number of NFs of the given NFType PCF currently registered with NRF is approaching minor threshold.

Note: Operator can add similar alerts for each NfType and configure the corresponding thresholds as required.

Default value of this alert trigger point in the alert file is when registered PCFs count with NRF is greater than or equal to 20 and below 30.

OID 1.3.6.1.4.1.323.5.3.36.1.2.7012
Metric Used 'ocnrf_active_registrations_count'
Recommended Actions

The alert is cleared when the number of registered PCFs is approaching minor threshold.

Steps:
  1. Check if there is traffic for requests other than registration (for example, discovery requests). This ensures that NRF FQDN is reachable from other NFs and Ingress Gateway is up and running.
  2. Check if Ingress Gateway pod is up and running:
    kubectl get po -n <namespace>
  3. Check for Registration pod logs on Kibana for ERROR WARN logs.
  4. In case the issue persists, capture all the outputs for the above steps and contact My Oracle Support.

    Note: Use CNC NF Data Collector tool for capturing logs. For more information on how to collect logs using Data Collector tool, see Oracle Communications Cloud Native Core, Network Function Data Collector User Guide.

Notes
  1. Operator can configure the threshold values with respect to the number of NFs of type PCF expected within the network.
  2. PCFs with NFStatus as 'SUSPENDED' or "UNDISCOVERABLE' are considered as unregistered.
  3. Operator can configure the RequesterNfType expected within the network.
  4. Operator can add similar alerts for each NfType and configure the corresponding thresholds as required.
Available in OCI No
6.3.3.5 OcnrfTotalNFsRegisteredBelowCriticalThreshold

Table 6-602 OcnrfTotalNFsRegisteredBelowCriticalThreshold

Field Details
Description 'Number of active registrations in OCNRF (current value is: {{ $value }}) is below critical threshold'
Summary kubernetes_namespace: {{$labels.kubernetes_namespace}},nrflevel:{{$labels.NrfLevel}}, podname: {{$labels.kubernetes_pod_name}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : Active registrations count.
Severity Critical
Condition The total number of NFs currently in "REGISTERED" state with the NRF is below the critical threshold.

Note: The threshold values are provided as an example. User can configure the threshold value as per the requirement.

OID 1.3.6.1.4.1.323.5.3.36.1.2.7042
Metric Used 'ocnrf_active_registrations_count'
Recommended Actions The alert is cleared when the number of registered NFs is above the critical threshold.
Steps:
  1. Check if there is traffic for requests other than registration (for example, discovery requests). This ensures that NRF FQDN is reachable from other NFs and Ingress Gateway is up and running.
  2. Check if Ingress Gateway pod is up and running:
    kubectl get po -n <namespace>
  3. Check for registration pod logs on Kibana for ERROR WARN logs.
  4. In case the issue persists, capture all the outputs for the above steps and contact My Oracle Support.

    Note: Use CNC NF Data Collector tool for capturing logs. For more information on how to collect logs using Data Collector tool, see Oracle Communications Cloud Native Core, cnDBTier User Guide.

Notes
  1. Operator can configure the threshold values with respect to the number of NFs expected within the network.
  2. NFs with NFStatus as 'SUSPENDED' or "UNDISCOVERABLE' are not considered as registered.
Available in OCI Yes
6.3.3.6 OcnrfTotalNFsRegisteredBelowMajorThreshold

Table 6-603 OcnrfTotalNFsRegisteredBelowMajorThreshold

Field Details
Description 'Number of active registrations in OCNRF (current value is: {{ $value }}) is below major threshold'
Summary kubernetes_namespace: {{$labels.kubernetes_namespace}},nrflevel:{{$labels.NrfLevel}}, podname: {{$labels.kubernetes_pod_name}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : Active registrations count.
Severity Major
Condition The total number of NFs currently in "REGISTERED" state with the NRF is below the major threshold.

Note: The threshold values are provided as an example. The user can configure the threshold value as per the requirement.

OID 1.3.6.1.4.1.323.5.3.36.1.2.7043
Metric Used 'ocnrf_active_registrations_count'
Recommended Actions The alert is cleared when the number of registered NFs is above the major threshold.
Steps:
  1. Check if there is traffic for requests other than registration (for example, discovery requests). This ensures that NRF FQDN is reachable from other NFs and Ingress Gateway is up and running.
  2. Check if Ingress Gateway pod is up and running:
    kubectl get po -n <namespace>
  3. Check for Registration pod logs on Kibana for ERROR WARN logs.
  4. In case the issue persists, capture all the outputs for the above steps and contact My Oracle Support.

    Note: Use CNC NF Data Collector tool for capturing logs. For more information on capturing logs, see Oracle Communications Cloud Native Core, Network Function Data Collector User Guide.

Notes
  1. Operator can configure the threshold values with respect to the number of NFs expected within the network.
  2. NFs with NFStatus as 'SUSPENDED' or "UNDISCOVERABLE' are not considered as registered.
Available in OCI Yes
6.3.3.7 OcnrfTotalNFsRegisteredBelowMinorThreshold

Table 6-604 OcnrfTotalNFsRegisteredBelowMinorThreshold

Field Details
Description 'Number of active registrations in OCNRF (current value is: {{ $value }}) is below minor threshold'
Summary kubernetes_namespace: {{$labels.kubernetes_namespace}},nrflevel:{{$labels.NrfLevel}}, podname: {{$labels.kubernetes_pod_name}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : Active registrations count.
Severity Minor
Condition The total number of NFs currently in "REGISTERED" state with the NRF is below the minor threshold.

Note: The threshold values are provided as an example. The user can configure the threshold value as per the requirement.

OID 1.3.6.1.4.1.323.5.3.36.1.2.7044
Metric Used 'ocnrf_active_registrations_count'
Recommended Actions The alert is cleared when the number of registered NFs is above the minor threshold.
Steps:
  1. Check if there is traffic for requests other than registration (for example, discovery requests). This ensures that NRF FQDN is reachable from other NFs and Ingress Gateway is up and running.
  2. Check if Ingress Gateway pod is up and running:
    kubectl get po -n <namespace>
  3. Check for registration pod logs on Kibana for ERROR WARN logs.
  4. In case the issue persists, capture all the outputs for the above steps and contact My Oracle Support.

    Note: Use CNC NF Data Collector tool for capturing logs. For more information on capturing logs, see Oracle Communications Cloud Native Core, Network Function Data Collector User Guide.

Notes
  1. Operator can configure the threshold values with respect to the number of NFs expected within the network.
  2. NFs with NFStatus as 'SUSPENDED' or "UNDISCOVERABLE' are not considered as registered.
Available in OCI Yes
6.3.3.8 OcnrfTotalNFsRegisteredApproachingMinorThreshold

Table 6-605 OcnrfTotalNFsRegisteredApproachingMinorThreshold

Field Details
Description 'Number of active registrations in OCNRF (current value is: {{ $value }}) is approaching minor threshold'
Summary kubernetes_namespace: {{$labels.kubernetes_namespace}},nrflevel:{{$labels.NrfLevel}}, podname: {{$labels.kubernetes_pod_name}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : Active registrations count.
Severity Info
Condition The total number of NFs currently in "REGISTERED" state with the NRF is approaching minor threshold.

Note: The threshold values provided as an example. The user can configure the threshold as per need.

OID 1.3.6.1.4.1.323.5.3.36.1.2.7045
Metric Used 'ocnrf_active_registrations_count'
Recommended Actions The alert is cleared when the number of registered NFs are approaching minor threshold.

Steps: No action is required. This is an information alert.

Notes
  1. Operator can configure the threshold values with respect to the number of NFs expected within the network.
  2. NFs with NFStatus as 'SUSPENDED' or "UNDISCOVERABLE' are not considered as registered.
Available in OCI Yes
6.3.3.9 OcnrfNFStatusTransitionToRegistered

Table 6-606 OcnrfNFStatusTransitionToRegistered

Field Details
Description 'NF with NF profile fqdn {{$labels.NfProfileFqdn}} NF instance id {{$labels.NfInstanceId}} NF type {{$labels.NfType}} is REGISTERED , previous status was {{$labels.PreviousStatus}}'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}},nrflevel:{{$labels.NrfLevel}},podname: {{$labels.kubernetes_pod_name}},NfInstanceId: {{$labels.NfInstanceId}},NfProfileFqdn: {{$labels.NfProfileFqdn}},NfType: {{$labels.NfType}},PreviousStatus: {{$labels.PreviousStatus}},NewStatus: {{$labels.NewStatus}},timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} NF is REGISTERED.'
Severity Info
Condition NF Instance's status transitions to REGISTERED.

Note: When multiple alerts are present for a given NF, the latest alert is always considered. The timestamp can also be seen in the "Active Since" field of the alert in Prometheus.

OID 1.3.6.1.4.1.323.5.3.36.1.2.7046
Metric Used ocnrf_nfInstance_status_change_total
Recommended Actions The alert is cleared automatically after a window of 5 minutes.

Steps:

No action is required. This is an information alert.
Available in OCI Yes
6.3.3.10 OcnrfNFServiceStatusTransitionToRegistered

Table 6-607 OcnrfNFServiceStatusTransitionToRegistered

Field Details
Description 'NF service {{$labels.NfServiceName}} and service instance id {{$labels.NfServiceInstanceId}} of NF profile fqdn {{$labels.NfProfileFqdn}} and instance id {{$labels.NfInstanceId}} is REGISTERED, previous status was {{$labels.PreviousStatus}}'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}},nrflevel:{{$labels.NrfLevel}},podname: {{$labels.kubernetes_pod_name}},NfInstanceId: {{$labels.NfInstanceId}},NfServiceName: {{$labels.NfServiceName}},NfServiceInstanceId:{{$labels.NfServiceInstanceId}},NfProfileFqdn: {{$labels.NfProfileFqdn}},NfServiceFqdn: {{$labels.NfServiceFqdn}},PreviousStatus: {{$labels.PreviousStatus}},NewStatus: {{$labels.NewStatus}},timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} NF service is REGISTERED.'
Severity Info
Condition Status of an NF Instance's service transitions to REGISTERED.

Note: When multiple alerts are present for a given NF, the latest alert is always considered. The timestamp can also be seen in the "Active Since" field of the alert in Prometheus.

OID 1.3.6.1.4.1.323.5.3.36.1.2.7047
Metric Used ocnrf_nfService_status_change_total
Recommended Actions The alert is cleared automatically after a window of 5 minutes.

Steps:

No action is required. This is an information alert.
Available in OCI Yes
6.3.3.11 OcnrfNFStatusTransitionToSuspended

Table 6-608 OcnrfNFStatusTransitionToSuspended

Field Details
Description 'NF with NF profile fqdn {{$labels.NfProfileFqdn}} NF instance id {{$labels.NfInstanceId}} NF type {{$labels.NfType}} is SUSPENDED, previous status was {{$labels.PreviousStatus}}'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}},nrflevel:{{$labels.NrfLevel}},podname: {{$labels.kubernetes_pod_name}},NfInstanceId: {{$labels.NfInstanceId}},NfProfileFqdn: {{$labels.NfProfileFqdn}},NfType: {{$labels.NfType}},PreviousStatus: {{$labels.PreviousStatus}},NewStatus: {{$labels.NewStatus}},timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} NF is SUSPENDED.'
Severity Major
Condition NF Instance's status transitions to SUSPENDED.

Note: When multiple alerts are present for a given NF, the latest alert is always considered. The timestamp can also be seen in the "Active Since" field of the alert in Prometheus.

OID 1.3.6.1.4.1.323.5.3.36.1.2.7048
Metric Used ocnrf_nfInstance_status_change_total
Recommended Actions The alert is cleared automatically after a window of 5 minutes.
Steps:
  1. Check logs in NRF registration pod for failing patch requests or check Jaeger traces to see traces for incoming requests.
  2. Check Ingress Gateway logs to see if the requests are coming.
  3. Check if the NRF pods are UP.
  4. Check for the Ingress Gateway metrics in Prometheus for PATCH requests or responses in this time frame. Confirm if the responses have any non-2xx error codes.
  5. Depending on the failure reason, take the resolution steps.
  6. In case the issue persists, capture all the outputs for the above steps and contact My Oracle Support.

    Note: Use CNC NF Data Collector tool for capturing logs. For more information on capturing logs, see Oracle Communications Cloud Native Core, Network Function Data Collector User Guide.

Available in OCI Yes
6.3.3.12 OcnrfNFServiceStatusTransitionToSuspended

Table 6-609 OcnrfNFServiceStatusTransitionToSuspended

Field Details
Description 'NF service {{$labels.NfServiceName}} and service instance id {{$labels.NfServiceInstanceId}} of NF profile fqdn {{$labels.NfProfileFqdn}} and instance id {{$labels.NfInstanceId}} is SUSPENDED, previous status was {{$labels.PreviousStatus}}'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}},nrflevel:{{$labels.NrfLevel}},podname: {{$labels.kubernetes_pod_name}},NfInstanceId: {{$labels.NfInstanceId}},NfServiceName: {{$labels.NfServiceName}},NfServiceInstanceId:{{$labels.NfServiceInstanceId}},NfProfileFqdn: {{$labels.NfProfileFqdn}},NfServiceFqdn: {{$labels.NfServiceFqdn}},PreviousStatus: {{$labels.PreviousStatus}},NewStatus: {{$labels.NewStatus}},timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} NF service is SUSPENDED.'
Severity Minor
Condition Status of an NF Instance's service transitions to SUSPENDED.

Note: When multiple alerts are present for a given NF, the latest alert is always considered. The timestamp can also be seen in the "Active Since" field of the alert in Prometheus.

OID 1.3.6.1.4.1.323.5.3.36.1.2.7049
Metric Used ocnrf_nfService_status_change_total
Recommended Actions The alert is cleared automatically after a window of 5 minutes.
Steps:
  1. Check logs in NRF registration pod for failing patch requests or check Jaeger traces to see traces for incoming requests.
  2. Check Ingress Gateway logs to see if the requests are coming.
  3. Check if the NRF pods are UP.
  4. Check for the Ingress Gateway metrics in Prometheus for PATCH requests or responses in this time frame. Confirm if the responses have any non-2xx error codes.
  5. Depending on the failure reason, take the resolution steps.
  6. In case the issue persists, capture all the outputs for the above steps and contact My Oracle Support.

    Note: Use CNC NF Data Collector tool for capturing logs. For more information on capturing logs, see Oracle Communications Cloud Native Core, Network Function Data Collector User Guide.

Available in OCI Yes
6.3.3.13 OcnrfNFStatusTransitionToUndiscoverable

Table 6-610 OcnrfNFStatusTransitionToUndiscoverable

Field Details
Description 'NF with NF profile fqdn {{$labels.NfProfileFqdn}} NF instance id {{$labels.NfInstanceId}} NF type {{$labels.NfType}} is UNDISCOVERABLE, previous status was {{$labels.PreviousStatus}}'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}},nrflevel:{{$labels.NrfLevel}},podname: {{$labels.kubernetes_pod_name}},NfInstanceId: {{$labels.NfInstanceId}},NfProfileFqdn: {{$labels.NfProfileFqdn}},NfType: {{$labels.NfType}},PreviousStatus: {{$labels.PreviousStatus}},NewStatus: {{$labels.NewStatus}},timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} NF is UNDISCOVERABLE.'
Severity Info
Condition NF Instance's status transitions to UNDISCOVERABLE.

Note: When multiple alerts are present for a given NF, the latest alert is always considered. The timestamp can also be seen in the "Active Since" field of the alert in Prometheus.

OID 1.3.6.1.4.1.323.5.3.36.1.2.7050
Metric Used ocnrf_nfInstance_status_change_total
Recommended Actions The alert is cleared automatically after a window of 5 minutes.

Steps:

  1. Check logs in NRF registration pod to verify if the NF has sent UNDISCOVERABLE status in NFRegister or NfUpdate requests or check Jaeger traces to see traces for incoming requests.
  2. If there is no such incoming request, collect the logs and contact My Oracle Support.

    Note: Use CNC NF Data Collector tool for capturing logs. For more information on capturing logs, see Oracle Communications Cloud Native Core, Network Function Data Collector User Guide.

Available in OCI Yes
6.3.3.14 OcnrfNFServiceStatusTransitionToUndiscoverable

Table 6-611 OcnrfNFServiceStatusTransitionToUndiscoverable

Field Details
Description

'NF service {{$labels.NfServiceName}} and service instance id {{$labels.NfServiceInstanceId}} of NF profile fqdn {{$labels.NfProfileFqdn}} and instance id {{$labels.NfInstanceId}} is UNDISCOVERABLE, previous status was {{$labels.PreviousStatus}}'

Summary

'kubernetes_namespace: {{$labels.kubernetes_namespace}},nrflevel:{{$labels.NrfLevel}},podname: {{$labels.kubernetes_pod_name}},NfInstanceId: {{$labels.NfInstanceId}},NfServiceName: {{$labels.NfServiceName}},NfServiceInstanceId:{{$labels.NfServiceInstanceId}},NfProfileFqdn: {{$labels.NfProfileFqdn}},NfServiceFqdn: {{$labels.NfServiceFqdn}},PreviousStatus: {{$labels.PreviousStatus}},NewStatus: {{$labels.NewStatus}},timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} NF service is UNDISCOVERABLE.'

Severity Info
Condition Status of an NF Instance's service transitions to UNDISCOVERABLE.

Note: When multiple alerts are present for a given NF, the latest alert is always considered. The timestamp can also be seen in the "Active Since" field of the alert in Prometheus.

OID 1.3.6.1.4.1.323.5.3.36.1.2.7051
Metric Used ocnrf_nfService_status_change_total
Recommended Actions The alert is cleared automatically after a window of 5 minutes.

Steps:

  1. Check logs in NRF registration pod to verify if the NF has sent UNDISCOVERABLE status in NFRegister or NfUpdate requests or check Jaeger traces to see traces for incoming requests.
  2. If there is no such incoming request, collect the logs and contact My Oracle Support.

    Note: Use CNC NF Data Collector tool for capturing logs. For more information on capturing logs, see Oracle Communications Cloud Native Core, Network Function Data Collector User Guide.

Available in OCI Yes
6.3.3.15 OcnrfNFStatusTransitionToDeregistered

Table 6-612 OcnrfNFStatusTransitionToDeregistered

Field Details
Description 'NF with NF profile fqdn {{$labels.NfProfileFqdn}} NF instance id {{$labels.NfInstanceId}} NF type {{$labels.NfType}} is DEREGISTERED, previous status was {{$labels.PreviousStatus}}'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}},nrflevel:{{$labels.NrfLevel}},podname: {{$labels.kubernetes_pod_name}},NfInstanceId: {{$labels.NfInstanceId}},NfProfileFqdn: {{$labels.NfProfileFqdn}},NfType: {{$labels.NfType}},PreviousStatus: {{$labels.PreviousStatus}},NewStatus: {{$labels.NewStatus}},timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} NF is DEREGISTERED.'
Severity Info
Condition NF Instance's status transitions to DEREGISTERED.

Note: When multiple alerts are present for a given NF, the latest alert is always considered. The timestamp can also be seen in the "Active Since" field of the alert in Prometheus.

OID 1.3.6.1.4.1.323.5.3.36.1.2.7052
Metric Used ocnrf_nfInstance_status_change_total
Recommended Actions The alert is cleared automatically after a window of 5 minutes.
Steps:
  1. Check logs in NRF registration pod for failing patch requests or check Jaeger traces to see traces for incoming requests.
  2. Check Ingress Gateway logs to see if the requests are coming.
  3. Check if the NRF pods are UP.
  4. Check for the Ingress Gateway metrics in Prometheus for PATCH requests or responses in this time frame. Confirm if the responses have any non 2xx error codes.
  5. Depending on the failure reason, take the resolution steps.
  6. In case the issue persists, capture all the outputs for the above steps and contact My Oracle Support.

    Note: Use CNC NF Data Collector tool for capturing logs. For more information on capturing logs, see Oracle Communications Cloud Native Core, Network Function Data Collector User Guide.

Available in OCI Yes
6.3.3.16 OcnrfNFServiceStatusTransitionToDeregistered

Table 6-613 OcnrfNFServiceStatusTransitionToDeregistered

Field Details
Description 'NF service {{$labels.NfServiceName}} and service instance id {{$labels.NfServiceInstanceId}} of NF profile fqdn {{$labels.NfProfileFqdn}} and instance id {{$labels.NfInstanceId}} is DEREGISTERED, previous status was {{$labels.PreviousStatus}}'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}},nrflevel:{{$labels.NrfLevel}},podname: {{$labels.kubernetes_pod_name}},NfInstanceId: {{$labels.NfInstanceId}},NfServiceName: {{$labels.NfServiceName}},NfServiceInstanceId:{{$labels.NfServiceInstanceId}},NfProfileFqdn: {{$labels.NfProfileFqdn}},NfServiceFqdn: {{$labels.NfServiceFqdn}},PreviousStatus: {{$labels.PreviousStatus}},NewStatus: {{$labels.NewStatus}},timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} NF service is DEREGISTERED.'
Severity Info
Condition Status of an NF Instance's service transitions to DEREGISTERED.

Note: When multiple alerts are present for a given NF, the latest alert is always considered. The timestamp can also be seen in the "Active Since" field of the alert in Prometheus.

OID 1.3.6.1.4.1.323.5.3.36.1.2.7053
Metric Used ocnrf_nfService_status_change_total
Recommended Actions The alert is cleared automatically after a window of 5 minutes.
Steps:
  1. Check logs in NRF registration pod for failing patch requests or check Jaeger traces to see traces for incoming requests.
  2. Check Ingress Gateway logs to see if the requests are coming.
  3. Check if the NRF pods are UP.
  4. Check for the Ingress Gateway metrics in Prometheus for PATCH requests or responses in this time frame. Confirm if the responses have any non 2xx error codes.
  5. Depending on the failure reason, take the resolution steps.
  6. In case the issue persists, capture all the outputs for the above steps and contact My Oracle Support.

    Note: Use CNC NF Data Collector tool for capturing logs. For more information on capturing logs, see Oracle Communications Cloud Native Core, Network Function Data Collector User Guide.

Available in OCI Yes
6.3.3.17 OcnrfNfProfileSizeAboveThreshold

Table 6-614 OcnrfNfProfileSizeAboveThreshold

Field Details
Description 'The size of the NF profile is above the critical threshold. (current value is: {{ $value }})'
Summary ''namespace: {{$labels.kubernetes_namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }}: The size of the NF profile is above 12kB threshold'
Severity Critical
Condition This alert is raised when the size of the NF profile is greater than the configured threshold.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7119
Metric Used ocnrf_nf_profile_size
Recommended Actions The alert is cleared when the size of the NF profile is less than the critical threshold.

Note: The threshold is configurable in the alert file.

Step:Verify which NF has registered a nfProfile above the threshold size, using the nfInstanceId in the ocnrf_nf_profile_size metric.

Available in OCI No
6.3.3.18 OcnrfDiscoveryResponseSizeAboveThreshold

Table 6-615 OcnrfDiscoveryResponseSizeAboveThreshold

Field Details
Description 'The size of nfDiscover response is above the critical threshold. (current value is: {{ $value }})'
Summary 'namespace: {{$labels.kubernetes_namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }}: The size of nfDiscover response is above 45kB threshold''
Severity Critical
Condition This alert is raised when the size of the nfDiscover response is greater than the configured threshold.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7120
Metric Used ocnrf_nfDiscover_tx_response_size_bytes_max
Recommended Actions The alert is cleared when the size of the nfDiscover response is less than the critical threshold.

Note: The threshold is configurable in the alert file.

Step:

  1. Refer Grafana to check for which targetNfType triggers discovery response with size greater than the threshold. Higher discovery response may impact NRF discovery performance. If the alert is unexpected, contact My Oracle Support.
Available in OCI No

6.3.4 Feature Specific Alerts

This section lists the feature specific alerts.

6.3.4.1 KeyID for AccessToken Feature

This section lists the alerts that are specific to KeyID for AccessToken feature. For more information about the feature, see the Key-ID for Access Token section.

6.3.4.1.1 OcnrfAccessTokenCurrentKeyIdNotConfigured

Table 6-616 OcnrfAccessTokenCurrentKeyIdNotConfigured

Field Details
Description 'AccessToken request(s) have been rejected by OCNRF (current value is: {{ $value }})'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}},nrflevel:{{$labels.NrfLevel}}, podname: {{$labels.kubernetes_pod_name}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} AccessToken Request has been rejected by OCNRF as Current Key Id is not configured.'
Severity Critical
Condition NRF Access Token Rejected due to CurrentKeyId not configured
OID 1.3.6.1.4.1.323.5.3.36.1.2.7033
Metric Used 'ocnrf_accessToken_tx_responses_total'
Recommended Actions The alert is automatically cleared as it is raised when NRF receives Access Token Request, and at that point, Current Key Id is not selected. For more information about configuring currentKeyID parameter, see Oracle Communications Cloud Native Core, Network Repository Function REST Specification Guide.
Available in OCI No
6.3.4.1.2 OcnrfAccessTokenCurrentKeyIdInvalidDetails

Table 6-617 OcnrfAccessTokenCurrentKeyIdInvalidDetails

Field Details
Description 'AccessToken request(s) have been rejected by OCNRF (current value is: {{ $value }})'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}},nrflevel:{{$labels.NrfLevel}}, podname: {{$labels.kubernetes_pod_name}}, KeyType: {{$labels.KeyType}}, RejectionReason: {{$labels.RejectionReason}},timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} AccessToken Request has been rejected by OCNRF as CurrentKeyId details are invalid.'
Severity Critical
Condition NRF Access Token Rejected due to token signing details corresponding to CurrentKeyId are invalid.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7034
Metric Used 'ocnrf_accessToken_tx_responses_total'
Recommended Actions The alert is automatically cleared when NRF receives Access Token Request, and at that point, Current Key Id details are invalid. For more information about configuring currentKeyID parameter, see Oracle Communications Cloud Native Core, Network Repository Function REST Specification Guide.
Available in OCI No
6.3.4.1.3 OcnrfOauthCurrentKeyNotConfigured

Table 6-618 OcnrfOauthCurrentKeyNotConfigured

Field Details
Description 'OCNRF Oauth Access token Current Key Id is not configured'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}},nrflevel:{{$labels.NrfLevel}}, podname: {{$labels.kubernetes_pod_name}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} OCNRF Oauth Access token Current Key Id is not configured.'
Severity Critical
Condition Oauth Current Key ID is not configured
OID 1.3.6.1.4.1.323.5.3.36.1.2.7035
Metric Used ocnrf_oauth_currentKeyId_configuredStatus
Recommended Actions The alert is cleared when the current key ID is configured.

Steps:

Configure valid current key ID in Access Token Configuration. For more information about configuring currentKeyID parameter, see Oracle Communications Cloud Native Core, Network Repository Function REST Specification Guide.

Available in OCI No
6.3.4.1.4 OcnrfOauthCurrentKeyDataHealthStatus

Table 6-619 OcnrfOauthCurrentKeyDataHealthStatus

Field Details
Description 'OCNRF Oauth Access token Current Key Id status is not healthy'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}},nrflevel:{{$labels.NrfLevel}}, podname: {{$labels.kubernetes_pod_name}}, KeyId: {{$labels.KeyId}}, KeyType: {{$labels.KeyType}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} OCNRF Oauth Access token Current Key Id status is not healthy.'
Severity Critical
Condition Oauth Current Key ID details health is not good.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7036
Metric Used ocnrf_oauth_keyData_healthStatus
Recommended Actions

The alert is cleared when the current key ID status is healthy.

Steps: Rectify the condition by checking ErrorCondition

For example: For ErrorCondition Invalid_Key_Details, check if the k8SecretName, k8SecretNameSpace, and filename combination exists correctly for both privateKey and certificate. Make sure that the pem file data is not corrupt or the certificate has not expired.

Available in OCI No
6.3.4.1.5 OcnrfOauthNonCurrentKeyDataHealthStatus

Table 6-620 OcnrfOauthNonCurrentKeyDataHealthStatus

Field Details
Description 'OCNRF Oauth Access token Non current Key Id status is not healthy'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}},nrflevel:{{$labels.NrfLevel}}, podname: {{$labels.kubernetes_pod_name}}, KeyId: {{$labels.KeyId}}, KeyType: {{$labels.KeyType}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} OCNRF Oauth Access token non current Key Id status is not healthy.'
Severity Info
Condition Oauth Non Current Key details health is not good
OID 1.3.6.1.4.1.323.5.3.36.1.2.7037
Metric Used ocnrf_oauth_keyData_healthStatus
Recommended Actions

The alert is cleared when the current key ID status is healthy.

Steps: Rectify the condition by checking ErrorCondition

For example: For ErrorCondition Invalid_Key_Details, check if the k8SecretName, k8SecretNameSpace, and filename combination exists correctly for both privateKey and certificate. Make sure that the pem file data is not corrupt or the certificate has not expired.

Available in OCI No
6.3.4.1.6 OcnrfOauthCurrentCertificateExpiringIn1Week

Table 6-621 OcnrfOauthCurrentCertificateExpiringIn1Week

Field Details
Description 'OCNRF Oauth Access token current Key Id certificate is expiring in less than 1 week'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}},nrflevel:{{$labels.NrfLevel}}, podname: {{$labels.kubernetes_pod_name}}, KeyId: {{$labels.KeyId}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} OCNRF Oauth Access token current Key Id certificate is expiring in less than 1 week.'
Severity Critical
Condition Oauth Current Key ID details are expiring in less than 1 week
OID 1.3.6.1.4.1.323.5.3.36.1.2.7038
Metric Used ocnrf_oauth_keyData_expiryStatus
Recommended Actions

The alert is cleared when the key expiry time is more than 1 week.

Steps:

Replace expiring certificate key pair with new ones. For more information on creating certificate key pair, see Oracle Communications Cloud Native Core, Network Repository Function Installation, Upgrade, and Fault Recovery Guide.
Available in OCI No
6.3.4.1.7 OcnrfOauthNonCurrentCertificateExpiringIn1Week

Table 6-622 OcnrfOauthNonCurrentCertificateExpiringIn1Week

Field Details
Description 'OCNRF Oauth Access token non current Key Id certificate is expiring in less than 1 week'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}},nrflevel:{{$labels.NrfLevel}}, podname: {{$labels.kubernetes_pod_name}}, KeyId: {{$labels.KeyId}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} OCNRF Oauth Access token non current Key Id certificate is expiring in less than 1 week.'
Severity Info
Condition Oauth Non Current Key ID details are expiring in less than 1 week
OID 1.3.6.1.4.1.323.5.3.36.1.2.7039
Metric Used ocnrf_oauth_keyData_expiryStatus
Recommended Actions

The alert is cleared when the key expiry time is more than 1 week.

Steps:

Replace expiring certificate key pair with new ones. For more information on creating certificate key pair, see Oracle Communications Cloud Native Core, Network Repository Function Installation, Upgrade, and Fault Recovery Guide.
Available in OCI No
6.3.4.1.8 OcnrfOauthCurrentCertificateExpiringIn30days

Table 6-623 OcnrfOauthCurrentCertificateExpiringIn30days

Field Details
Description 'OCNRF Oauth Access token current Key Id certificate is expiring in less than 30 days'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}},nrflevel:{{$labels.NrfLevel}}, podname: {{$labels.kubernetes_pod_name}}, KeyId: {{$labels.KeyId}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} OCNRF Oauth Access token current Key Id certificate is expiring in less than 30 days.'
Severity Major
Condition Oauth Current Key ID details are expiring in more than 24 hours and less than 30 days
OID 1.3.6.1.4.1.323.5.3.36.1.2.7040
Metric Used ocnrf_oauth_keyData_expiryStatus
Recommended Actions

The alert is cleared when certificate for the current key id's expiry time is more than 30 days.

Steps:

Replace expiring certificate key pair with new ones. For more information on creating certificate key pair, see Oracle Communications Cloud Native Core, Network Repository Function Installation, Upgrade, and Fault Recovery Guide.
Available in OCI No
6.3.4.1.9 OcnrfOauthNonCurrentCertificateExpiringIn30days

Table 6-624 OcnrfOauthNonCurrentCertificateExpiringIn30days

Field Details
Description 'OCNRF Oauth Access token non current Key Id certificate is expiring in less than 30 days'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}},nrflevel:{{$labels.NrfLevel}}, podname: {{$labels.kubernetes_pod_name}}, KeyId: {{$labels.KeyId}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} OCNRF Oauth Access token non current Key Id certificate is expiring in less than 30 days.'
Severity Info
Condition Oauth Non Current Key ID details are expiring in more than 24 hours and less than 30 days
OID 1.3.6.1.4.1.323.5.3.36.1.2.7041
Metric Used ocnrf_oauth_keyData_expiryStatus
Recommended Actions

The alert is cleared when certificate for the non-current key id's certificate expiry time is more than 30 days.

Steps:

Replace expiring certificate key pair with new ones. For more information on creating certificate key pair, see Oracle Communications Cloud Native Core, Network Repository Function Installation, Upgrade, and Fault Recovery Guide.
Available in OCI No
6.3.4.2 Overload Control Based on Percentage Discards Feature

This section lists the alerts that are specific to Overload Control Based on Percentage Discards feature. For more information about the feature, see the Overload Control section.

6.3.4.2.1 OcnrfMemoryUsageCrossedMinorThreshold

Table 6-625 OcnrfMemoryUsageCrossedMinorThreshold

Field Details
Description 'OCNRF Memory Usage for pod <Pod name> has crossed the configured minor threshold (50 %) (value={{ $value }}) of its limit.'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, podname: {{$labels.kubernetes_pod_name}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : Memory Usage of pod exceeded 50% of its limit.'
Severity Minor
Condition A pod has reached the configured minor threshold (50%) of its memory resource limits.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7030
Metric Used 'container_memory_usage_bytes' and 'container_spec_memory_limit_bytes'

Note: This is a Kubernetes metric used for instance availability monitoring. If the metric is not available, use the similar metric as exposed by the monitoring system.

Recommended Actions The alert gets cleared when the memory utilization falls below the minor threshold or crosses the major threshold, in which case OcnrfMemoryUsageCrossedMajorThreshold alert is raised.

Note: The threshold is configurable in the alerts file.

In case the issue persists, capture all the outputs for the above steps and contact My Oracle Support.

Note: Use CNC NF Data Collector tool for capturing logs. For more information on how to collect logs using Data Collector tool, see Oracle Communications Cloud Native Core, Network Function Data Collector User Guide.

Available in OCI Yes
6.3.4.2.2 OcnrfMemoryUsageCrossedMajorThreshold

Table 6-626 OcnrfMemoryUsageCrossedMajorThreshold

Field Details
Description 'OCNRF Memory Usage for pod <Pod name> has crossed the major threshold (60%) (value = {{ $value }}) of its limit.'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, podname: {{$labels.kubernetes_pod_name}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : Memory Usage of pod exceeded 60% of its limit.'
Severity Major
Condition A pod has reached the configured major threshold (60%) of its memory resource limits.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7031
Metric Used 'container_memory_usage_bytes' and 'container_spec_memory_limit_bytes'

Note: This is a Kubernetes metric used for instance availability monitoring. If the metric is not available, use the similar metric as exposed by the monitoring system.

Recommended Actions The alert gets cleared when the memory utilization falls below the major threshold or crosses the critical threshold, in which case OcnrfMemoryUsageCrossedCriticalThreshold alert is raised.

Note: The threshold is configurable in the alert file.

In case the issue persists, capture all the outputs for the above steps and contact My Oracle Support.

Note: Use CNC NF Data Collector tool for capturing logs. For more information on how to collect logs using Data Collector tool, see Oracle Communications Cloud Native Core, Network Function Data Collector User Guide.

Available in OCI Yes
6.3.4.2.3 OcnrfMemoryUsageCrossedCriticalThreshold

Table 6-627 OcnrfMemoryUsageCrossedCriticalThreshold

Field Details
Description 'OCNRF Memory Usage for pod <Pod name> has crossed the configured critical threshold (70%) (value = {{ $value }}) of its limit.'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, podname: {{$labels.kubernetes_pod_name}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : Memory Usage of pod exceeded 70% of its limit.'
Severity Critical
Condition A pod has reached the configured critical threshold (70%) of its memory resource limits.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7032
Metric Used 'container_memory_usage_bytes' and 'container_spec_memory_limit_bytes'

Note: This is a Kubernetes metric used for instance availability monitoring. If the metric is not available, use a similar metric as exposed by the monitoring system.

Recommended Actions The alert gets cleared when the memory utilization falls below the critical threshold.

Note: The threshold is configurable in the alert file.

In case the issue persists, capture all the outputs for the above steps and contact My Oracle Support.

Note: Use CNC NF Data Collector tool for capturing logs. For more information on how to collect logs using Data Collector tool, see Oracle Communications Cloud Native Core, Network Function Data Collector User Guide.

Available in OCI Yes
6.3.4.2.4 OcnrfOverloadThresholdBreachedL1

Table 6-628 OcnrfOverloadThresholdBreachedL1

Field Details
Description 'Overload Level of {{$labels.app_kubernetes_io_name}} service is L1'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, podname: {{$labels.kubernetes_pod_name}}: Overload Level of {{$labels.app_kubernetes_io_name}} service is L1'
Severity Warning
Condition NRF Services have breached its configured threshold of Level L1 for any of the aforementioned metrics. Thresholds are configured for CPU, svc_failure_count, svc_pending_count, and memory.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7059
Metric Used load_level
Recommended Actions

The alert is cleared when the Ingress Traffic rate falls below the configured L1 threshold.

Note: The thresholds can be configured using REST API.

Steps:

  1. Reassess the reasons leading to NRF receiving additional traffic.
  2. Refer to alert to determine which service is receiving high traffic. It may be due to a sudden spike in traffic.

    For example: When one mated site goes down, the NFs move to the given site.

  3. Check the service pod logs on Kibana to determine the reason for the errors.
  4. If this is expected traffic, then the thresholds levels may be reevaluated as per the call rate and reconfigured as mentioned in Oracle Communications Cloud Native Core, Network Repository Function REST Specification Guide.
  5. If this is the unexpected traffic, contact My Oracle Support.
Available in OCI Yes
6.3.4.2.5 OcnrfOverloadThresholdBreachedL2

Table 6-629 OcnrfOverloadThresholdBreachedL2

Field Details
Description 'Overload Level of {{$labels.app_kubernetes_io_name}} service is L2'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, podname: {{$labels.kubernetes_pod_name}}: Overload Level of {{$labels.app_kubernetes_io_name}} service is L2'
Severity Warning
Condition NRF Services have breached its configured threshold of Level L2 for any of the aforementioned metrics. Thresholds are configured for CPU, svc_failure_count, svc_pending_count, and memory.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7060
Metric Used load_level
Recommended Actions

The alert is cleared when the Ingress Traffic rate falls below the configured L2 threshold.

Note: The thresholds can be configured using REST API.

Steps:

  1. Reassess the reasons leading to NRF receiving additional traffic.
  2. Refer to alert to determine which service is receiving high traffic. It may be due to a sudden spike in traffic.

    For example: When one mated site goes down, the NFs move to the given site.

  3. Check the service pod logs on Kibana to determine the reason for the errors.
  4. If this is expected traffic, then the thresholds levels may be reevaluated as per the call rate and reconfigured as mentioned in Oracle Communications Cloud Native Core, Network Repository Function REST Specification Guide.
  5. If this is the unexpected traffic, contact My Oracle Support.
Available in OCI Yes
6.3.4.2.6 OcnrfOverloadThresholdBreachedL3

Table 6-630 OcnrfOverloadThresholdBreachedL3

Field Details
Description 'Overload Level of {{$labels.app_kubernetes_io_name}} service is L3'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, podname: {{$labels.kubernetes_pod_name}}: Overload Level of {{$labels.app_kubernetes_io_name}} service is L3'
Severity Warning
Condition NRF Services have breached its configured threshold of Level L3 for any of the aforementioned metrics. Thresholds are configured for CPU, svc_failure_count, svc_pending_count, and memory.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7061
Metric Used load_level
Recommended Actions

The alert is cleared when the Ingress Traffic rate falls below the configured L3 threshold.

Note: The thresholds can be configured using REST API.

Steps:

  1. Reassess the reasons leading to NRF receiving additional traffic.
  2. Refer to alert to determine which service is receiving high traffic. It may be due to a sudden spike in traffic.

    For example: When one mated site goes down, the NFs move to the given site.

  3. Check the service pod logs on Kibana to determine the reason for the errors.
  4. If this is expected traffic, then the thresholds levels may be reevaluated as per the call rate and reconfigured as mentioned in Oracle Communications Cloud Native Core, Network Repository Function REST Specification Guide.
  5. If this is the unexpected traffic, contact My Oracle Support.
Available in OCI Yes
6.3.4.2.7 OcnrfOverloadThresholdBreachedL4

Table 6-631 OcnrfOverloadThresholdBreachedL4

Field Details
Description 'Overload Level of {{$labels.app_kubernetes_io_name}} service is L4'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, podname: {{$labels.kubernetes_pod_name}}: Overload Level of {{$labels.app_kubernetes_io_name}} service is L4'
Severity Warning
Condition NRF Services have breached its configured threshold of Level L4 for any of the aforementioned metrics. Thresholds are configured for CPU, svc_failure_count, svc_pending_count, and memory.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7062
Metric Used load_level
Recommended Actions

The alert is cleared when the Ingress Traffic rate falls below the configured L4 threshold.

Note: The thresholds can be configured using REST API.

Steps:

  1. Reassess the reasons leading to NRF receiving additional traffic.
  2. Refer to alert to determine which service is receiving high traffic. It may be due to a sudden spike in traffic.

    For example: When one mated site goes down, the NFs move to the given site.

  3. Check the service pod logs on Kibana to determine the reason for the errors.
  4. If this is expected traffic, then the thresholds levels may be reevaluated as per the call rate and reconfigured as mentioned in Oracle Communications Cloud Native Core, Network Repository Function REST Specification Guide.
  5. If this is the unexpected traffic, contact My Oracle Support.
Available in OCI Yes
6.3.4.3 DNS NAPTR Update Feature

This section lists the alerts that are specific to DNS NAPTR Update feature. For more information about the feature, see the DNS NAPTR Update section.

6.3.4.3.1 OcnrfDnsNaptrFailureResponseStatus

Table 6-632 OcnrfDnsNaptrFailureResponseStatus

Field Details
Description OCNRF DNS NAPTR Response status is not healthy
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}},nrflevel:{{$labels.NrfLevel}}, podname: {{$labels.kubernetes_pod_name}}, NfInstanceId: {{$labels.NfInstanceId}}, NfSetFqdn: {{$labels.NfSetFqdn}}, Replacement: {{$labels.Replacement}},timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} OCNRF Dns Naptr Response status is not healthy.'
Severity Major
Condition The DNS NAPTR response towards DNS Server is not successful.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7063
Metric Used ocnrf_dns_naptr_failure_rx_response
Recommended Actions This alert is cleared when DNS NAPTR response is successful either automatic through service operations, or manual trigger for update and delete NAPTR requests.
6.3.4.3.2 OcnrfAlternateRouteUpstreamDnsRetryExhausted

Table 6-633 OcnrfAlternateRouteUpstreamDnsRetryExhausted

Field Details
Description OCNRF alternate route upstream DNS retry exhausted
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, podname: {{$labels.kubernetes_pod_name}}, FQDNS_Name: {{$labels.FQDNS_Name}}, Replacement_Name: {{$labels.Replacement_Name}},timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} OCNRF alternate route upstream dns retry exhausted'
Severity Major
Condition The DNS NAPTR retry is exhausted.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7064
Metric Used oc_alternate_route_upstream_dns_retry_exhausted
Recommended Actions This alert is cleared automatically in 2 minutes.
Available in OCI No
6.3.4.4 Notification Retry Feature

This section lists the alerts that are specific to Notification Retry feature. For more information about the feature, see the Notification Retry section.

6.3.4.4.1 OcnrfNotificationRetryExhausted

Table 6-634 OcnrfNotificationRetryExhausted

Field Details
Description 'OCNRF NotificationRetry Exhausted'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, podname: {{$labels.kubernetes_pod_name}}, SubscriptionId: {{$labels.SubscriptionId}}, NotificationHostPort: {{$labels.NotificationHostPort}}'
Severity Major
Condition This alarm is raised when number of retries are exhausted.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7065
Metric Used ocnrf_nfStatusNotify_rx_responses_total
Recommended Actions The alert is cleared automatically after 5 minutes.

Steps: Check logs in NF management pod to check the reason for retry query failures.

Note: Use CNC NF Data Collector tool for capturing logs. For more information on how to collect logs using Data Collector tool, see Oracle Communications Cloud Native Core, Network Function Data Collector User Guide.
Available in OCI Yes
6.3.4.4.2 OcnrfNotificationFailureOtherThanRetryExhausted

Table 6-635 OcnrfNotificationFailureOtherThanRetryExhausted

Field Details
Description 'OCNRF notification failure other than retry exhausted'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, podname: {{$labels.kubernetes_pod_name}}, SubscriptionId: {{$labels.SubscriptionId}}, NotificationHostPort: {{$labels.NotificationHostPort}}, NumberOfRetriesAttempted: {{$labels.NumberOfRetriesAttempted}}'
Severity Major
Condition This alarm is raised when notification failure occurs with reason other than retry count exhausted.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7066
Metric Used ocnrf_nfStatusNotify_rx_responses_total
Recommended Actions The alert is cleared automatically after 5 minutes.

Steps: Check logs in NF management pod to check the reason for retry query failures.

Note: Use CNC NF Data Collector tool for capturing logs. For more information on how to collect logs using Data Collector tool, see Oracle Communications Cloud Native Core, Network Function Data Collector User Guide.
Available in OCI Yes
6.3.4.5 NRF Message Feed Feature

This section lists the alerts that are specific to NRF Message Feed feature. For more information about the feature, see the NRF Message Feed section.

6.3.4.5.1 OcnrfIngressGatewayDDUnreachable

Table 6-636 OcnrfIngressGatewayDDUnreachable

Field Details
Description OCNRF Ingress Gateway Data Director unreachable
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} OCNRF Ingress Gateway Data Director unreachable'
Severity Major
Condition This alarm is raised when data director is not reachable from Ingress Gateway.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7067
Metric Used oc_ingressgateway_dd_unreachable
Recommended Actions Alert gets cleared automatically when the connection with data director is established.
Available in OCI No
6.3.4.5.2 OcnrfEgressGatewayDDUnreachable

Table 6-637 OcnrfEgressGatewayDDUnreachable

Field Details
Description OCNRF Egress Gateway Data Director unreachable
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} OCNRF Egress Gateway Data Director unreachable'
Severity Major
Condition This alarm is raised when data director is not reachable from Egress Gateway.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7068
Metric Used oc_egressgateway_dd_unreachable
Recommended Actions Alert gets cleared automatically when the connection with data director is established.
Available in OCI No
6.3.4.6 Subscription Limit Feature

This section lists the alerts that are specific to Subscription Limit feature. For more information about the feature, see the Subscription Limit section.

6.3.4.6.1 OcnrfSubscriptionGlobalCountWarnThresholdBreached

Table 6-638 OcnrfSubscriptionGlobalCountWarnThresholdBreached

Field Details
Description The total number of subscriptions has breached the configured WARN level threshold.
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, nrflevel:{{$labels.NrfLevel}}, podname: {{$labels.kubernetes_pod_name}}: The total number of subscriptions has breached the configured WARN level threshold'
Severity Warning
Condition This alarm is raised when the total number of subscriptions has breached the configured WARN level threshold.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7069
Metric Used ocnrf_nfset_limit_level
Recommended Actions

The alert is cleared automatically when the count comes down due to unsubscription.

Note: The thresholds can be configured using REST API.

Steps:

  1. Reassess the reasons for new or renewal of subscription.
  2. If this is expected subscription, then the subscription limit may be reevaluated as mentioned in Oracle Communications Cloud Native Core, Network Repository Function REST Specification Guide.
  3. If this is the unexpected subscription, contact My Oracle Support.
Available in OCI Yes
6.3.4.6.2 OcnrfSubscriptionGlobalCountMinorThresholdBreached

Table 6-639 OcnrfSubscriptionGlobalCountMinorThresholdBreached

Field Details
Description The total number of subscriptions has breached the configured MINOR level threshold
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, nrflevel:{{$labels.NrfLevel}}, podname: {{$labels.kubernetes_pod_name}}: The total number of subscriptions has breached the configured MINOR level threshold'
Severity Minor
Condition This alarm is raised when the total number of subscriptions has breached the configured MINOR level threshold.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7070
Metric Used ocnrf_nfset_limit_level
Recommended Actions

The alert is cleared automatically when the count comes down due to unsubscription.

Note: The thresholds can be configured using REST API.

Steps:

  1. Reassess the reasons for new or renewal of subscription.
  2. If this is expected subscription, then the subscription limit may be reevaluated as mentioned in Oracle Communications Cloud Native Core, Network Repository Function REST Specification Guide.
  3. If this is the unexpected subscription, contact My Oracle Support.
Available in OCI Yes
6.3.4.6.3 OcnrfSubscriptionGlobalCountMajorThresholdBreached

Table 6-640 OcnrfSubscriptionGlobalCountMajorThresholdBreached

Field Details
Description The total number of subscriptions has breached the configured MAJOR level threshold
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, nrflevel:{{$labels.NrfLevel}}, podname: {{$labels.kubernetes_pod_name}}: The total number of subscriptions has breached the configured MAJOR level threshold'
Severity MAJOR
Condition This alarm is raised when the total number of subscriptions has breached the configured MAJOR level threshold.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7071
Metric Used ocnrf_nfset_limit_level
Recommended Actions

The alert is cleared automatically when the count comes down due to unsubscription.

Note: The thresholds can be configured using REST API.

Steps:

  1. Reassess the reasons for new or renewal of subscription.
  2. If this is expected subscription, then the subscription limit may be reevaluated as mentioned in Oracle Communications Cloud Native Core, Network Repository Function REST Specification Guide.
  3. If this is the unexpected subscription, contact My Oracle Support.
Available in OCI Yes
6.3.4.6.4 OcnrfSubscriptionGlobalCountCriticalThresholdBreached

Table 6-641 OcnrfSubscriptionGlobalCountCriticalThresholdBreached

Field Details
Description The total number of subscriptions has breached the configured CRITICAL level threshold
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, nrflevel:{{$labels.NrfLevel}}, podname: {{$labels.kubernetes_pod_name}}: The total number of subscriptions has breached the configured CRITICAL level threshold'
Severity Critical
Condition This alarm is raised when the total number of subscriptions has breached the configured CRITICAL level threshold.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7072
Metric Used ocnrf_nfset_limit_level
Recommended Actions

The alert is cleared automatically when the count comes down due to unsubscription.

Note: The thresholds can be configured using REST API.

Steps:

  1. Reassess the reasons for new or renewal of subscription.
  2. If this is expected subscription, then the subscription limit may be reevaluated as mentioned in Oracle Communications Cloud Native Core, Network Repository Function REST Specification Guide.
  3. If this is the unexpected subscription, contact My Oracle Support.
Available in OCI Yes
6.3.4.6.5 OcnrfSubscriptionMigrationInProgressWarn

Table 6-642 OcnrfSubscriptionMigrationInProgressWarn

Field Details
Description The subscription migration is pending and subscriptionLimit feature is disabled
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, nrflevel:{{$labels.NrfLevel}}, subscriptionLimitFeatureStatus:{{$labels.subscriptionLimitFeatureStatus}}: The subscription migration is pending and subscriptionLimit feature is disabled'
Severity Warning
Condition The subscription migration is pending and subscriptionLimit feature is disabled.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7073
Metric Used ocnrf_subscription_migration_status
Recommended Actions This alert is cleared automatically when the migration is complete.
Available in OCI No
6.3.4.6.6 OcnrfSubscriptionMigrationInProgressCritical

Table 6-643 OcnrfSubscriptionMigrationInProgressCritical

Field Details
Description The subscription migration is pending and subscriptionLimit feature is enabled
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, nrflevel:{{$labels.NrfLevel}}, subscriptionLimitFeatureStatus:{{$labels.subscriptionLimitFeatureStatus}}: The subscription migration is pending and subscriptionLimit feature is enabled'
Severity Warning
Condition The subscription migration is pending and subscriptionLimit feature is enabled.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7074
Metric Used ocnrf_subscription_migration_status
Recommended Actions

This alert is cleared automatically when the migration is complete.

Steps: Disable the Subscription Limit feature. For more information, see Oracle Communications Cloud Native Core, Network Repository Function REST Specification Guide.

Available in OCI No
6.3.4.7 Pod Protection Support for NRF Subscription Microservice

This section lists the alerts that are specific to Pod Protection Support for NRF Subscription Microservice feature. For more information about the feature, see the Pod Protection Support for NRF Subscription Microservice section.

6.3.4.7.1 OcnrfPodInDangerOfCongestionState

Table 6-644 OcnrfPodInDangerOfCongestionState

Field Details
Description 'The pod {{$labels.kubernetes_pod_name}} of service {{$labels.app_kubernetes_io_name}} is in Danger of Congestion state'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, nrflevel:{{$labels.NrfLevel}}, podname: {{$labels.kubernetes_pod_name}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : The pod is in Danger of Congestion state'
Severity Major
Condition A pod of a service is in Danger Of Congestion state. This could be due to CPU Usage or Pending Message Count above configured thresholds.

This alert is raised when the Pod Protection feature is enabled for nfSubscription service. Currently this is applicable for NfSubscription service only.

OID 1.3.6.1.4.1.323.5.3.36.1.2.7079
Metric Used ocnrf_pod_congestion_state
Recommended Actions The alert is cleared when the CPU or Pending Message Count goes below the configured thresholds for the Danger of Congested state.

Note: The thresholds can be viewed using REST API.

Reassess if the NRF is receiving additional traffic.

If this is unexpected, contact My Oracle Support.

Steps:
  1. Refer to alert to determine which pod is receiving high traffic. It may due to a sudden spike in traffic. For example: When one mated site goes down, the NFs move to the given site. Check if NF is sending high number of updates, register or deregister.
  2. Check for the corresponding congestion alert for CPU and Pending Message Count to understand the reason for pod congestion.
  3. Check the service pod logs on Kibana to determine the reason for the errors.
  4. If this is expected traffic, then the thresholds levels may need to be re-evaluated as per the call rate and reconfigured as mentioned in Oracle Communications Cloud Native Core, Network Repository Function REST Specification Guide.
Available in OCI No
6.3.4.7.2 OcnrfPodPendingMessageCountInDangerOfCongestionState

Table 6-645 OcnrfPodPendingMessageCountInDangerOfCongestionState

Field Details
Description 'The pod {{$labels.kubernetes_pod_name}} of service {{$labels.app_kubernetes_io_name}} is in Danger of Congestion state due to Pending Message Count above threshold'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, nrflevel:{{$labels.NrfLevel}}, podname: {{$labels.kubernetes_pod_name}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : The pod is in Danger of Congestion state due to Pending Message Count above threshold'
Severity Major
Condition

A pod of a service is in Danger Of Congestion state due to its Pending Message Count above configured thresholds.

Currently this is applicable for NfSubscription service only.

OID 1.3.6.1.4.1.323.5.3.36.1.2.7081
Metric Used ocnrf_pod_pending_message_count_congestion_state
Recommended Actions The alert is cleared when the pending message count goes below the configured thresholds for the Danger of Congested state.

Note: The thresholds can be viewed using REST API.

Steps:

Reassess if the NRF is receiving additional traffic.

If this is unexpected, contact My Oracle Support.

  1. Refer to alert to determine which pod is receiving high traffic. It may due to a sudden spike in traffic. For example: When one mated site goes down, the NFs move to the given site. Check if NF is sending high number of updates, register, or deregister.
  2. Check the service pod logs on Kibana to determine the reason for the errors.
  3. If this is expected traffic, then the thresholds levels may need to be re-evaluated as per the call rate and reconfigured as mentioned in Oracle Communications Cloud Native Core, Network Repository Function REST Specification Guide.
6.3.4.7.3 OcnrfPodInCongestedState

Table 6-646 OcnrfPodInCongestedState

Field Details
Description 'The pod {{$labels.kubernetes_pod_name}} of service {{$labels.app_kubernetes_io_name}} is in Congested state'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, nrflevel:{{$labels.NrfLevel}}, podname: {{$labels.kubernetes_pod_name}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : The pod is in Congested state'
Severity Major
Condition One or more pods of a service are in congested state. This could be due to CPU usage or Pending Message Count above configured thresholds. Currently this is applicable for NfSubscription service only.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7082
Metric Used ocnrf_pod_congested_state
Recommended Actions The alert is cleared when the CPU usage or Pending Message Count goes below the configured thresholds for the congested state.

Note: The thresholds can be viewed using REST API.

Steps:

Reassess if the NRF is receiving additional traffic.

If this is unexpected, contact My Oracle Support.

  1. Refer to alert to determine which pod is receiving high traffic. It may due to a sudden spike in traffic. For example: When one mated site goes down, the NFs move to the given site. Check if NF is sending high number of updates, register, or deregister.
  2. Check the service pod logs on Kibana to determine the reason for the errors.
  3. If this is expected traffic, then the thresholds levels may need to be re-evaluated as per the call rate and reconfigured as mentioned in Oracle Communications Cloud Native Core, Network Repository Function REST Specification Guide.
Available in OCI No
6.3.4.7.4 OcnrfPodCpuUsageInCongestedState

Table 6-647 OcnrfPodCpuUsageInCongestedState

Field Details
Description 'The pod {{$labels.kubernetes_pod_name}} of service {{$labels.app_kubernetes_io_name}} is in Congested state due to CPU usage above threshold'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, nrflevel:{{$labels.NrfLevel}}, podname: {{$labels.kubernetes_pod_name}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : The pod is in Congested state due to CPU usage above threshold'
Severity Major
Condition A pod of a service is in Congested state due to its CPU Usage above configured thresholds. Currently this is applicable for NfSubscription service only.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7083
Metric Used ocnrf_pod_cpu_congestion_state
Recommended Actions The alert is cleared when the CPU usage goes below the configured thresholds for the congested state.

Note: The thresholds can be viewed using REST API.

Steps:

Reassess if the NRF is receiving additional traffic.

If this is unexpected, contact My Oracle Support.

  1. Refer to alert to determine which pod is receiving high traffic. It may due to a sudden spike in traffic. For example: When one mated site goes down, the NFs move to the given site. Check if NF is sending high number of updates, register or deregister.
  2. Check the service pod logs on Kibana to determine the reason for the errors.
  3. If this is expected traffic, then the thresholds levels may need to be re-evaluated as per the call rate and reconfigured as mentioned in Oracle Communications Cloud Native Core, Network Repository Function REST Specification Guide.
Available in OCI No
6.3.4.7.5 OcnrfPodCpuUsageInDangerOfCongestionState

Table 6-648 OcnrfPodCpuUsageInDangerOfCongestionState

Field Details
Description 'The pod {{$labels.kubernetes_pod_name}} of service {{$labels.app_kubernetes_io_name}} is in Danger of Congestion state due to CPU usage above threshold'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, nrflevel:{{$labels.NrfLevel}}, podname: {{$labels.kubernetes_pod_name}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : The pod is in Danger of Congestion state due to CPU usage above threshold'
Severity Major
Condition

A pod of a service is in Danger Of Congestion state due to its CPU above configured thresholds.

This alert is raised when the Pod Pretoectoin feature is enabled for nfSubscription service. Currently this is applicable for NfSubscription service only.

OID 1.3.6.1.4.1.323.5.3.36.1.2.7080
Metric Used ocnrf_pod_cpu_congestion_state
Recommended Actions The alert is cleared when the CPU goes below the configured thresholds for the Danger of Congested state.

Note: The thresholds can be viewed using REST API.

Steps:

Reassess if the NRF is receiving additional traffic.

If this is unexpected, contact My Oracle Support.

  1. Refer to alert to determine which pod is receiving high traffic. It may due to a sudden spike in traffic. For example: When one mated site goes down, the NFs move to the given site. Check if NF is sending sending high number of updates, register or deregister.
  2. Check the service pod logs on Kibana to determine the reason for the errors.
  3. If this is expected traffic, then the thresholds levels may need to be re-evaluated as per the call rate and reconfigured as mentioned in Oracle Communications Cloud Native Core, Network Repository Function REST Specification Guide.
Available in OCI No
6.3.4.7.6 OcnrfPodPendingMessageCountInCongestedState

Table 6-649 OcnrfPodPendingMessageCountInCongestedState

Field Details
Description 'The pod {{$labels.kubernetes_pod_name}} of service {{$labels.app_kubernetes_io_name}} is in Congested state due to Pending Message Count above threshold'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, nrflevel:{{$labels.NrfLevel}}, podname: {{$labels.kubernetes_pod_name}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : The pod is in Congested state due to Pending Message Count above threshold'
Severity Major
Condition A pod of a service is in Congested state due to its Pending Message Count above configured thresholds. Currently this is applicable for NfSubscription service only.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7084
Metric Used ocnrf_pod_pending_message_count_congestion_state
Recommended Actions The alert is cleared when the pending message count goes below the configured thresholds for the congested state.

Note: The thresholds can be viewed using REST API.

Steps:

Reassess if the NRF is receiving additional traffic.

If this is unexpected, contact My Oracle Support.

  1. Refer to alert to determine which pod is receiving high traffic. It may due to a sudden spike in traffic. For example: When one mated site goes down, the NFs move to the given site. Check if NF is sending high number of updates, register or deregister.
  2. Check the service pod logs on Kibana to determine the reason for the errors.
  3. If this is expected traffic, then the thresholds levels may need to be re-evaluated as per the call rate and reconfigured as mentioned in Oracle Communications Cloud Native Core, Network Repository Function REST Specification Guide.
Available in OCI No
6.3.4.8 Controlled Shutdown of NRF Feature

This section lists the alerts that are specific to Controlled Shutdown of NRF feature. For more information about the feature, see the Controlled Shutdown of NRF section.

6.3.4.8.1 OcnrfOperationalStateCompleteShutdown

Table 6-650 OcnrfOperationalStateCompleteShutdown

Field Details
Description 'The operational state of NRF is Complete Shutdown.'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : The Operational state of NRF is Complete Shutdown'
Severity Warning
Condition The operator has changed the operational state of NRF to Complete Shutdown.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7085
Metric Used ocnrf_operational_state
Recommended Actions The alert is cleared when the user changes the operational state to NORMAL
  • If the alert is not cleared automatically after the operational state changes to NORMAL, collect the following:
    • all the logs as mentioned in the NrfConfiguration, Ingress Gateway, Egress Gateway, NrfAuditor microservices
    • the database dump from the site
    • REST output of operationalState, operationalStateHistory, and controlledShutdownOptions
  • Contact My Oracle Support.
Available in OCI No
6.3.4.8.2 OcnrfAuditOperationsPaused

Table 6-651 OcnrfAuditOperationsPaused

Field Details
Description 'The Audit procedures at NRF have been paused.'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : The Audit procedures at NRF has been paused'
Severity Warning
Condition The NrfAuditor microservice has paused all audit procedures.
This occurs during any of the following scenarios:
  1. The NRF is in COMPLETE_SHUTDOWN operational state or just transitioned from COMPLETE_SHUTDOWN to a NORMAL operational state.
  2. The database has been down for a prolonged period of time. To restore the database, see section "Database Corruption" in Oracle Communications Cloud Native Core, Network Repository Function Installation, Upgrade, and Fault Recovery Guide.
  3. If the NrfAuditor pod has transitioned from READY to NOT_READY state.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7086
Metric Used ocnrf_audit_status
Recommended Actions The alert is expected to clear automatically, after the waiting period, and once all the above conditions are resolved.
  • If the alert is not cleared automatically, collect the following:
    • all the logs as mentioned in the NrfConfiguration microservice, and NrfAuditor pod logs,
    • the database dump from the site,
    • REST output of operationalState, operationalStateHistory, and controlled ShutdownOptions
  • Contact My Oracle Support.
Notes

NrfAuditor continues to remain in the paused state for some time, even after OcnrfOperationalStateCompleteShutdown alarm is cleared. For more information, see From CONTROLLED_SHUTDOWN to NORMAL subsection under "Controlled Shutdown of NRF" section in Oracle Communications Cloud Native Core, Network Repository Function User Guide.

Available in OCI No
6.3.4.9 Monitoring the Availability of SCP Using SCP Health APIs Feature

This section lists the alerts that are specific to Monitoring the Availability of SCP Using SCP Health APIs feature. For more information about the feature, see the Monitoring the Availability of SCP Using SCP Health APIs section.

6.3.4.9.1 OcnrfAllSCPsMarkedAsUnavailable

Table 6-652 OcnrfAllSCPsMarkedAsUnavailable

Field Details
Description 'All SCPs have been marked unavailable.'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : All SCPs have been marked as unavailable'
Severity Critical
Condition All SCPs have been marked unavailable.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7088
Metric Used 'oc_egressgateway_peer_count and oc_egressgateway_peer_available_count'
Recommended Actions NF clears the critical alarm when atleast 1 SCP peer in a peerset becomes available such that all other SCP peers in the given peerset are still unavailable.
Available in OCI Yes
6.3.4.9.2 OcnrfSCPMarkedAsUnavailable

Table 6-653 OcnrfSCPMarkedAsUnavailable

Field Details
Description 'An SCP has been marked unavailable.'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : One of the SCP has been marked unavailable'
Severity Major
Condition One of the SCPs has been marked unhealthy.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7087
Metric Used oc_egressgateway_peer_health_status
Recommended Actions This alert gets cleared when unavailable SCPs become available.
Available in OCI Yes
6.3.4.10 CCA Header Validation in NRF for Access Token Service Operation Feature

This section lists the alerts that are specific to CCA Header Validation in NRF for Access Token Service Operation feature. For more information about the feature, see the CCA Header Validation in NRF for Access Token Service Operation section.

6.3.4.10.1 OcnrfCcaRootCertificateExpiringIn4Hours

Table 6-654 OcnrfCcaRootCertificateExpiringIn4Hours

Field Details
Description 'The CCA Root Certificates expiring in 4 hours'.
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : CCA Root Certificate is expiring in 4 Hours'
Severity Critical
Condition Indicates the expiry dates of the CCA Root certificates that are expiring in four hours.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7091
Metric Used 'oc_ingressgateway_cca_certificate_info'
Recommended Actions The alert is cleared when the expiring CCA root certificates are replaced with new ones.

Steps: Replace expiring certificate key pair with new ones. For more information on creating certificate key pair, see Oracle Communications Cloud Native Core, Network Repository Function Installation, Upgrade, and Fault Recovery Guide.

Available in OCI No
6.3.4.10.2 OcnrfCcaRootCertificateExpiringIn1Day

Table 6-655 OcnrfCcaRootCertificateExpiringIn1Day

Field Details
Description 'The CCA Root Certificates expiring in 1 day'.
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : CCA Root Certificate is expiring in 1 Day'
Severity Major
Condition Indicates the expiry dates of the CCA Root certificates that are expiring in one day.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7090
Metric Used 'oc_ingressgateway_cca_certificate_info'
Recommended Actions The alert is cleared when the expiring CCA root certificates are replaced with new ones.

Steps: Replace expiring certificate key pair with new ones. For more information on creating certificate key pair, see Oracle Communications Cloud Native Core, Network Repository Function Installation, Upgrade, and Fault Recovery Guide.

Available in OCI No
6.3.4.10.3 OcnrfCcaRootCertificateExpiringIn5Days

Table 6-656 OcnrfCcaRootCertificateExpiringIn5Days

Field Details
Description 'The CCA Root Certificates expiring in 5 days.'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : CCA Root Certificate is expiring in 5 Days'
Severity Minor
Condition Indicates the expiry dates of the CCA Root certificates that are expiring in five days.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7089
Metric Used 'oc_ingressgateway_cca_certificate_info'
Recommended Actions The alert is cleared when the expiring CCA root certificates are replaced with new ones.

Steps: Replace expiring certificate key pair with new ones. For more information on creating certificate key pair, see Oracle Communications Cloud Native Core, Network Repository Function Installation, Upgrade, and Fault Recovery Guide.

Available in OCI No
6.3.4.11 NRF Georedundancy Feature

This section lists the alerts that are specific to NRF Georedundancy feature. For more information about the feature, see the NRF Georedundancy section.

6.3.4.11.1 OcnrfDbReplicationStatusInactive

Table 6-657 OcnrfDbReplicationStatusInactive

Field Details
Description 'The Database Replication Status is currently INACTIVE.'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, nftype:{{$labels.NfType}}, nrflevel:{{$labels.NrfLevel}}, remoteNrfInstanceId: {{$labels.nrfInstanceId}}, remoteSiteName: {{$labels.siteName}}, podname: {{$labels.kubernetes_pod_name}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }}: The database replication status is INACTIVE.'
Severity Critical
Condition The database replication channel status between the given site and the georedundant site(s) is inactive. The alert is raised per replication channel. The alarm is raised or cleared only if the georedundancy feature is enabled.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7013
Metric Used 'ocnrf_dbreplication_status'
Recommended Actions The alert is cleared when the database channel replication status between the given site and the georedundant site(s) is up. For more information on how to check the database replication status, see Oracle Communications Cloud Native Core, cnDBTier User Guide.
Notes The alarm is included only if the georedundancy feature is enabled.
Available in OCI No
6.3.4.11.2 OcnrfReplicationStatusMonitoringInactive

Table 6-658 OcnrfReplicationStatusMonitoringInactive

Field Details
Description 'OCNRF Replication Status Monitoring Inactive'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : Pod {{ $labels.kubernetes_pod_name}} are not monitoring the replication status'
Severity Critical
Condition This alarm is raised when one or more pods are not monitoring the replication status.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7078
Metric Used ocnrf_replication_status_monitoring_inactive
Recommended Actions Resolution Steps:
  1. Identify the pod for which the alert is raised.
  2. Run the following command to restart the pod:

    kubectl delete pod <pod_name> -n <namespace>

6.3.4.12 XFCC Header Validation Feature

This section lists the alert that is specific to XFCC Header Validation feature. For more information about the feature, see the XFCC Header Validation section.

6.3.4.12.1 OcnrfNfAuthenticationFailureRequestsRejected

Table 6-659 OcnrfNfAuthenticationFailureRequestsRejected

Field Details
Description 'Service request(s) received from NF have been rejected by OCNRF (current value is: {{ $value }})'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}},nrflevel:{{$labels.NrfLevel}}, podname: {{$labels.kubernetes_pod_name}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : Request rejected for Nf FQDN based Authentication failure.'
Severity Warning
Condition NRF rejected a service request due to NF authentication failure
OID 1.3.6.1.4.1.323.5.3.36.1.2.7015
Metric Used 'ocnrf_nf_authentication_failure_total'
Recommended Actions The alert is cleared automatically.

Steps:

Filter out nfAccessToken application ERROR logs on Kibana for more details.
Available in OCI No
6.3.4.13 Enhanced NRF Set Based Deployment (NRF Growth) Feature

This section lists the alert that is specific to Enhanced NRF Set Based Deployment (NRF Growth) feature. For more information about the feature, see the Enhanced NRF Set Based Deployment (NRF Growth) section.

6.3.4.13.1 OcnrfRemoteSetNrfSyncFailed

Table 6-660 OcnrfRemoteSetNrfSyncFailed

Field Details
Description 'A sync request to the NRF in the remote set has failed.'

Note: The alert must be configured only if the NRF Growth feature is enabled.

Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : A sync request to the NRF in the remote set has failed.'
Severity Minor
Condition Sync request to the NRF in the remote NRF set has failed.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7098
Metric Used ocnrf_query_remote_cds_responses_total
Recommended Actions

The alert is cleared when the synchronization with the remote NRF set is successful.

Steps:

  1. Verify the remote NRF set is up.
  2. Verify the connectivity between the local NRF set and remote NRF set.
  3. Collect logs from local NRF and remote NRF(s). Contact My Oracle Support.
Available in OCI No
6.3.4.13.2 OcnrfSyncFailureFromAllNrfsOfAnyRemoteSet

Table 6-661 OcnrfSyncFailureFromAllNrfsOfAnyRemoteSet

Field Details
Description 'Sync requests to all the NRFs of a remote set has failed.'

Note: The alert must be configured only if the NRF Growth feature is enabled.

Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : Sync requests to all the NRFs in any of the remote sets have failed'
Severity Major
Condition The sync requests to all the NRFs in the remote sets has failed.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7099
Metric Used ocnrf_remote_set_unavailable_total
Recommended Actions The alert is cleared when synchronization is successful with at least one NRF of the remote NRF set.

Steps:

  1. Verify the remote NRF sets are up.
  2. Verify the host details configured in the nrfHostConfig attribute using REST API. For more information about the attribute, see Oracle Communications, Cloud Native Core Network Repository Function REST Specifications Guide.
  3. Verify the connectivity between the local NRF set and remote NRF set.
  4. Collect logs from local NRF and remote NRF(s). Contact My Oracle Support.
Available in OCI No
6.3.4.13.3 OcnrfSyncFailureFromAllNrfsOfAllRemoteSets

Table 6-662 OcnrfSyncFailureFromAllNrfsOfAllRemoteSets

Field Details
Description 'Sync request to all the NRFs in all the remote sets have failed.'

Note: The alert must be configured only if the NRF Growth feature is enabled.

Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : Sync request to all the NRFs in all the remote sets have failed'
Severity critical
Condition Sync requests to all the NRFs in all the remote sets have failed.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7100
Metric Used ocnrf_all_remote_sets_unavailable_total
Recommended Actions

The alert is cleared when synchronization is successful with at least one NRF of the remote set(s).

Steps:

  1. Verify the remote NRF sets are up.
  2. Verify the host details configured in the nrfHostConfig attribute using REST API. For more information about the attribute, see Oracle Communications, Cloud Native Core Network Repository Function REST Specifications Guide.
  3. Verify the connectivity between the local NRF set and remote NRF set.
  4. Collect logs from local NRF and remote NRF(s). Contact My Oracle Support.
Available in OCI No
6.3.4.13.4 OcnrfCacheDataServiceDown

Table 6-663 OcnrfCacheDataServiceDown

Field Details
Description 'OCNRF NrfCacheData service {{$labels.app_kubernetes_io_name}} is down'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : Cache Data Service is down'
Severity Critical
Condition Cache Data Service is unavailable.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7101
Metric Used up
Recommended Actions

The alert is cleared when the Cache Data Service (CDS) is available.

Steps:
  1. To check the orchestration logs of the CDS and check for liveness or readiness probe failures, do the following:
    1. Run the following command to check the pod status:
      $ kubectl get po -n <namespace>
    2. Run the following command to analyze the error condition of the pod that is not in the running state:
      $ kubectl describe pod <pod name not in Running state> -n <namespace>

      Where <pod name not in Running state> indicates the pod that is not in the Running state.

  2. Refer to the application logs on Kibana and filter based on service names. Check for ERROR WARNING logs.
  3. Check the DB status. For more information on how to check the DB status, see Oracle Communications Cloud Native Core, cnDBTier User Guide. Depending on the failure reason, take the resolution steps.
  4. In case the issue persists, capture all the outputs for the above steps and contact My Oracle Support.

Note: Use the CNC NF Data Collector tool for capturing logs. For more information on how to collect logs using the Data Collector tool, see Oracle Communications Cloud Native Core, Network Function Data Collector User Guide.

Available in OCI No
6.3.4.13.5 OcnrfDatabaseFallbackUsed

Table 6-664 OcnrfDatabaseFallbackUsed

Field Details
Description 'A service operation is unable to get data from the Cache Data Service, and hence gets the data from the cnDBTier to fulfill the service operation'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : A service Operation is unable to get data from the Cache Data Service, so falling back to DB'
Severity Major
Condition When a service operation is unable to get data from the Cache Data Service, and hence gets the data from the database to fulfill the service operation.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7102
Metric Used ocnrf_db_fallback_total
Recommended Actions

The alert is cleared automatically.

Steps:

  1. To check the orchestration logs of the CDS and check for liveness or readiness probe failures, do the following:
    1. Run the following command to check the pod status:
      $ kubectl get po -n <namespace>
    2. Run the following command to analyze the error condition of the pod that is not in the running state:
      $ kubectl describe pod <pod name not in Running state> -n <namespace>

      Where <pod name not in Running state> indicates the pod that is not in the Running state.

  2. Refer to the application logs on Kibana and filter based on service names. Check for ERROR WARNING logs.
  3. In case the issue persists, capture all the outputs for the above steps and contact My Oracle Support.
Available in OCI No
6.3.4.13.6 OcnrfTotalNFsRegisteredAtSegmentBelowMinorThreshold

Table 6-665 OcnrfTotalNFsRegisteredAtSegmentBelowMinorThreshold

Field Details
Description The alert is raised when the number of NFs registered at the segment is below the configured minor threshold.
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : The number of NFs registered at the segment is below minor threshold'
Severity Minor
Condition The number of NFs registered at the segment is below minor threshold.

Note: This alert is triggered when the registered NF count is greater than or equal to 10 and below 20. This default value can be modified in the ocnrf_alertrules_25.1.200.yaml or ocnrf_alertrules_promha_25.1.200.yaml file depending on Prometheus version.

OID 1.3.6.1.4.1.323.5.3.36.1.2.7103
Metric Used ocnrf_nf_registered_count
Recommended Actions

The alert is cleared when the number of registered NFs in the segment is above the minor threshold.

Steps:

  1. Check if there is traffic for requests other than registration (for example, discovery requests). This ensures that NRF FQDN is reachable from other NFs and Ingress Gateway is up and running in all NRF Sets.
  2. Check if the Ingress Gateway pod is up and running in all NRF sets.
    kubectl get po -n <namespace>
  3. Validate that the CDS synchronization with remote NRF sets is successful. Validate below alerts are not present in the system:
    1. OcnrfSyncFailureFromAllNrfsOfAnyRemoteSet
    2. OcnrfSyncFailureFromAllNrfsOfAllRemoteSets
  4. Check for registration pod logs on Kibana for ERROR WARN logs.
  5. In case the issue persists, capture all the outputs for the above steps and contact My Oracle Support.

    Note: Use the CNC NF Data Collector tool for capturing logs. For more information on how to collect logs using the Data Collector tool, see Oracle Communications Cloud Native Core, cnDBTier User Guide.

Available in OCI No
6.3.4.13.7 OcnrfTotalNFsRegisteredAtSegmentBelowMajorThreshold

Table 6-666 OcnrfTotalNFsRegisteredAtSegmentBelowMajorThreshold

Field Details
Description The alert is raised when the number of NFs registered at the segment is below the configured major threshold.
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : The number of NFs registered at the segment is below major threshold
Severity Major
Condition The number of NFs registered at the segment is below major threshold.

Note: This alert is triggered when the registered NF count is greater than or equal to 2 and below 10. This default value can be modified in the ocnrf_alertrules_25.1.200.yaml or ocnrf_alertrules_promha_25.1.200.yaml file depending on Prometheus version.

OID 1.3.6.1.4.1.323.5.3.36.1.2.7104
Metric Used ocnrf_nf_registered_count
Recommended Actions

The alert is cleared when the number of registered NFs in the segment is above the major threshold.

Steps:

  1. Check if there is traffic for requests other than registration (for example, discovery requests). This ensures that NRF FQDN is reachable from other NFs and Ingress Gateway is up and running in all NRF sets.
  2. Check if the Ingress Gateway pod is up and running in all NRF sets.
    kubectl get po -n <namespace>
    
  3. Validate that the CDS synchronization with remote NRF sets is successful. Validate below alerts are not present in the system:
    1. OcnrfSyncFailureFromAllNrfsOfAnyRemoteSet
    2. OcnrfSyncFailureFromAllNrfsOfAllRemoteSets
  4. Check for registration pod logs on Kibana for ERROR WARN logs.
  5. In case the issue persists, capture all the outputs for the above steps and contact My Oracle Support.

    Note: Use the CNC NF Data Collector tool for capturing logs. For more information on how to collect logs using the Data Collector tool, see Oracle Communications Cloud Native Core, cnDBTier User Guide.

Available in OCI No
6.3.4.13.8 OcnrfTotalNFsRegisteredAtSegmentBelowCriticalThreshold

Table 6-667 OcnrfTotalNFsRegisteredAtSegmentBelowCriticalThreshold

Field Details
Description The alert is raised when the number of NFs registered at the segment is below the configured critical threshold.
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : The number of NFs registered at the segment is below critical threshold'
Severity Critical
Condition The number of NFs registered at the segment is below critical threshold.

Note: This alert is triggered when the registered NF count is below 2. This default value can be modified in the ocnrf_alertrules_25.1.200.yaml or ocnrf_alertrules_promha_25.1.200.yaml file depending on Prometheus version.

OID 1.3.6.1.4.1.323.5.3.36.1.2.7105
Metric Used ocnrf_nf_registered_count
Recommended Actions

The alert is cleared when the number of registered NFs in the segment is above the critical threshold.

Steps:

  1. Check if there is traffic for requests other than registration (for example, discovery requests). This ensures that NRF FQDN is reachable from other NFs and Ingress Gateway is up and running in all NRF sets.
  2. Check if the Ingress Gateway pod is up and running in all NRF sets.
    kubectl get po -n <namespace>
  3. Validate that the CDS synchronization with remote NRF sets is successful. Validate below alerts are not present in the system:
    1. OcnrfSyncFailureFromAllNrfsOfAnyRemoteSet
    2. OcnrfSyncFailureFromAllNrfsOfAllRemoteSets
  4. Check for registration pod logs on Kibana for ERROR WARN logs.
  5. In case the issue persists, capture all the outputs for the above steps and contact My Oracle Support.

    Note: Use the CNC NF Data Collector tool for capturing logs. For more information on how to collect logs using the Data Collector tool, see Oracle Communications Cloud Native Core, cnDBTier User Guide.

6.3.4.14 Ingress Gateway Pod Protection Feature

This section lists the alerts that are specific to Ingress Gateway Pod Protection feature. For more information about the feature, see the Ingress Gateway Pod Protection section.

6.3.4.14.1 OcnrfIngressGatewayPodInDangerOfCongestionState

Table 6-668 OcnrfIngressGatewayPodInDangerOfCongestionState

Field Details
Description 'The pod {{$labels.kubernetes_pod_name}} is in Danger of Congestion state'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, podname: {{$labels.kubernetes_pod_name}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : The pod is in Danger of Congestion state'
Severity Major
Condition

When Ingress Gateway pod is in Danger Of Congestion state.

OID 1.3.6.1.4.1.323.5.3.36.1.2.7092
Metric Used oc_ingressgateway_pod_congestion_state
Recommended Actions The alert is cleared when the pod is out of Danger Of Congestion (DoC) state.

Note: The thresholds can be viewed using REST API.

Steps:

Reassess if the NRF is receiving additional traffic.

If this is unexpected, contact My Oracle Support.

  1. Refer to alert to determine which pod is receiving high traffic. It may due to a sudden spike in traffic. For example: When one mated site goes down, the NFs move to the given site. Check if NF is sending high number of updates, register, or deregister.
  2. Check the service pod logs on Kibana to determine the reason for the errors.
  3. If this is expected traffic, then the thresholds levels may need to be re-evaluated as per the call rate and reconfigured as mentioned in Oracle Communications Cloud Native Core, Network Repository Function REST Specification Guide.
Available in OCI No
6.3.4.14.2 OcnrfIngressGatewayPodInCongestedState

Table 6-669 OcnrfIngressGatewayPodInCongestedState

Field Details
Description 'The pod {{$labels.kubernetes_pod_name}} is in Congested state'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, podname: {{$labels.kubernetes_pod_name}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : The pod is in Congested state'
Severity Critical
Condition

When Ingress Gateway pod is in Congested state.

OID 1.3.6.1.4.1.323.5.3.36.1.2.7093
Metric Used oc_ingressgateway_pod_congestion_state
Recommended Actions The alert is cleared when the pod is out of Congested state.

Note: The thresholds can be viewed using REST API.

Steps:

Reassess if the NRF is receiving additional traffic.

If this is unexpected, contact My Oracle Support.

  1. Refer to alert to determine which pod is receiving high traffic. It may due to a sudden spike in traffic. For example: When one mated site goes down, the NFs move to the given site. Check if NF is sending high number of updates, register, or deregister.
  2. Check the service pod logs on Kibana to determine the reason for the errors.
  3. If this is expected traffic, then the thresholds levels may need to be re-evaluated as per the call rate and reconfigured as mentioned in Oracle Communications Cloud Native Core, Network Repository Function REST Specification Guide.
Available in OCI No
6.3.4.14.3 OcnrfIngressGatewayPodCpuUsageInCongestedState

Table 6-670 OcnrfIngressGatewayPodCpuUsageInCongestedState

Field Details
Description 'The pod {{$labels.kubernetes_pod_name}} is in Congested state'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}},podname: {{$labels.kubernetes_pod_name}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : The pod is in Congested state'
Severity Critical
Condition

Ingress Gateway pod is in Congested state due to CPU consumption above the configured thresholds.

OID 1.3.6.1.4.1.323.5.3.36.1.2.7094
Metric Used oc_ingressgateway_pod_resource_state
Recommended Actions The alert is cleared when the CPU consumption goes below the configured thresholds for the Congested state.

Note: The thresholds can be viewed using REST API.

Steps:

Reassess if the NRF is receiving additional traffic.

If this is unexpected, contact My Oracle Support.

  1. Refer to alert to determine which pod is receiving high traffic. It may due to a sudden spike in traffic. For example: When one mated site goes down, the NFs move to the given site. Check if NF is sending high number of updates, register, or deregister.
  2. Check the service pod logs on Kibana to determine the reason for the errors.
  3. If this is expected traffic, then the thresholds levels may need to be re-evaluated as per the call rate and reconfigured as mentioned in Oracle Communications Cloud Native Core, Network Repository Function REST Specification Guide.
Available in OCI No
6.3.4.14.4 OcnrfIngressGatewayPodCpuUsageInDangerOfCongestionState

Table 6-671 OcnrfIngressGatewayPodCpuUsageInDangerOfCongestionState

Field Details
Description 'The pod {{$labels.kubernetes_pod_name}} is in Danger of Congestion state due to CPU usage above threshold'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}},podname: {{$labels.kubernetes_pod_name}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : The pod is in Danger of Congestion state due to CPU usage above threshold'
Severity Major
Condition

Ingress Gateway pod is in Danger of Congestion state due to CPU consumption above the configured thresholds.

OID 1.3.6.1.4.1.323.5.3.36.1.2.7095
Metric Used oc_ingressgateway_pod_resource_state
Recommended Actions The alert is cleared when the CPU consumption is not as per the configured thresholds value for the Danger of Congestion state.

Note: The thresholds can be viewed using REST API.

Steps:

Reassess if the NRF is receiving additional traffic.

If this is unexpected, contact My Oracle Support.

  1. Refer to alert to determine which pod is receiving high traffic. It may due to a sudden spike in traffic. For example: When one mated site goes down, the NFs move to the given site. Check if NF is sending high number of updates, register, or deregister.
  2. Check the service pod logs on Kibana to determine the reason for the errors.
  3. If this is expected traffic, then the thresholds levels may need to be re-evaluated as per the call rate and reconfigured as mentioned in Oracle Communications Cloud Native Core, Network Repository Function REST Specification Guide.
Available in OCI No
6.3.4.14.5 OcnrfIngressGatewayPodPendingMessageInCongestedState

Table 6-672 OcnrfIngressGatewayPodPendingMessageInCongestedState

Field Details
Description 'The pod {{$labels.kubernetes_pod_name}} is in Congested state'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}},podname: {{$labels.kubernetes_pod_name}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : The pod is in Congested state'
Severity Critical
Condition

Ingress Gateway pod is in Congested state due to pending message count above the configured thresholds.

OID 1.3.6.1.4.1.323.5.3.36.1.2.7096
Metric Used oc_ingressgateway_pod_resource_state
Recommended Actions The alert is cleared when the pending message count is not as per the configured thresholds value for the Congested state.

Note: The thresholds can be viewed using REST API.

Steps:

Reassess if the NRF is receiving additional traffic.

If this is unexpected, contact My Oracle Support.

  1. Refer to alert to determine which pod is receiving high traffic. It may due to a sudden spike in traffic. For example: When one mated site goes down, the NFs move to the given site. Check if NF is sending high number of updates, register, or deregister.
  2. Check the service pod logs on Kibana to determine the reason for the errors.
  3. If this is expected traffic, then the thresholds levels may need to be re-evaluated as per the call rate and reconfigured as mentioned in Oracle Communications Cloud Native Core, Network Repository Function REST Specification Guide.
Available in OCI No
6.3.4.14.6 OcnrfIngressGatewayPodPendingMessageInDangerOfCongestionState

Table 6-673 OcnrfIngressGatewayPodPendingMessageInDangerOfCongestionState

Field Details
Description 'The pod {{$labels.kubernetes_pod_name}} is in Danger of Congestion state due to Pending Message above threshold'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}},podname: {{$labels.kubernetes_pod_name}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : The pod is in Danger of Congestion state due to Pending Message above threshold'
Severity Major
Condition

Ingress Gateway pod is in Danger of Congestion state due to pending message count above the configured thresholds.

OID 1.3.6.1.4.1.323.5.3.36.1.2.7097
Metric Used oc_ingressgateway_pod_resource_state
Recommended Actions The alert is cleared when the pending message count is not as per the configured thresholds value for the Danger of Congestion state.

Note: The thresholds can be viewed using REST API.

Steps:

Reassess if the NRF is receiving additional traffic.

If this is unexpected, contact My Oracle Support.

  1. Refer to alert to determine which pod is receiving high traffic. It may due to a sudden spike in traffic. For example: When one mated site goes down, the NFs move to the given site. Check if NF is sending high number of updates, register, or deregister.
  2. Check the service pod logs on Kibana to determine the reason for the errors.
  3. If this is expected traffic, then the thresholds levels may need to be re-evaluated as per the call rate and reconfigured as mentioned in Oracle Communications Cloud Native Core, Network Repository Function REST Specification Guide.
Available in OCI No
6.3.4.15 Subscriber Location Function Feature

This section lists the alert that is specific to Subscriber Location Function feature. For more information about the feature, see the Subscriber Location Function section.

6.3.4.15.1 OcnrfMaxSlfAttemptsExhausted

Table 6-674 OcnrfMaxSlfAttemptsExhausted

Field Details
Description 'NF discovery request with fqdn {{$labels.NfProfileFqdn}} NF type {{$labels.NfType}} has exhausted maximum SLF attempts'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, nrflevel:{{$labels.NrfLevel}}, podname: {{$labels.kubernetes_pod_name}}, NfProfileFqdn: {{$labels.NfProfileFqdn}}, NfType: {{$labels.NfType}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }}: The maximum slf attempts have exhausted.'
Severity Critical
Condition

NF discovery request with FQDN of the given NFType UDR has exhausted maximum SLF attempts. This alert is raised when the ocnrf_max_slf_attempts_exhausted_total metric is pegged.

Note: This alert is included if SLF selection from registered profiles is enabled.

OID 1.3.6.1.4.1.323.5.3.36.1.2.7054
Metric Used 'ocnrf_max_slf_attempts_exhausted_total'
Recommended Actions

The alert is cleared automatically after 5 minutes.

Steps:
  1. Check logs in NF discovery pod to check the reason for SLF query failures.
  2. In DISCOVERED_SLF_CONFIG_MODE, make sure that SLFs are registered with valid IPV4, PV6, or FQDN information. Verify the same in the slfDiscoveredCandidateList from the slfOptions.
  3. In STATIC_SLF_CONFIG_MODE, verify if slfHostConfig details are configured correctly.

    Note: Use CNC NF Data Collector tool for capturing logs. For more information on how to collect logs using Data Collector tool, see Oracle Communications Cloud Native Core, Network Function Data Collector User Guide.

Available in OCI Yes
6.3.4.16 EmptyList in Discovery Response Feature

This section lists the alert that is specific to EmptyList in Discovery Response feature. For more information about the feature, see the EmptyList in Discovery Response section.

6.3.4.16.1 OcnrfNFDiscoveryEmptyListObservedNotification

Table 6-675 OcnrfNFDiscoveryEmptyListObservedNotification

Field Details
Description 'Empty List observed with received discovery request with NfType $labels.NfType Feature Status $labels.FeatureStatus'
Summary 'namespace: $labels.namespace, nrflevel:$labels.NrfLevel, podname: $labels.pod, NfType: $labels.NfType, FeatureStatus: $labels.FeatureStatus: Empty List observed with received discovery request'
Severity Critical
Condition

This alarm is raised when profiles do not match the discovery request.

Also, this alarm is raised when the SUSPENDED profile is in response to incoming request and Empty List feature is enabled.

OID 1.3.6.1.4.1.323.5.3.36.1.2.7055
Metric Used ocnrf_nfDiscover_emptyList_total
Recommended Actions

The alert is cleared automatically after a duration of 5 minutes.

Steps:

  1. Collect the logs.
  2. Check logs for the following conditions:
    • Verify if the NF has sent Empty List in response in NRF Discovery.
    • Check if NF has sent SUSPENDED profiles in response for incoming requests when EmptyList feature is ENABLED.
    • If the response is not Empty List or does not contain SUSPENDED profiles.
  3. If the alert still persists, contact My Oracle Support.
Note: Use CNC NF Data Collector tool for capturing logs. For more details, see Oracle Communications Cloud Native Core, Network Function Data Collector User Guide.
Available in OCI No
6.3.4.17 Support for TLS

This section lists the alert that is specific to Support for TLS feature. For more information about the feature, see the Support for TLS section.

6.3.4.17.1 OcnrfTLSCertificateExpireMinor

Table 6-676 OcnrfTLSCertificateExpireMinor

Field Details
Description 'TLS certificate to expire in 6 months'.
Summary 'namespace: {{$labels.namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : TLS certificate to expire in 6 months'
Severity Minor
Condition This alert is raised when the TLS certificate is about to expire in six months.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7106
Metric Used security_cert_x509_expiration_seconds
Recommended Actions

The alert is cleared when the TLS certificate is renewed.

For more information about certificate renewal, see "Creating Private Keys and Certificate " section in the Oracle Communications Cloud Native Core, Network Repository Function Installation, Upgrade, and Fault Recovery Guide.

Available in OCI No
6.3.4.17.2 OcnrfTLSCertificateExpireMajor

Table 6-677 OcnrfTLSCertificateExpireMajor

Field Details
Description 'TLS certificate to expire in 3 months.'
Summary 'namespace: {{$labels.namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : TLS certificate to expire in 3 months'
Severity Major
Condition This alert is raised when the TLS certificate is about to expire in three months.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7107
Metric Used security_cert_x509_expiration_seconds
Recommended Actions

The alert is cleared when the TLS certificate is renewed.

For more information about certificate renewal, see "Creating Private Keys and Certificate" section in the Oracle Communications Cloud Native Core, Network Repository Function Installation, Upgrade, and Fault Recovery Guide.

Available in OCI No
6.3.4.17.3 OcnrfTLSCertificateExpireCritical

Table 6-678 OcnrfTLSCertificateExpireCritical

Field Details
Description 'TLS certificate to expire in one month.'
Summary 'namespace: {{$labels.namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} : TLS certificate to expire in 1 month'
Severity Critical
Condition This alert is raised when the TLS certificate is about to expire in one month.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7108
Metric Used security_cert_x509_expiration_seconds
Recommended Actions

The alert is cleared when the TLS certificate is renewed.

For more information about certificate renewal, see "Creating Private Keys and Certificate" section in the Oracle Communications Cloud Native Core, Network Repository Function Installation, Upgrade, and Fault Recovery Guide.

Available in OCI No
6.3.4.18 Egress Gateway Pod Throttling
6.3.4.18.1 OcnrfEgressPerPodDiscardRateAboveMajorThreshold

Table 6-679 OcnrfEgressPerPodDiscardRateAboveMajorThreshold

Field Details
Description 'Egressgateway PerPod Discard Rate is greater than the configured major threshold. (current value is: {{ $value }})'
Summary 'kubernetes_namespace: {{$labels.namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }}: Egressgateway PerPod Discard Rate is more than 1 request per second.'
Severity Major
Condition This alert is raised when the Egress Gateway pods discard traffic due to its request limit is greater than the configured threshold.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7113
Metric Used oc_egressgateway_podlevel_throttling_discarded_total
Recommended Actions The alert is cleared when the Egress Gateway pods discard traffic rate falls below the major threshold.

Note: The threshold is configurable in the alert file. Reassess why the NRF is receiving additional traffic (for example, Mated site NRF is unavailable in georedundancy scenario). If this alert is unexpected, contact My Oracle Support.

Steps:

  1. Refer Egress Gateway section in Grafana to determine which service is sending high traffic.
  2. Refer Egress Gateway section in Grafana to determine the increase in 4xx and 5xx error codes.
  3. Check Egress Gateway logs on Kibana to determine the reason for the errors.
Available in OCI No
6.3.4.18.2 OcnrfEgressPerPodDiscardRateAboveCriticalThreshold

Table 6-680 OcnrfEgressPerPodDiscardRateAboveCriticalThreshold

Field Details
Description 'Egressgateway PerPod Discard Rate is greater than the configured critical threshold. (current value is: {{ $value }})'
Summary 'kubernetes_namespace: {{$labels.namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }}: Egressgateway PerPod Discard Rate is more than 100 requests per second.’
Severity Critical
Condition This alert is raised when the Egress Gateway pods discard traffic due to its request limit is greater than the configured threshold.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7114
Metric Used oc_egressgateway_podlevel_throttling_discarded_total
Recommended Actions The alert is cleared when the Egress Gateway pods discard traffic rate falls below the critical threshold.

Note: The threshold is configurable in the alert file. Reassess why the NRF is receiving additional traffic (for example, Mated site NRF is unavailable in georedundancy scenario). If this alert is unexpected, contact My Oracle Support.

Steps:

  1. Refer Egress Gateway section in Grafana to determine which service is sending high traffic.
  2. Refer Egress Gateway section in Grafana to determine the increase in 4xx and 5xx error codes.
  3. Check Egress Gateway logs on Kibana to determine the reason for the errors.
Available in OCI No
6.3.4.19 Ingress Gateway Pod Protection Using Rate Limiting
6.3.4.19.1 OcnrfIngressDiscardDueToRateLimitMajorThreshold

Table 6-681 OcnrfIngressDiscardDueToRateLimitMajorThreshold

Field Details
Description 'Ingress Gateway discards due to rate limit exceeds the configured major threshold. (current value is: {{ $value }})'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }}: Ingressgateway Discard due to Rate Limit is more than or equal to 1 requests per second and less than 100 requests per second.'
Severity Major
Condition This alert is raised when Ingress Gateway discard requests as rate limit exceeds the configured major threshold.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7129
Metric Used oc_ingressgateway_http_request_ratelimit_denied_count_total
Recommended Actions

The alert is cleared when the Ingress Gateway pods discard traffic rate falls below the major threshold or exceeds the critical threshold.

Note: The threshold is configurable in the alert file. Reassess why the NRF is receiving additional traffic (for example, Mated site NRF is unavailable in georedundancy scenario). If this alert is unexpected, contact My Oracle Support.

Steps:

  1. Refer Ingress Gateway Pod Protection By Rate Limit section in Grafana to determine which pods are overloaded and the rate of traffic received.
  2. Refer Ingress Gateway section in Grafana to determine the increase in 4xx and 5xx error codes.
  3. Refer the Grafana dashboard to determine which service traffic is above expectation.
Available in OCI No
6.3.4.19.2 OcnrfIngressDiscardDueToRateLimitCriticalThreshold

Table 6-682 OcnrfIngressDiscardDueToRateLimitCriticalThreshold

Field Details
Description 'Ingress gateway discards due to rate limit exceeds the configured critical threshold. (current value is: {{ $value }})'
Summary 'kubernetes_namespace: {{$labels.kubernetes_namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }}: Ingressgateway Discard due to Rate Limit is more than or equal to 100 requests per second.'
Severity Critical
Condition This alert is raised when Ingress Gateway discard requests as rate limit exceeds the configured critical threshold.
OID 1.3.6.1.4.1.323.5.3.36.1.2.7130
Metric Used oc_ingressgateway_http_request_ratelimit_denied_count_total
Recommended Actions

The alert is cleared when the Ingress Gateway pods discard traffic rate falls below the critical threshold.

Note: The threshold is configurable in the alert file. Reassess why the NRF is receiving additional traffic (for example, Mated site NRF is unavailable in georedundancy scenario). If this alert is unexpected, contact My Oracle Support.

Steps:

  1. Refer Ingress Gateway Pod Protection By Rate Limit section in Grafana to determine which pods are overloaded and the rate of traffic received.
  2. Refer Ingress Gateway section in Grafana to determine the increase in 4xx and 5xx error codes.
  3. Refer the Grafana dashboard to determine which service traffic is above expectation.
Available in OCI No

6.3.5 NRF Alert Configuration

This section describes the measurement based alert rules configuration for NRF. The Alert Manager uses the Prometheus measurements values as reported by microservices in conditions under alert rules to trigger alerts.

Note:

  • Alert file is packaged with NRF custom templates. The NRF CSAR package can be downloaded from MOS. Unzip the NRF CSAR package file to get the Alertrules.yaml file.
  • Review the Alertrules.yaml file and edit the value of the parameters in the Alertrules.yaml file (if needed to be changed from default values) before configuring the alerts. See below table for details.
  • kubernetes_namespace is configured as Kubernetes namespace in which NRF is deployed. Default value is NRF. Update the Alertrules.yaml file to reflect the correct NRF Kubernetes namespace.
Alert details which can be updated in Alertrules.yaml file before configuration

Table 6-683 Alerts

Alert Name Details Default Value Notes
OcnrfTotalIngressTrafficRateAboveMinorThreshold Traffic Rate is above 80 Percent of Max requests per second Greater than/equal to 800 and Less than 900

Maximum Ingress rate considered is 1000 requests per second.

So, here in default value 800 is 80% of 1000 and 900 is 90% of 1000.

For example, if value need to be updated then depending upon maximum ingress request rate, set [ 90% of Max Ingress Request Rate] and [ 80% of Max Ingress Request Rate] for this alert

OcnrfTotalIngressTrafficRateAboveMajorThreshold Traffic Rate is above 90 Percent of Max requests per second Greater than/equal to 900 and Less than 950

Maximum Ingress rate considered is 1000 requests per second.

So, here in default value 900 is 90% of 1000 and 950 is 95% of 1000.

For example, if value need to be updated then depending upon maximum ingress request rate, set [ 90% of Max Ingress Request Rate] and [ 95% of Max Ingress Request Rate] for this alert
OcnrfTotalIngressTrafficRateAboveCriticalThreshold Traffic Rate is above 95 Percent of Max requests per second Greater than/equal to 950

Maximum Ingress rate considered is 1000 requests per second.

So, here in default value 950 is 95% of 1000.

For example, if value need to be updated then depending upon maximum ingress request rate, set [ 95% of Max Ingress Request Rate] for this alert

NRF Alert configuration in Prometheus

Update NRF alerts for CNE 1.8.x and previous versions

The following procedure describes how to update the NRF alerts for CNE version 1.8.x and previous versions:

_NAME_ :- Helm Release of Prometheus

_Namespace_ :- Kubernetes NameSpace in which Prometheus is installed

  1. Find the config map to configure alerts in Prometheus server using the following command:
    kubectl get configmap -n <Namespace>
    where, <Namespace> is the prometheus server namespace used in helm install command. For example, assuming Prometheus server is under occne-infra namespace, run the following command to find the config map:
    kubectl get configmaps -n occne-infra | grep prometheus-server 
  2. Take backup of current configuration map of Prometheus:
    kubectl get configmaps _NAME_-server -o yaml -n _Namespace_ > /tmp/tempConfig.yaml
  3. Check if alertsnrf is present in the tempConfig.yaml file by running the following command:
    cat /tmp/tempConfig.yaml | grep alertsnrf

    Depending on the outcome of the previous step, perform anyone of the following steps:

    1. If alertsnrf is present, delete the alertsnrf entry from the tempConfig.yaml file, by running the following commands:
      sed -i '/etc\/config\/alertsnrf/d' /tmp/tempConfig.yaml
      sed -i '/rule_files:/a\  \- /etc/config/alertsnrf' /tmp/tempConfig.yaml

      Note:

      This command should be run only once.
    2. If alertsnrf is not present, add the alertsnrf entry in the tempConfig.yaml file by running the following command:
      sed -i '/rule_files:/a\  \- /etc/config/alertsnrf' /tmp/tempConfig.yaml
  4. Update configuration map with updated file name of NRF alert file:
    kubectl replace configmap _NAME_-server -f /tmp/tempConfig.yaml
  5. Add NRF alert rules in configuration map under file name of NRF alert file:
    kubectl patch configmap _NAME_-server -n _Namespace_--type merge --patch
    "$(cat ~/NrfAlertrules.yaml)"

Update NRF alerts for CNE 1.9.x

This section describes the measurement based Alert rules configuration for NRF in Prometheus. Use the ocnrf_alerting_rules_promha_25.1.200.yaml file updated in NRF Alert configuration section.

  1. Run the following command to apply the prometheusrules CRD:
    $ kubectl apply -f ocnrf_alerting_rules_promha_25.1.200.yaml --namespace <namespace>
    Example:
    $ kubectl apply -f ocnrf_alerting_rules_promha_25.1.200.yaml --namespace ocnrf
      prometheusrule.monitoring.coreos.com/ocnrf-alerting-rules created
  2. Run the following command to check NRF alert file is added to prometheusrules:
    $ kubectl get prometheusrules --namespace <namespace>
    Example:
    $ kubectl get prometheusrules --namespace ocnrf
    
    Sample output:
    NAME                          AGE
    ocnrf-alerting-rules          1m
  3. Log in to Prometheus GUI and verify the alerts.
    The following alert configuration file must be loaded as shown in the figure.

    Figure 6-2 Prometheus Alert Manager

    Prometheus Alert Manager

Note:

The Prometheus server takes an updated configuration map that is automatically reloaded after approximately 60 seconds. Refresh the Prometheus GUI to confirm that the NRF Alerts have been reloaded.

Validating Alerts

After configuring the alerts in Prometheus server, a user can verify the same by following steps:

  • Open the Prometheus server from your browser using the <IP>:<Port>
  • Navigate to Status and then Rules.
  • Search Ocnrf. OcnrfAlerts list will appear.

    Note:

    If you are unable to see the alerts, it means the alert file is not loaded in a format that Prometheus server accepts. Modify the file and try again.
6.3.5.1 Disable Alerts
This section explains the procedure to disable the alerts in NRF.
  1. Edit NrfAlertrules-25.1.200.yaml file to remove a specific alert.
  2. Remove complete content of a specific alert from the NrfAlertrules-25.1.200.yaml file.
    For example: If you want to remove OcnrfTrafficRateAboveMinorThreshold alert, remove the complete content:
    ## ALERT SAMPLE START##
    
          - alert: OcnrfTrafficRateAboveMinorThreshold
            annotations:
              description: 'Ingress traffic Rate is above minor threshold i.e. 800 mps (current value is: {{ $value }})'
              summary: 'Traffic Rate is above 80 Percent of Max requests per second(1000)'
            expr: sum(rate(oc_ingressgateway_http_requests_total{app_kubernetes_io_name="ingressgateway",kubernetes_namespace="ocnrf"}[2m])) >= 800 < 900
            labels:
              severity: Minor
    ## ALERT SAMPLE END##
  3. Perform Alert configuration. For more information about configuring alerts, see NRF Alert Configuration section.
6.3.5.2 Configuring SNMP Notifier

This section describes the procedure to configure SNMP Notifier.

Configure the IP and port of the SNMP trap receiver in the SNMP Notifier using the following procedure:
  1. Run the following command to edit the deployment:
    $ kubectl edit deploy <snmp_notifier_deployment_name> -n <namespace>

    Example:

    $ kubectl edit deploy occne-snmp-notifier -n occne-infra

    SNMP deployment yaml file is displayed.

  2. Edit the SNMP destination in the deployment yaml file as follows:
    --snmp.destination=<destination_ip>:<destination_port>

    Example:

    --snmp.destination=10.75.203.94:162
  3. Save the file.
Checking SNMP Traps
Following is an example on how to capture the logs of the trap receiver server to view the generated SNMP traps:
$ docker logs <trapd_container_id>
Sample output:
2020-04-29 15:34:24 10.75.203.103 [UDP: [10.75.203.103]:2747->[172.17.0.4]:162]:DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (158510800) 18 days, 8:18:28.00        SNMPv2-MIB::snmpTrapOID.0 = OID: SNMPv2-SMI::enterprises.323.5.3.36.1.2.7003    SNMPv2-SMI::enterprises.323.5.3.36.1.2.7003.1 = STRING: "1.3.6.1.4.1.323.5.3.36.1.2.7003[]"  SNMPv2-SMI::enterprises.323.5.3.36.1.2.7003.2 = STRING: "critical"      SNMPv2-SMI::enterprises.323.5.3.36.1.2.7003.3 = STRING: "Status: critical- Alert: OcnrfActiveSubscribersBelowCriticalThreshold  Summary: namespace: ocnrf, nftype:5G_EIR, nrflevel:6faf1bbc-6e4a-4454-a507-a14ef8e1bc5c, podname: ocnrf-nrfauditor-6b459f5db5-4kvt4,
        timestamp: 2020-04-29 15:33:24.408 +0000 UTC: Current number of registered NFs detected below critical threshold.  Description: The number of registered NFs detected below critical threshold (current value
          is: 0)
MIB Files for NRF

There are two MIB files which are used to generate the traps. The user need to update these files along with the Alert file in order to fetch the traps in their environment.

  • ocnrf_mib_tc_25.1.200.mib

    This is considered as NRF top level mib file, where the objects and their data types are defined.

  • ocnrf_mib_25.1.200.mib

    This file fetches the objects from the top level mib file and based on the alert notification, these objects can be selected for display.

  • toplevel_25.1.200.mib: This defines the OIDs for all NFs.

Note:

MIB files are packaged along with the release package. Download the file from MOS. For more information on downloading the release package, see Oracle Communications Cloud Native Core, Network Repository Function Installation, Upgrade, and Fault Recovery Guide.

6.3.6 NRF Alert Configuration in OCI

The following procedure describes how to configure the NRF alerts for OCI. The OCI supports metric expressions written in MQL (Metric Query Language) and thus, requires a new NRF alert file for configuring alerts in OCI observability platform.

The following are the steps:

  1. Run the following command to extract the .zip file:
    unzip ocnrf_oci_alertrules_<version>.zip
    The ocnrf_oci and ocnrf_oci_resources folders are available in the zip file.

    Note:

    The zip file is available in the Scripts folder of CSAR package.
  2. Open the ocnrf_oci folder, in the notifications.tf file, update the parameter endpoint with the email id of the user.
  3. Open the ocnrf_oci_resources folder, in the notifications.tf file, update the parameter endpoint with the email id of the user (replace test@gmail.com with the email id of the user).
  4. Log in to the OCI Console.

    Note:

    For more details about logging in to the OCI, refer to Signing In to the OCI Console.
  5. Open the navigation menu and select Developer Services. The Developer Services window appears in the right pane.
  6. Under the Developer Services, select Resource Manager.
  7. Under Resource Manager, select Stacks. The Stacks window appears.
  8. Click Create Stack.
  9. Select the default My Configuration radio button.
  10. Under Stack configuration, select the folder radio button and upload the ocnrf_oci folder.
  11. Enter the Name and Description and select the compartment.
  12. Select the latest Terraform version from the Terraform version drop-down.
  13. Click Next. The Edit Stack screen appears.
  14. Enter the required inputs to create the NRF alerts or alarms and click Save and Run Apply.
  15. Verify that the alarms are created in the Alarm Definitions screen (OCI Console> Observability & Management> Monitoring>Alarm Definitions) provided.

    The required inputs are:

    • Alarms Configuration
      • Compartment Name - Choose name of compartment from the drop-down
      • Metric namespace - Metric namespace that the user provided while deploying OCI Adaptors.
      • Topic Name - Any user configurable name. Must contain fewer than 256 characters. Only alphanumeric characters plus hyphens (-) and underscores (_) are allowed.
      • Message Format - Keep it as ONS_OPTIMIZED. (This is pre-populated)
      • Alarm is_enabled - Keep it as True. (This is pre-populated)
  16. The steps 6 to 16 must be repeated for uploading the ocnrf_oci_resources folder. Keep Metric namespace as mgmtagent_kubernetes_metrics (This is pre-populated).