5.2.10.1 SEPPPn32fHSRoutingFailureAlert

Table 5-51 SEPPPn32fHSRoutingFailureAlert

Field Details
Trigger Condition When the routing failure rate at Pn32f service is greater than 20 percentage.
Severity Major
Alert details provided Summary
namespace: {{$labels.namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }}: Routing has failed due to {{ $labels.http_error_message }}
Expression:
((sum by(namespace, app, nf_instance_id, pod) (ocsepp_allowed_p_rss_routing_failure_total{namespace="sepp-namespace"}) ) / (sum by(namespace, app, nf_instance_id, pod) (ocsepp_pn32f_requests_total{namespace="sepp-namespace"}))) > 0.2
OID 1.3.6.1.4.1.323.5.3.46.1.2.4013
Metric Used ocsepp_allowed_p_rss_routing_failure_total , ocsepp_pn32f_requests_total
Resolution The alert gets automatically cleared when the failure rate at pn32f microservice goes below 20 percent.
Possible resolutions:
  1. If a request gets rejected due to Remote SEPP Set not being present in allowed list, add the corresponding entry for the same.
  2. For further details, refer 'Hosted SEPP' section in the Oracle Communications Cloud Native Core, Security Edge Protection Proxy Troubleshooting Guide.