Analyse ZCC Logs Automatically
The CentaurNexus Agent analyses ZCC logs on the endpoint. The platform receives structured, signed findings with severity, recommendations, and technical evidence.
Demo run in our live demo with sample data. Times and steps come from the run shown, not a benchmark measurement.
Chapters
- 00:06Platform and agent
- 00:23Free web tool
- 00:36Direct support context
- 00:51Findings by severity
- 01:05Open technical details
- 01:19Manual fallback
- 01:33Evidence and PAC content
- 01:47Value for support and security
Show transcript+
The Log Analyzer is built directly into CentaurNexus. Wherever the CentaurNexus Agent is installed, it automatically analyses ZCC logs on the endpoint and transfers only structured, signed findings to the platform. Raw log lines never leave the device.
For individual investigations, the Log Analyzer is also available free of charge and without registration on our website. The complete analysis runs locally in the browser.
In the normal platform workflow, diagnosis therefore no longer begins by collecting and uploading a log bundle. The help desk opens the user context and sees the latest available finding directly in the same view.
Detected issues are sorted by severity. They include tunnel and DNS problems, PAC errors, authentication, posture, certificates, and possible interference from local firewall or security software.
Every finding includes a clear explanation and a concrete recommendation for the next diagnostic step. Troubleshooting no longer begins with a manual search through tens of thousands of log lines.
If the CentaurNexus Agent is not yet installed on a device, or if an older bundle needs to be checked, ZIP, log, or text files can still be analysed manually. The analysis is not stored permanently.
For a manual analysis, the associated sample lines and detected PAC content can also be opened. The finding, recommendation, and technical evidence remain connected in one continuous workflow.
The help desk starts with a prepared finding instead of a request for files. Administration and security can continue with a structured, technically traceable analysis when needed. This shortens root-cause resolution and reduces unnecessary handovers between support levels.
This page answers
- analyse ZCC logs
- Zscaler Client Connector troubleshooting
- ZCC tunnel issue
- Zscaler log analyzer
- PAC error in ZCC log
- ZCC support diagnostics