5.4.1.5 OcnrfOauthNonCurrentKeyDataHealthStatus
Table 5-66 OcnrfOauthNonCurrentKeyDataHealthStatus
| Field | Details |
|---|---|
| Description | 'OCNRF Oauth Access token Non current Key Id status is not healthy' |
| Summary | 'kubernetes_namespace: {{$labels.kubernetes_namespace}},nrflevel:{{$labels.NrfLevel}}, podname: {{$labels.kubernetes_pod_name}}, KeyId: {{$labels.KeyId}}, KeyType: {{$labels.KeyType}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} OCNRF Oauth Access token non current Key Id status is not healthy.' |
| Severity | Info |
| Condition | Oauth Non Current Key details health is not good |
| OID | 1.3.6.1.4.1.323.5.3.36.1.2.7037 |
| Metric Used | ocnrf_oauth_keyData_healthStatus |
| Recommended Actions |
The alert is cleared when the current key ID status is healthy. Steps: Rectify the condition by checking ErrorCondition For example: For ErrorCondition Invalid_Key_Details, check if the k8SecretName, k8SecretNameSpace, and filename combination exists correctly for both privateKey and certificate. Make sure that the pem file data is not corrupt or the certificate has not expired. |
| Available in OCI | No |