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.	Increase the upload limit for this log type. 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.	Provide a valid file path. 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.	If the log lines are correct, reconfigure your pattern. If the configured log pattern is correct but the log files are wrong, then configure a proper log file for the log profile(s).  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.	If the monitor experiences temporary downtime, logs will be collected again once the monitor is up.  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. For Windows, you can find the agent logs in the following folder path: C:\Program Files (x86)\Site24x7\WinAgent\monitoring\logs  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

• Synthetic browser module prerequisite and troubleshooting guide for On-Premise Pollers

  Introduction This document provides a structured troubleshooting guide for resolving issues encountered during the download process of On-Premise Poller for Synthetic (Browser) Module. It covers possible statuses, check-up steps, remedies, and ...

• How to set up alerts for network device data collection issues

  When your network monitoring interfaces are not collecting data due to issues in the Network Module, you'll want to be alerted. To set up alerts, you need to add or edit the threshold and availability profile of the On-Premise Poller, which is used ...

• 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 ...

• How to retrieve logs from different Site24x7 monitors

  The log location varies with different agents and monitors. View a consolidated list here: Site24x7 Server Monitoring agent Monitor or module OS Directory, path, or command Detailed reference Server Monitoring Agent Windows Installation directory > ...

• What are the common OAuth errors and how to solve them?

  While configuring OAuth,  here are a few errors that you might face. They are: Invalid Redirect URI - Error_invalid_redirect_uri Invalid Code - invalid_code OAuth Scope associated to the OAuth Access Token is disallowed. - error_code: 1120 Invalid ...