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

# Dev Logs

> Troubleshoot agent behavior 

### **What Are Dev Logs?** 

Dev Logs are a timestamped sequence of system-level events that occur during the lifecycle of a voice/chat interaction. These logs capture each stage of the agent orchestration, starting from the initial greeting to transcription, LLM processing, voice synthesis, and call disconnection. It's built for developers and advanced users who want visibility into every stage of the agent's thinking and speaking process.  

### **Where to Find It** 

You can access Dev Logs by navigating to:
**Conversation Logs → Dev Logs**  

### **Why Use Dev Logs?** 

Dev Logs are essential when: 

* You want to debug why an agent didn't respond correctly 
* You need to analyze latency at each stage (TTS, ASR, LLM) 
* You're optimizing call performance 

### **Log Source / Module Tags** 

Each log line is prefixed by a module to indicate where it originated: 

| **Module**       | **Description**                                                                                                         |
| :--------------- | :---------------------------------------------------------------------------------------------------------------------- |
| CALL             | Tracks call lifecycle: start, disconnect                                                                                |
| ORCH             | Orchestration logic like greeting fetch, post-call actions, post-call processing                                        |
| TTS              | Text-to-speech processing, TTFB (time to first byte), latencies, audio durations                                        |
| ASR / TRANSCRIBE | Speech recognition, transcription results, audio duration and latency                                                   |
| LLM              | Large Language Model events, streaming, token usage info, language switch detection, error handling if generation fails |
| KB               | Knowledge base context retrieval and metrics                                                                            |
| BARGE            | User interruption (barge-in) detection and handling                                                                     |
| ERROR            | Error responses, especially from OpenAI or other APIs                                                                   |
| UNKNOWN          | Fallback logs for unexpected events or raw debug info                                                                   |

### **Latency Monitoring** 

Look out for high latency values in: 

* **ASR Latency** 
* **TTS Latency** 
* **LLM Generation Time** 

High values may indicate network, model, or transcription delays. These are key areas to optimize. 

### **End of Conversation Signals** 

Look out for: 

* EOC: End of Conversation 
* CALL: Disconnecting call: User hang-up or timeout 
* ORCH: Finalizing total call credits: Post-call processing 

### **Debugging Tips** 

| **Issue**                                 | **Check This Section** |
| :---------------------------------------- | :--------------------- |
| Agent responded slowly                    | TTS / LLM latency      |
| Agent misunderstood user                  | ASR final result       |
| Agent gave a wrong or incomplete response | LLM logs               |
| Response wasn’t spoken                    | TTS                    |
| Unexpected disconnect                     | CALL logs at the end   |

### **Summary** 

The Dev Logs tab is your deep-dive tool for full transparency into: 

* What your agent said 
* What the user said 
* How long each step took 
* What the model generated and why 

It’s invaluable for debugging, improving accuracy, and ensuring top performance.