If the log collection fails or the collection status is abnormal when you use Logtail, follow these steps to troubleshoot the errors.


  1. Check whether the Logtail heartbeat in the machine group is normal
    Log on to the Log Service console and click Machine Status to view the status of the machine group.  For more information, see Manage a machine group. If the heartbeat status is normal, move to the next step. 

    If the heartbeat status is fail, see Logtail heartbeat error for troubleshooting.

  2. Check whether the collection configuration is created and applied to the machine group
    After you confirm that the Logtail client status is normal, check the following configurations. 
    1. Check whether Logtail configuration is created
      For more information, see Logtail configuration.  Make sure that the log monitoring directory and the log file name match with the files on the machine. The directory does not support fuzzy match and must be set to an absolute path, while the log file name supports fuzzy match.
    2. Check whether Logtail configuration is applied to the machine group
      See Manage configurations in Manage a machine group. Check if the target configuration is applied to the machine group.
  3. Check for collection errors
    If Logtail is properly configured, check whether new data is generated in real time in the log file.  Logtail collects incremental data only, it does not read inventory files if the files are not updated.  If the log file is updated but the updates cannot be queried in Log Service, diagnose the problem in the following ways:
    • Diagnose collection errors

      See Diagnose collection errors to handle the errors according to the error type reported by Logtail.

    • View Logtail logs

      Client logs include key INFO logs and all the WARNING and ERROR logs.  To see complete and real-time errors, view the client logs in the following paths:

      • Linux: /usr/local/ilogtail/ilogtail.LOG
      • Linux: /usr/local/ilogtail/logtail_plugin.LOG (logs of input  sources such as HTTP, MySQL binlog, and MySQL query results)
      • Windows x64: C:\Program Files Program Files (x86)\Alibaba\Logtail\logtail_*.log
      • Windows x32:  C:\Program Files\Alibaba\Logtail\logtail_*.log
    • Usage exceeds the limit

    If the problem persists, open a ticket to contact Log Service engineers and attach the key information collected during troubleshooting to the ticket.