5.4.1.1 OcnrfAccessTokenCurrentKeyIdNotConfigured
Table 5-62 OcnrfAccessTokenCurrentKeyIdNotConfigured
| Field | Details |
|---|---|
| Description | 'AccessToken request(s) have been rejected by OCNRF (current value is: {{ $value }})' |
| Summary | 'kubernetes_namespace: {{$labels.kubernetes_namespace}},nrflevel:{{$labels.NrfLevel}}, podname: {{$labels.kubernetes_pod_name}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} AccessToken Request has been rejected by OCNRF as Current Key Id is not configured.' |
| Severity | Critical |
| Condition | NRF Access Token Rejected due to CurrentKeyId not configured |
| OID | 1.3.6.1.4.1.323.5.3.36.1.2.7033 |
| Metric Used | 'ocnrf_accessToken_tx_responses_total' |
| Recommended Actions | The alert is automatically cleared as it is raised when
NRF receives Access Token Request, and at that point, Current Key Id is
not selected. For more information about configuring
currentKeyID parameter, see Oracle Communications Cloud Native Core, Network Repository Function REST
Specification Guide.
|
| Available in OCI | No |