5.2.12.1 SEPPPn32fSORFailureAlertPercent30to40

Table 5-60 SEPPPn32fSORFailureAlertPercent30to40

Field Details
Trigger Condition 30% to 40% of SOR traffic results in failure.
Severity Minor
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.3 and 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.4
OID 1.3.6.1.4.1.323.5.3.46.1.2.4022
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 in the range 30%-40%, 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 the same as the one configured through CNC Console. This code can be viewed in the metricocsepp_pn32f_sor_failure_total.
  3. Check if the SOR Server is sending the response code 5xx and whether the code is not configured through CNC Console or retry to Producer NF is disabled. This code can be viewed in the metric ocsepp_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.