Turn raw Amazon Connect CCP logs into structured, searchable diagnostics. Extract API latency metrics, agent state snapshots, skew data, and pinpoint errors with intelligent remediation hints.
API latency & skew metrics per endpointAgent state snapshots with contact detailsFilter by level, keyword, or regexSmart error intelligence with fix tipsTimeline chart of log volume over time
// LOG SUMMARY
CCP Log Input
Drop CCP log file here
Accepts .log .txt .json — parsed entirely in your browser
or paste log text
Samples:
Event Timeline
Log entries per minute
Log Level Distribution
Top Sources
Source / Module
Count
Errors
Volume
API Request Latency
API Endpoint
Calls
Avg Latency
Min
Max
P95
Status
Clock Skew
RTC / Media Events
Event
Count
Last seen
Timestamp
Level
Source
Message
Understanding Amazon Connect CCP Logs
The Amazon Connect Contact Control Panel (CCP) is the softphone interface agents use to handle calls, chats, and tasks. When troubleshooting call quality issues, connectivity problems, or agent state discrepancies, CCP logs are the primary diagnostic source. Logs record every API call, WebRTC state change, agent snapshot, error, and timing metric with millisecond precision.
Where do I find Amazon Connect CCP logs?
In the CCP, click the settings gear → "Download logs" (or Ctrl+Shift+Alt+L). Logs are downloaded as a .log text file. You can also access them via the browser console by searching for the connect-log object, or programmatically via the Streams API using connect.getLog().download().
What does "skew" mean in CCP logs?
Skew is the time difference between the agent's local clock and the Amazon Connect server clock. A large skew (e.g., ±500ms+) indicates the agent's workstation clock is out of sync, which can cause authentication issues, timestamp confusion in contact records, and API signature validation failures. Skew should ideally be under 100ms.
What causes high API latency in CCP logs?
High API latency (over 1000ms) in CCP logs is typically caused by: slow network between the agent workstation and AWS region, VPN routing adding hops, DNS resolution delays, overloaded corporate proxy servers, or the agent being connected to a non-optimal AWS region. GetCurrentContactState and GetCurrentMetricData are the most latency-sensitive endpoints.
What do ICE/RTC errors in CCP logs mean?
ICE (Interactive Connectivity Establishment) errors indicate WebRTC media path failures. "ICE failed" means no media path was negotiated — usually a firewall blocking UDP ports 3478 or 49152-65535. "ICE disconnected" is a transient state that often recovers. "ICE checking" that never resolves indicates STUN/TURN unreachability. One-way audio is almost always an ICE failure.
What is the CCP Streams API and how do logs relate to it?
The Amazon Connect Streams API is a JavaScript library that lets you embed and extend the CCP in custom applications. Logs generated by the Streams API use the [StreamsManager], [AgentWorkerApi], and [ContactController] sources. Streams API errors often indicate initialization failures, authentication issues, or iframe embedding problems.
How do I interpret agent state snapshots in CCP logs?
Snapshots are periodic JSON dumps of complete agent state — routing profile, contacts in queue, current status, ACW (After Call Work) timer, and skill assignments. They appear as large JSON blobs in log lines with source "Snapshot" or "WorkerPollingService". Comparing successive snapshots helps identify when state changes occurred and whether they were expected.
