Drilldown: PEMetric

None (24)

counter (16) · Gauge (15) · histogram (2)

None (5) · N/A (19) · Number (3) · Unsigned32 (2)

None (15) · 0 (2) · 2 (4) · 23 (3) · 35929 (2)

{{{UsedFor}}} · Traffic · Latency · Errors · Error · Saturation · Health · Information · Health check · The number of callbacks booked in GES · Other · Overall GES activity and usage · Performance · Software version · There might be issues with the ORS deployment. GES could also be supplying an incorrect URL to ORS. Change the GES_URL environment variable to fix the latter issue. · The number of Click-to-Call-In requests GES has received · The overall health of the GES deployment and connections · There is no specific problem that this metric indicates. Check the logs for more information. · n/a · Typically indicates some sort of issue with the Kubernetes pod or the host

Other values: ; Aggregated health check CPU Usage Certain configuration values such as the location of GWS, Redis, Postgres, or ORS might be incorrect Dependent on which HTTP codes you observe. Excessive 500 codes might indicate an issue with configuration or with GES itself. Excessive 400 errors might indicate malicious behavior. Health of the connection from GES to URS Health of the connection to ORS Redis. Health of the connection to Redis Health of the connection to the GWS Authentication Service Health of the connection to the GWS Configuration Service Health of the connection to the GWS Environment Service How many Push Notifications that GES has dispatched Incorrect client credentials are being supplied to GWS. Check that correct credentials have been made available in the secret. Indicates issues with the Nexus deployment or the connection from GES to Nexus. Latency related to starting scheduled callbacks Monitoring Monitoring Filesystem usage Monitoring Healthy pods Monitoring incoming network Monitoring outgoing network Monitoring pod restarts Monitoring the CPU usage Operability The ability of GES to create or delete the script objects The ability of GES to create or delete the script objects. Useful for checking if SD is stuck or there is any deadlock Workload Workload, Error, ORS Error Workload, Operability