> ## Documentation Index
> Fetch the complete documentation index at: https://docs.operata.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Tools and logs

> When the dashboards aren't enough, Operata gives you the raw logs and a set of diagnostic tools. Here's what's available and when to reach for each.

Dashboards tell you what happened. Logs tell you why. When an error count or an insight points at a problem you can't explain from a chart, pull the logs for that agent and that contact.

## When to use logs

* A dashboard shows an error you don't recognize.
* One agent behaves differently from everyone else on the same network and device.
* Operata is missing data you expected, and you need to prove where collection stopped.

## Getting logs out of Operata

Open [Calls and logs](/docs/help/calls-and-logs), filter to the agent and time range you need, and download. Use the absolute time filter — it runs on the UTC clock, which matters when you're lining logs up against platform-side timestamps.

Downloads are capped, so narrow the time range rather than widening it.

## Platform specifics

Log formats, and the tools that read them, are platform-specific.

* [Amazon Connect: CCP log parser](/docs/help/amazon-connect-log-parser) — load a downloaded CCP (Contact Control Panel) log file into a browser-based viewer.
* [Amazon Connect: capture WebRTC diagnostics](/docs/help/dump-function-amazon-connect) — dump the live WebRTC session from the agent's browser console when Operata is missing collection data.

## Related

* [Softphone issues](/docs/diagnose-softphone-issues) — what the errors in those logs mean.
* [Get help and report issues](/docs/help/getting-help-and-reporting-issues) — what to send Operata support.
* [Check service status](/docs/help/checking-operata-service-status-and-reporting-platform-issues) — rule out a platform incident before you dig.