Networking alerts

kubernetes-system-apiserver

RKE2CertificateExpiry7Days

This alert indicates that the server TLS certificate expires in the following 7 days.

To fix this issue, update the TLS certificate. For instructions, see Managing the certificates.

RKE2CertificateExpiry90Days

This alert has different severity levels and messages based on the number of remaining days:

• Warning Severity alert

  Message: RKE2 certificates are going to expire in 89 days! To renew, restart RKE.

• Warning Severity alert

  Message: RKE2 certificates are going to expire in 29 days! To renew, restart RKE.

• Critical Severity alert

  Message: RKE2 certificates are going to expire in 7 days! To renew, restart RKE.

RKE2CACertificateExpiry60Days

Warning Severity alert

Message: RKE2 CA certificates are going to expire in 59 days!

RKE2CACertificateExpiry30Days

Critical Severity alert

Message: RKE2 CA certificates are going to expire in 29 days!

RKE2CACertificateExpiry15Days

This alert indicates that the server TLS certificate expires in the following 15 days.

To fix this issue, update the TLS certificate. For instructions, see Managing server certificates.

uipath.cronjob.alerts.rules

IdentityKerberosTgtUpdateFailed

This job updates the latest Kerberos ticket to all the UiPath® services. Failures in this job would cause SQL server authentication to fail.

To fix this issue, check the logs:

kubectl -n uipath logs job/kerberos-tgt-update

If the issue persists, please contact UiPath® Support.

IdentityCertificateExpiry30Days

This alert indicates that the Identity token signing certificate will expire in the following 30 days.

To fix this issue, update the Identity token signing certificate. For instructions, see Managing server certificates.

IdentityCertificateExpiry7Days

This alert indicates that the Identity token signing certificate will expire in the following 7 days.

To fix this issue, update the Identity token signing certificate. For instructions, see Managing server certificates.

UiPathAvailabilityHighTrafficBackend, UiPathAvailabilityMediumTrafficUserFacing, UiPathAvailabilityMediumTrafficBackend, UiPathAvailabilityLowTrafficUserFacing, UiPathAvailabilityLowTrafficBackend

The number of http 500 responses from UiPath® services exceeds a given threshold.

Traffic level	Number of requests in 20 minutes	Error threshold (for http 500s)
High	>100,000	0.1%
Medium	Between 10,000 and 100,000	1%
Low	< 10,000	5%

Errors in user-facing services would likely result in degraded functionality that is directly observable in the Automation Suite UI, while errors in backend services would have less obvious consequences.

The alert indicates which service is experiencing a high error rate. To understand what cascading issues there may be from other services that the reporting service depends on, you can use the Istio Workload dashboard, which shows errors between services.

Please double check any recently reconfigured Automation Suite products. Detailed logs are also available with the kubectl logs command. If the error persists, please contact UiPath® Support.

certs

SecretCertificateExpiry30Days

This alert indicates that the server TLS certificate will expire in the following 30 days.

To fix this issue, update the server TLS certificate. For instructions, see Managing server certificates.

SecretCertificateExpiry7Days

This alert indicates that the server TLS certificate will expire in the following 7 days.

To fix this issue, update the TLS certificate. For instructions, see Managing server certificates.

uipath.requestrouting.alerts

UiPathRequestRouting

Errors in the request routing layer would result in degraded functionality that is directly observable in the Automation Suite UI. The requests will not be routed to backend services.

You can find detailed error log of request routing in istio-ingressgateway pods in istio-system namespace. Retrieve the pod name by running the following commands:

kubectl get pods -n istio-system
kubectl logs <istio-ingressgateway-pod-name> -n istio-system

If the error persists, contact UiPath® Support.

InternodeCommunicationBroken

The node has become unresponsive due to some issue causing broken communication between nodes in the cluster.

To fix this problem, take the following steps:

1. Make sure that you implemented the settings mentioned in Step 8: Configuring kernel and OS level settings.

2. If applicable, make sure you implemeneted the changes mentioned in

   How to disable TX checksum offloading.

3. If the previous steps did not solve the issue, reach out to UiPath® Support with the generated support bundle.