1. What the Debug Log Viewer Does #
From your docs and earlier sections, the Debug Logs module is a centralized log viewer built into Davix AI Engine. It:
- Collects diagnostic messages from all main modules:
- Chatbot / Theming & OpenAI
- Telegram human handoff
- Forms (entries, AI, email, Telegram)
- Comment & Review auto-replies
- AI Writer (Gutenberg sidebar)
- LLM Index
- Lets you enable/disable channels so you only log what you need.
- Stores logs in plain text files in the plugin’s log directory.
- Provides a simple UI to view and clear logs inside WordPress.
image IMAGE PLACEHOLDER: Screenshot of Davix AI Engine → Debug Logs page showing toggles per module and “View log” / “Clear log” buttons. IMAGE image
2. Where to Find Debug Logs in WordPress #
In wp-admin:
- Go to Davix AI Engine → Debug Logs.
On this screen you’ll see:
- A list of log channels (Chatbot, Forms, Auto-Reply, AI Writer, Telegram, LLM Index, Global).
- For each channel:
- An enable/disable toggle.
- A View log button.
- A Clear log button (or similar action).
- Sometimes general options like:
- Max log size.
- Log level (if your docs mention it).
- A short explanation of what each channel logs.
3. How Modules Use Debug Logs #
Each module you’ve documented references Debug Logs as the place to investigate issues:
- Chatbot / Telegram
- We already mentioned “use Debug Logs to inspect Telegram or chat errors” when messages don’t arrive.
- Forms module
- Debug logs for:
- Entry capture.
- AI reply generation.
- Email sending.
- Telegram alerts.
- Debug logs for:
- Comment & Review Auto-reply
- Logs AI reply generation and Telegram notifications.
- AI Writer
- Logs REST calls, OpenAI errors, and insertion problems when
debug_aiwriter_enabledis on.
- Logs REST calls, OpenAI errors, and insertion problems when
- LLM Index
- If there is a dedicated channel, it logs index generation, endpoint access, and configuration problems.
All of these modules write to Debug Logs only when their respective log channel is enabled, to avoid unnecessary noise.
