Drilldown: PEMetric
Use the filters below to narrow your results.
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 (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) ·
n/a (2) ·
Operability (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) ·
Workload (2) ·
Workload, Error, ORS Error (2) ·
Workload, Operability (2) ·
{{{UsedFor}}} (14)
Showing below up to 27 results in range #1 to #27.
View (previous 250 | next 250) (20 | 50 | 100 | 250 | 500)
D
- Draft:IXN/Current/IXNPEGuide/Interaction Server metrics
- Draft:PEC-CAB/Current/CABPEGuide/CallbackMetrics
- Draft:PrivateEdition/Current/TenantPEGuide/VoiceTenantServiceMetrics
- Draft:VM/Current/VMPEGuide/VoiceAgentStateServiceMetrics
- Draft:VM/Current/VMPEGuide/VoiceCallStateServiceMetrics
- Draft:VM/Current/VMPEGuide/VoiceConfigServiceMetrics
- Draft:VM/Current/VMPEGuide/VoiceDialPlanServiceMetrics
- Draft:VM/Current/VMPEGuide/VoiceFrontEndServiceMetrics
- Draft:VM/Current/VMPEGuide/VoiceOrchestrationServiceMetrics
D cont.
- Draft:VM/Current/VMPEGuide/VoiceRegistrarServiceMetrics
- Draft:VM/Current/VMPEGuide/VoiceRQServiceMetrics
- Draft:VM/Current/VMPEGuide/VoiceSIPClusterServiceMetrics
- Draft:VM/Current/VMPEGuide/VoiceSIPProxyServiceMetrics
- Draft:VM/Current/VMPEGuide/VoiceVoicemailServiceMetrics
I
P
- PEC-CAB/Current/CABPEGuide/CallbackMetrics
- PrivateEdition/Current/TenantPEGuide/VoiceTenantServiceMetrics
V
V cont.
- VM/Current/VMPEGuide/VoiceCallStateServiceMetrics
- VM/Current/VMPEGuide/VoiceConfigServiceMetrics
- VM/Current/VMPEGuide/VoiceDialPlanServiceMetrics
- VM/Current/VMPEGuide/VoiceFrontEndServiceMetrics
- VM/Current/VMPEGuide/VoiceOrchestrationServiceMetrics
- VM/Current/VMPEGuide/VoiceRegistrarServiceMetrics
- VM/Current/VMPEGuide/VoiceSIPClusterServiceMetrics
- VM/Current/VMPEGuide/VoiceSIPProxyServiceMetrics
- VM/Current/VMPEGuide/VoiceVoicemailServiceMetrics