5.2.16.4 seppN32fSrvcApiQryPrmValFailAltCritical

Table 5-83 seppN32fSrvcApiQryPrmValFailAltCritical

Field Description
Trigger Condition Triggered as a critical alert in case of a failure of Cat-1 NRF service API query parameters validation feature when the rate of failure goes above 100.
Severity Critical
Alert Details Provided

Summary

namespace:{{ $labels.namespace}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }}: Service Api Query Param Validation has failed because {{ $labels.cause }}

Expression:
sum(rate(ocsepp_security_service_api_query_param_validation_failure_total{namespace="sepp-namespace"}[2m]))by(namespace,nf_instance_id,app,pod,resource_uri) > 100
OID 
1.3.6.1.4.1.323.5.3.46.1.2.4070
Metric Name ocsepp_security_service_api_query_param_validation_failure_total
Resolution The alert gets automatically cleared when the rate of failure goes down below 100.
Possible Resolutions:
  1. Verify that both the Cat-1 NRF Service API Query Parameters Validation feature and the Cat-1 Service API Validation feature are enabled. For configuration-related issues, refer to 'Cat-1 NRF Service API Query Parameters Validation Feature' section in the Oracle Communications Cloud Native Core, Security Edge Protection Proxy Troubleshooting Guide.
  2. Ensure that the same list-name is selected across all lists configured for query parameter validation.
  3. Check the pair of Network Functions and the values included in the request. Make sure they match the configuration defined for this feature.
  4. Confirm that the request is an NRF discovery request using the GET method.