Troubleshooting tips for log collection errors

Troubleshooting tips for log collection errors

The following is a list of possible log collection errors and the solutions to fix them:

Error message
Reason
Solution
Upload Limit Reached
You might have reached the maximum upload limit configured for this log type in the current billing cycle.

  1. Increase the upload limit for this log type.
  2. To do this, navigate to Site24x7, then go to Admin > AppLogs > Log Type, and select the desired log type. From there, you can adjust the Maximum Upload Limit (in GB) on the Edit Log Type page.
Files Not Found
Your log files don't match those in the directory provided in the log profile.

  1. Provide a valid file path.
  2. For a static file path such as /var/log/tomcat/localhost.2024-04-29.log or /var/log/tomcat/localhost.2024-04-30.log, where a date field such as '2024-04-29' or '2024-04-30' is appended to the file name, the log profile path should be specified as /var/log/tomcat/localhost.*.log.
Recent Files Not Found
Our agent is only able to collect logs from the files that were modified within the last 24 hours. 
This informational message indicates that we have collected the latest logs and no additional logs are available for collection.
Empty File
You might have configured an empty log file.
Provide a valid file.
Log Pattern Mismatch
The configured log pattern might not match the file content.

  1. If the log lines are correct, reconfigure your pattern.
  2. If the configured log pattern is correct but the log files are wrong, then configure a proper log file for the log profile(s). 
  3. If you need assistance in log pattern configuration, reach out to support@site24x7.com.
Permission Denied
The agent doesn't have read permission for the configured log files.
Provide read permission to the configured log files.
Monitor is down
If the "Monitor is down," there will be no communication with the agent, and no logs will be collected.

  1. If the monitor experiences temporary downtime, logs will be collected again once the monitor is up. 
  2. If the monitor is down permanently,  users can remove the monitor from the log profile.To do this, navigate to Site24x7, then go to Admin > AppLogs > Log Profile, and select the desired log profile. In the Edit Log Profile page,  deselect the monitor from the "Associate this log profile with these servers" drop-down.
No status

If you are encountering errors without a specified reason, send the agent logs of the server to support@site24x7.com for further analysis.
  1. For Windows, you can find the agent logs in the following folder path: C:\Program Files (x86)\Site24x7\WinAgent\monitoring\logs 
  2. For Linux, the logs can be found in /opt/site24x7/monagent/logs

If you encounter a log collection error with Windows Event Logs, refer to this document for troubleshooting steps.
You can set up notifications to alert you if log collection stops for any of the configured log types on your account servers. Refer to this document for more information.
If you need further assistance in solving log collection errors, please reach out to support@site24x7.com.

    • Related Articles

    • Site24x7 Real User Monitoring (RUM) - Data Collection

      When you include Site24x7 RUM beacon script in your web pages, the following data is collected. All data that's being collected is in accordance with GDPR compliance. Performance details of web page load time - Metrics like response time of web page ...
    • Troubleshooting false positive alerts in monitoring

      Problem False positive alerts are being generated. Possible cause The monitoring system is down in some locations. The Website monitor might be configured for one location, such as Seattle, but may appear down when accessed from another location, ...
    • Troubleshoot the "pymysql module not found" error when installing the MySQL plugin

      If you're encountering the pymysql module not found error, it likely means that the pymysql Python library is not installed on the server. pymysql is a Python package that provides a way to interact with MySQL databases using Python code and is used ...
    • Troubleshoot the Unauthorized user (Error 401) when installing Tomcat plugins

      When installing Tomcat plugins, you may encounter the following error: Unauthorized user. Does not have permissions. HTTP Error 401: This error usually occurs when the user accessing the Tomcat Manager application does not have the necessary ...
    • Troubleshoot the Error 404 and Error 99 for RabbitMQ

      When installing the RabbitMQ plugin, you may encounter the following errors: HTTP Error 404: Not Found: This error usually occurs when Site24x7's RabbitMQ monitoring plugin attempts to access the /api/overview page of RabbitMQ, but the resource ...