From Genesys Documentation
Jump to: navigation, search
(Published)
 
(Published)
 
Line 6: Line 6:
 
|Endpoint=/metrics
 
|Endpoint=/metrics
 
|MetricsUpdateInterval=15 seconds
 
|MetricsUpdateInterval=15 seconds
 +
|MetricsDefined=Yes
 
|PEMetric={{PEMetric
 
|PEMetric={{PEMetric
 
|Metric=cxc_lb_jobs_running_total
 
|Metric=cxc_lb_jobs_running_total
Line 74: Line 75:
 
}}
 
}}
 
|AlertsDefined=Yes
 
|AlertsDefined=Yes
 +
|PEAlert={{PEAlert
 +
|Alert=CXC-LB-LatencyHigh
 +
|Severity=HIGH
 +
|AlertDescription=Triggered when the latency for list builder is above the defined threshold.
 +
|Threshold=5000ms for 5m
 +
}}{{PEAlert
 +
|Alert=CXC-CPUUsage
 +
|Severity=HIGH
 +
|AlertDescription=Triggered when the CPU utilization of a pod is beyond the threshold
 +
|Threshold=300% for 5m
 +
}}{{PEAlert
 +
|Alert=CXC-MemoryUsage
 +
|Severity=HIGH
 +
|AlertDescription=Triggered when the memory utilization of a pod is beyond the threshold.
 +
|Threshold=70% for 5m
 +
}}{{PEAlert
 +
|Alert=CXC-PodNotReadyCount
 +
|Severity=HIGH
 +
|AlertDescription=Triggered when the number of pods ready for a CX Contact deployment is less than or equal to the threshold.
 +
|Threshold=1 for 5m
 +
}}{{PEAlert
 +
|Alert=CXC-PodRestartsCount
 +
|Severity=HIGH
 +
|AlertDescription=Triggered when the restart count for a pod is beyond the threshold.
 +
|Threshold=1 for 5m
 +
}}{{PEAlert
 +
|Alert=CXC-MemoryUsagePD
 +
|Severity=HIGH
 +
|AlertDescription=Triggered when the memory usage of a pod is above the critical threshold.
 +
|Threshold=90% for 5m
 +
}}{{PEAlert
 +
|Alert=CXC-PodRestartsCountPD
 +
|Severity=HIGH
 +
|AlertDescription=Triggered when the restart count is beyond the critical threshold.
 +
|Threshold=5 for 5m
 +
}}{{PEAlert
 +
|Alert=CXC-PodsNotReadyPD
 +
|Severity=HIGH
 +
|AlertDescription=Triggered when there are no pods ready for CX Contact deployment.
 +
|Threshold=0 for 1m
 +
}}
 
}}
 
}}

Latest revision as of 14:22, February 7, 2022

Difference between revisions of "PEC-OU/Current/CXCPEGuide/LBMetrics"

Find the metrics LB exposes and the alerts defined for LB.

Related documentation:
Service CRD or annotations? Port Endpoint/Selector Metrics update interval
List Builder ServiceMonitor 3104 /metrics 15 seconds

See details about:

Metrics[edit source]

Metric and description Metric details Indicator of
cxc_lb_jobs_running_total

Number of currently active jobs.

Unit:

Type: Counter
Label: "'type', 'ccid', 'tenant_name'"
Sample value: [1, 2, 3]

cxc_lb_contacts_imported_total

Total contacts imported.

Unit:

Type: Counter
Label: "'ccid', 'tenant_name'"
Sample value: 42

cxc_lb_devices_imported_total

Total device imported.

Unit:

Type: Counter
Label: "'ccid', 'tenant_name'"
Sample value: 42

cxc_lb_rejected_contact_lines_total

Total of rejected lines in input contact list files.

Unit:

Type: Counter
Label: "'ccid', 'tenant_name'"
Sample value: 42

cxc_lb_healthy_instance

Healthy instance.

Unit:

Type: Gauge
Label: n/a
Sample value: 4.2

cxc_lb_request_count

Total requests by verb and code.

Unit:

Type: Counter
Label: "'method', 'path', 'code'"
Sample value: 42

cxc_lb_request_latencies_ms

Request latencies histogram by verb, in milliseconds.

Unit:

Type: Histogram
Label: "'method', 'path', 'code'"
Sample value: [1, 2, 3]

cxc_lb_job_count

Total jobs.

Unit:

Type: Counter
Label: "'type', 'result', 'ccid', 'tenant_name'"
Sample value: 42

cxc_lb_job_duration_seconds

Jobs duration histogram in seconds

Unit:

Type: Histogram
Label: "'type', 'ccid', 'tenant_name'"
Sample value: [1, 2, 3]

cxc_lb_request_out_count

Total out requests by verb, destination, and code.

Unit:

Type: Counter
Label: "'method', 'destination', 'code'"
Sample value: 42

cxc_lb_request_out_latencies_ms

Out Request latencies histogram by verb, destination, and code, in milliseconds.

Unit:

Type: Histogram
Label: "'method', 'destination', 'code'"
Sample value: [1, 2, 3]

Alerts[edit source]

The following alerts are defined for List Builder.

Alert Severity Description Based on Threshold
CXC-LB-LatencyHigh HIGH Triggered when the latency for list builder is above the defined threshold. 5000ms for 5m


CXC-CPUUsage HIGH Triggered when the CPU utilization of a pod is beyond the threshold 300% for 5m


CXC-MemoryUsage HIGH Triggered when the memory utilization of a pod is beyond the threshold. 70% for 5m


CXC-PodNotReadyCount HIGH Triggered when the number of pods ready for a CX Contact deployment is less than or equal to the threshold. 1 for 5m


CXC-PodRestartsCount HIGH Triggered when the restart count for a pod is beyond the threshold. 1 for 5m


CXC-MemoryUsagePD HIGH Triggered when the memory usage of a pod is above the critical threshold. 90% for 5m


CXC-PodRestartsCountPD HIGH Triggered when the restart count is beyond the critical threshold. 5 for 5m


CXC-PodsNotReadyPD HIGH Triggered when there are no pods ready for CX Contact deployment. 0 for 1m
Comments or questions about this documentation? Contact us for support!