AI Diagnostics and Log Analysis
Use local log analysis to locate traffic and errors, then send sanitized context to third-party AI as needed.
Local Log Analysis
Log analysis reads up to 7 days and 512MB of data, covering current logs and already rotated compressed logs. The report shows request volume, status codes, common paths, IPs, crawlers, blocks, and security events.
High-frequency IPs and high-frequency paths are two separate rankings, so you cannot directly infer that a specific IP accessed a specific path. Only the specific log samples in the details can establish such a correspondence. Seeing "Truncated" indicates that only part of the data was analyzed this time.
AI Deep Diagnosis
AI provider, API key, connection test, and other settings are located in the settings popup at the top-right corner of the AI Diagnostics page. You can configure and diagnose on the same page, and upgrades will not clear saved settings.
AI diagnostics only provide suggestions and do not automatically execute Shell, SQL, or modify the server. Both regular website diagnostics and in-depth log diagnostics use the same sensitive information protection rules.
Before sending, passwords, tokens, cookies, API keys, and absolute website paths are cleaned, and the real IP is temporarily replaced with a session-specific alias. After the results are returned, the real IP is only restored locally on the panel.
Understanding Reports Correctly
- Historical 5xx errors do not mean the website is still down; you should check with immediate access.
- 444 indicates that the request has been blocked and should not be repeatedly described as an unhandled risk.
- Fake, unknown, or unverified crawler identities alone cannot be used as a basis for permanent bans.
- AI suggestions must be verified against the actual panel entry points, current configuration, and latest logs before execution.
