Drilldown: PEAlert

Jump to: navigation, search

Choose a table:


PEAlert > Severity: HIGH & Threshold: <2

Use the filters below to narrow your results.

Severity: (Click arrow to add another value)
AlertDescription:
A Genesys Authentication pod has CPU usage above 300% during the last 5 minutes.
(2) · A Genesys Authentication pod has memory usage above 70% in the last 5 minutes.
(2) · A Genesys Authentication pod has restarted 1 or more times during the last 5 minutes. (2) · All the MCP ports in MCP LRG are exceeded (2) · Genesys Authentication has 1 pod ready in the last 5 minutes. (2) · Genesys Authentication received more than 10 errors in the last 30 seconds during context initialization. A spike might indicate a network or configuration problem. Check the logs for details. (2) · Genesys Authentication received more than 20 SAML errors for the contact center ID in the last 60 seconds. (2) · Genesys Authentication received more than 20 SAML timing errors for the contact center ID in the last 60 seconds. (2) · Genesys Authentication received more than 3 errors in PSDK connections in the last 30 seconds. A spike might indicate a problem with the backend or a network issue. Check the logs for details. (2) · There are errors creating a JWT token with a websocket client (2) · There are errors fetching Auth token with a websocket client (2) · There are errors getting information for Auth token with a websocket client (2) · There are errors opening a session with a websocket client (2) · There are protocol errors with a websocket client (2) · Triggered when average CPU usage is more than 60% (2) · Triggered when average memory usage is more than 60% (2) · Triggered when GSP encounters unknown person(s) (2) · Triggered when network traffic exceeds 10MB/second for 5 minutes (2) · Triggered when pod database connections number is above 75. (2) · Triggered when the connection to redis fails for more than 1 minute. (4) · Triggered when the number of healthy pods drops to critical level (2) · Triggered when the number of HTTP errors exceeds 500 responses in 5 minutes (2) · Triggered when the number of pods ready for a CX Contact deployment is less than or equal to the threshold. (14) · Triggered when the restart count for a pod is beyond the threshold. (14) · Triggered when there are no pods ready for CX Contact deployment. (14) · Triggered when there are too many error responses from the auth service (list manager) for more than the specified time threshold. (2) · Triggered when there are too many error responses from the auth service for more than the specified time threshold. (2) · Triggered when there is no connection to the GAuth service (2)
Threshold: (Click arrow to add another value)

Showing below up to 26 results in range #1 to #26.

View (previous 250 | next 250) (20 | 50 | 100 | 250 | 500)


View (previous 250 | next 250) (20 | 50 | 100 | 250 | 500)

Retrieved from "https://all.docs.genesys.com/Special:Drilldown/PEAlert (2024-05-05 14:59:03)"