![]() If the network is normal, see How do I view Logtail collection errors? in Query diagnosis errors to troubleshoot the issue.Įxample /etc/init.d/ilogtaild status logfile 1 sls-zc-test release-test-same /disk2/test/normal/access.logįile_path : /disk2/test/normal/access.log If you still get this output, Configure Configure the startup parameters of Logtail as per your needs to modify the upper limit of CPU usage or the limit on concurrent sending by using network.Ĭheck whether or not the log format is consistent with the log collection configuration.Īn exception occurred when sending log data.Ĭheck the network status. true means the flag is valid, and false means the flag is disabled because of network errors or quota errors.Ĭheck if logs are generated too quickly. Whether or not the send flag of this Logstore is valid when the window ends. Whether or not the send queue is blocked when the window ends. The number of successfully sent data packets in the window. ![]() The number of discarded data packets in the window because of data exceptions or insufficient permissions. The number of data packets that failed to be sent in the window because the quota is exceeded. The number of data packets that failed to be sent in the window because of network errors. The number of unsent data packets in the current send queue when the window ends. The maximum time that data is successfully sent in the window. The minimum time that unsent data packets are in the send queue when the window ends. The maximum time that unsent data packets are in the send queue when the window ends. The average of the differences between the current offset and the file size each time logs are read in the window. The number of times that logs are read in the window. The number of log lines that failed to be parsed in the window. The number of successfully parsed log lines in the window. The collection configuration name, which is globally unique and consists of #1.0#, project, $, and config. For specific statuses, descriptions, and change methods, see the following table. etc/init.d/ilogtaild status logstore -format=json 1 sls-zc-test release-test-same To troubleshoot the issue, see How do I view Logtail collection errors?.Įxample /etc/init.d/ilogtaild status logstore 1 sls-zc-test release-test-same If you still get this output, Configure the startup parameters of Logtail as per your needs to modify the upper limit of CPU usage or the limit on concurrent sending by using network. Check if logs are generated too quickly and if the network status is normal. ![]() If you still get this output, Configure the startup parameters of Logtail as per your needs to modify the upper limit of CPU usage or the limit on concurrent sending by using network.īlocked. The number of logs being collected is large.Ĭheck if the configuration contains files that do not need to be collected.Ĭheck if logs are generated too quickly. The current collection speed is high and the Logtail status is normal. in all, it means last $(index) minutes in active/logstore/logfile/history, it means last $(index)*10 minutes Status history beginIndex endIndex project logstore Get log file status with line or json style. Status logfile index project logstore fileFullPath Get logstore status with line or json style. if use -logfile, please add project and logstore. If the logtail insight, version keyword is returned, it indicates that this function is supported on the Logtail client. To install Logtail, see Install Logtail on a Linux server.Įnter the /etc/init.d/ilogtaild -h command on the client to check if the client supports querying local log collection status. If a Logtail client supporting status query function is installed, you can query local log collection status by entering commands on the client. Determine whether or not Logtail has finished collecting log files
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |