5.2.12.3 SEPPPn32fSORFailureAlertPercentAbove50

Table 5-62 SEPPPn32fSORFailureAlertPercentAbove50

Field Details
Trigger Condition 50% of SOR traffic results in failure
Severity Critical
Alert details provided Summary:

'namespace: {{$labels.namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }}'

Expression:
sum(rate(ocsepp_pn32f_sor_failure_total{namespace="sepp-namespace"}[2m]))by(namespace,nf_instance_id,app)/sum(rate(ocsepp_pn32f_sor_requests_total{namespace="sepp-namespace"}[2m]))by(namespace,nf_instance_id,app)>=0.5

OID 1.3.6.1.4.1.323.5.3.46.1.2.4024
Metric Used ocsepp_pn32f_sor_failure_total

and

ocsepp_pn32f_sor_requests_total
Resolution

This alert will be raised when the percentage failure of SOR responses is above 50%, in the sample collected in last 2 min.

Possible Resolutions:

  1. Check the below headers in the response coming from SOR server, if any of these is missing, it will cause SOR Failure:
    1. Server Header
    2. Location Header
  2. Check if the redirection code(3xx) received from SOR should be same as one configured via CNC Console. This code can be viewed in the metricocsepp_pn32f_sor_failure_total.
  3. Check if SOR Server is sending response code 5xx and the code is not configured through CNC Console or retry to Producer NF is disabled. This code can be viewed in the metricocsepp_pn32f_sor_failure_total.
  4. Check if any client error(4xx) is coming while connecting to SOR. This code can be viewed in the metricocsepp_pn32f_sor_failure_total.