1. Why Log Size Matters #
Your documentation hints at:
- Log files stored on disk.
- Each request can append entries when a channel is enabled.
If logs grow very large:
- They can take longer to open in the UI.
- They can consume more disk space on hosting.
- Reading/parsing them becomes harder.
2. Clearing a Single Channel’s Log #
- Go to Davix AI Engine → Debug Logs.
- For a specific channel (e.g., Chatbot, Forms, AI Writer):
- Click Clear log or similar action.
Behind the scenes:
- The plugin truncates or recreates that channel’s log file as empty.
- Future events are logged into a fresh file.
image IMAGE PLACEHOLDER: Screenshot of Debug Logs page showing a “Clear log” button next to a channel and a confirmation message saying “Chatbot log cleared.” IMAGE image
3. When to Clear Logs #
Good practice based on how you use the plugin:
- After fixing an issue:
- Clear relevant logs to start fresh.
- Before reproducing a specific bug:
- Clear logs first, reproduce the problem once, then read only the fresh entries.
- Periodically:
- If logs haven’t been needed for some time, clear them to free space.
4. Disabling Channels You Don’t Need #
To minimize noise and disk usage:
- Turn OFF any debug channels you’re not actively using (e.g., if AI Writer is stable, you can keep its log disabled).
- Save.
Only modules with debug enabled will write logs, so turning off channels significantly reduces log growth.
5. Impact on Site Performance #
In normal use:
- Logging adds a small overhead when channels are enabled, because each request writes to a file.
- For production sites under heavy traffic:
- Only enable channels when needed for debugging.
- Disable once a problem is resolved.
This matches your docs’ suggestion to use Debug Logs as a diagnostic tool, not something to leave fully enabled at maximum verbosity all the time.
