5.2.10.4 SEPPCn32fHSRoutingFailureAlertCritical

Table 5-54 SEPCn32fHSRoutingFailureAlertCritical

Field Details
Trigger Condition When the routing failure rate at Cn32f service is greater than 65 percentage.
Severity Critical
Alert details provided Summary
namespace: {{$labels.namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }}: Routing has failed due to {{ $labels.http_error_message }} for {{ $labels.sourceRss }}
Expression:
((sum by(namespace, app, nf_instance_id, pod, sourceRss) (ocsepp_allowed_p_rss_routing_failure_total{namespace="sepp-namespace"}) ) / (sum by(namespace, app, nf_instance_id, pod, sourceRss) (ocsepp_cn32f_requests_total{namespace="sepp-namespace"}))) > 0.65
OID 1.3.6.1.4.1.323.5.3.46.1.2.4016
Metric Used ocsepp_allowed_p_rss_routing_failure_total, ocsepp_cn32f_requests_total
Resolution The alert gets automatically cleared when the failure rate at cn32f microservice goes below 65 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.