System Health Monitor
The VC Health Visibility page in Studio provides real-time and historical insights into how your scripts are performing against shared Virtual Contact (VC) system infrastructure. This tool gives you proactive visibility into resource stress and performance events. It reduces the need to rely on support tickets for basic troubleshooting.
On this page, you can:
- Monitor Resource Utilization: View current VC state metrics, such as memory, CPU, and voice port footprint to see how your scripts are performing relative to established patterns. This helps you see if your scripts are nearing resource limits so you can optimize them before they cause system instability.
- Review Performance Events: Access a timeline of recent anomalies, alerts, and incidents affecting your tenant, complete with AI-generated explanations in plain language. This allows you to see example when a performance dip occured so you can correlate it with specific script changes or high-traffic periods.
- Access Root Cause Analysis (RCA): View customer-facing RCA documents and remediation guidance directly in the interface. This provides durable, reusable answers to recurring issues and offers remediation guidance to prevent the problem from happening again.
- Investigate with Conversational AI: Use a natural language chat interface to ask specific questions about your script performance, such as "Why did my billing flow slow down yesterday?" Plain-language summaries translate complex technical telemetry into understandable terms and helps you to more quickly grasp the core of an issue without taking the time to dig into the log files.
Key Facts About the System Health Monitor
- Access is restricted by permissions assigned to NiCE CXone roles.
- The System Health Monitor page is read-only; you cannot initiate script actions, manage alert rules, or change infrastructure configurations from this page.
- All data and AI responses are strictly scoped to your specific tenant to ensure security and privacy.
Available System Health Data
The VC health monitor provides information about your NiCE CXone system and the cluster it resides in. The following table describes the available information.
| Data Point | Details |
|---|---|
| Cluster and Tenant Summary |
The top of the VC Health Monitor page provides a summary of your system:
|
|
Concurrent Scripts |
The number of scripts currently running in your tenant and the maximum number for your tenant. The percentage of the maximum number of scripts that are currently running. For example, if your system is running 180 out of 5000 scripts, the page shows you're using 37% of your total number of concurrent scripts. time graphs? |
| Blocking Threads | The number of active blocking threads running in your tenant. |
| Memory Breaches | The number of memory breaches. A memory breach occurs when a script exceeds its memory threshold. |
| In-Memory Consumption | Lists scripts and |
AI-Powered Diagnostics
The VC Health Monitor page has a conversational AI tool that helps you investigate specific issues. You can prompt it with questions, such as "Why did my billing flow slow down yesterday?" The tool returns diagnostic information with your prompt as the context. The following table describes the data it may return:
| Diagnostic Data | Description |
|---|---|
| Tenant-Scroped Telemetry | Historical data points (CPU, memory, execution time) filtered strictly to your specific business unit and the time range requested. |
|
Anomaly Signals |
Identification of out-of-pattern behavior where script performance deviated from its established baseline. |
| Remediation Guidance | Actionable steps or script optimizations suggested by the AI to resolve the identified performance bottleneck. |
| Knowledge Base Grounding | Contextual information pulled from internal documentation to ensure the AI's diagnosis is based on known best practices and system limits. |