Drilldown: PEMetric

None (25)

counter (23) · gauage (2) · gauge (25)

None · N/A · seconds · milliseconds · bytes · Unsigned32 · Integer · Number · DisplayString · 'le', 'ccid', 'domain', 'service', 'component' · Status · Unix timestamp · Unix Time · Timestamp · time from epoch in seconds · time · Counter64 · 0/1 · Percentage · Amount · callback · intger · gauge · events · MB · Other

None (23) · 0 (4) · 1 (8) · 2 (12) · 3 (2) · ges_build_info{version="100.0.000.0000.build.69.rev.d07b89146"} 1 (2) · service_version_info{version="100.0.1000006"} 1 (8)

Aggregated health check (2) · Certain configuration values such as the location of GWS, Redis, Postgres, or ORS might be incorrect (2) · 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. (2) · Errors (19) · Health (6) · Health of the connection from GES to URS (2) · Health of the connection to ORS Redis. (2) · Health of the connection to Redis (2) · Health of the connection to the GWS Authentication Service (2) · Health of the connection to the GWS Configuration Service (2) · Health of the connection to the GWS Environment Service (2) · How many Push Notifications that GES has dispatched (2) · Incorrect client credentials are being supplied to GWS. Check that correct credentials have been made available in the secret. (2) · Indicates issues with the Nexus deployment or the connection from GES to Nexus. (2) · Latency (2) · Other (2) · Overall GES activity and usage (2) · Saturation (9) · Software version (2) · The ability of GES to create or delete the script objects (1) · The ability of GES to create or delete the script objects. (1) · The number of callbacks booked in GES (2) · The number of Click-to-Call-In requests GES has received (2) · The overall health of the GES deployment and connections (2) · There is no specific problem that this metric indicates. Check the logs for more information. (2) · 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. (2) · Traffic (21) · Typically indicates some sort of issue with the Kubernetes pod or the host (2) · {{{UsedFor}}} (14)