Viewing your error logs in the panel

Overview

This article provides steps to view and understand your website's error logs in the panel.

Background

The Error Logs page contains all critical error messages related to your website. This includes server issues, script failures, or other problems the server encounters while handling a request. Reviewing this data is important as it can help you diagnose and resolve any website issues you may encounter.

Viewing the Error Logs page

To view your site's error logs:

1. Navigate to the Manage Websites page.
2. Click the Manage button to open the Domain Settings page, which allows you to adjust various settings for your site.
   • If in Grid view, click the Manage button at the bottom of the website box.
   • If in List view, click the Manage button at the far right of your domain name.
3. Click the Logs tab.

   The Error Logs page opens, displaying your site's error logs and graphs.

Analyzing the Error Logs graph

This section explains how to analyze the data in the panel.

Error Logs graph

The graph displays error log frequency over time. The lines can be filtered by severity, as described below. This helps quickly identify patterns and investigate periods of error spikes.

Log data

Logs are organized in columns showing Timestamp, Severity, and Message.

PHP warnings and deprecated notices are hidden to keep the error.log clean. They can be enabled by following this article. 

Filter Logs by Date and Time

Use the calendar option located at the top right of the graph to filter logs by date and time.

The system retains logs for up to 7 days. Grayed-out dates in the calendar indicate they are unavailable as they fall outside of this time range.

Filter Logs by Severity

Click the Severities dropdown at the top to filter logs by error severity. Selecting a checkbox automatically filters the results.

Understanding Severity levels

The following provides a brief explanation for each level of severity.

Entry	Severity	Description	Examples	Action
Critical	Very high	Indicates an issue is preventing the website from working. These errors are marked as high priority in the log file and can be caused by site issues.	Database connection failure Server crash Critical service down	Immediate intervention required.
Error	High	Indicates a runtime error that needs addressing but may not halt the entire application. It usually means a request or operation has failed.	File not found Failed API request Unhandled exceptions	Investigate and fix as soon as possible to avoid potential escalation into critical issues.
Alert	Very high	Signals a condition that needs immediate action, often triggered by monitoring systems.	Disk space running out Too many failed login attempts	Immediate attention.
Warning	Medium	Indicates a potential issue that is not currently causing failure, but might lead to problems if not addressed.	Deprecated API usage Approaching resource limits Minor configuration issues	Monitor the situation and address it to prevent it from becoming an error or critical issue.
Notice	Low	Signals normal but significant events. These messages highlight important application behavior that might not be problematic but is still worth noting.	Configuration changes Successful job completion Minor policy violations	No immediate action is needed, but it's good to review notices periodically to ensure system health.

Using the summary tool

The Error Logs page features an AI-powered summary tool. This is a simple way to analyze error logs, providing a quick impact summary, recommended actions, and possible root causes to streamline troubleshooting.

To generate a summary, click the Create Summary button below the graph. A new window opens, displaying key details such as Time, Impact, Symptoms, and Resolution.

If you have any questions or need further clarification, please Contact Support for further assistance.

See also

• The Website Logs page
• Viewing your access logs in the panel
• Viewing and examining your error log via SSH
• Viewing your access and error logs via SFTP