Drilldown: PEMetric

Jump to: navigation, search

Choose a table:


PEMetric > Unit : N/A or Status or None

Use the filters below to narrow your results.

IncludedServiceId:
None (77) · c39fe496-c79e-4846-b451-1bc8bedb126b (2)
Type:
Constant (2) · Counter (59) · gauage (2) · Gauge (70) · Guage (2) · histogram (32) · Integer (2) · Number (2) · summary (7)
Unit: (Click arrow to add another value)
SampleValue:
None (46) · 0 (27) · 2 (25) · 1 (25) · 42 (14) · 4.2 (14) · [1, 2, 3] (14) · service_version_info{version="100.0.1000006"} 1 (10) · 100 (10) · 10 (7) · 1000 (6) · 3 (5) · 5 (5)
Other values:
UsedFor:
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) · Error (18) · Errors (19) · Health (6) · Health check (4) · 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 (17) · Monitoring (2) · Operability (2) · Other (2) · Overall GES activity and usage (2) · Performance (2) · Saturation (15) · 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 (29) · Typically indicates some sort of issue with the Kubernetes pod or the host (2) · {{{UsedFor}}} (48)

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

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

A

D

D cont.

G

I

P

P cont.

S

U

V

W


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

Retrieved from "https://all.docs.genesys.com/Special:Drilldown/PEMetric (2024-07-17 11:37:16)"