Then, configure data collection by following the steps that you perform to collect Kubernetes stdout and stderr. On this tab, click Docker Standard Output - Container. If you want to collect Docker stdout and stderr, perform the following steps: In the Import Data section, click the On-premises Open Source/Commercial Software tab. For more information, see Logtail plug-ins. For example, you can add data processing plug-ins to extract fields, extract log time, desensitize data, and filter logs. If the fixed collection modes cannot meet your requirements to parse logs, you can turn on Enable Plug-in Processing in the Logtail configuration and add Logtail plug-ins. For more information about collection modes, see Collection modes. If you want to collect JSON logs, you can select JSON Mode. For example, if you want to collect multi-line logs, you can select Simple Mode - Multi-line or Full Regex Mode. Logtail parses logs based on the collection mode that you select. When you collect Docker text logs, you must select a collection mode based on your business requirements, such as Simple Mode, Simple Mode - Multi-line, Full Regex Mode, JSON Mode, Delimiter Mode, and NGINX Mode. For more information, see Use the Simple Log Service console to collect container text logs in DaemonSet mode. Then, configure data collection by following the steps that you perform to collect Kubernetes text logs. On this tab, click Docker File - Container. If you want to collect Docker text logs, perform the following steps: In the Import Data section, click the On-premises Open Source/Commercial Software tab. Then, you must enter a valid UUID in the file, for example, 169E98C9-ABC0-4A92-B1D2-AA6239C0D261, and mount the file on the /sys/class/dmi/id/product_uuid directory of the Logtail container.Ĭreate a Logtail configuration in the Simple Log Service console based on your business requirements. If the The parameter is invalid : uuid=none error is returned in the /usr/local/ilogtail/ilogtail.LOG log file, you must create a file named product_uuid on the host. The root directory of the host is mounted on the /logtail_host directory of the Logtail container. The /var/run directory of the host is mounted on the /var/run directory of the Logtail container. The following environment variables are configured: ALIYUN_LOGTAIL_USER_DEFINED_ID, ALIYUN_LOGTAIL_USER_ID, and ALIYUN_LOGTAIL_CONFIG. You can customize the startup parameters of the Logtail container only if the following conditions are met: The custom identifier of your machine group. For more information, see Obtain the ID of the Alibaba Cloud account for which Simple Log Service is activated. The ID of the Alibaba Cloud account for which Simple Log Service is activated. For example, if your project resides in the China (Hangzhou) region, set the parameter to cn-hangzhou. If your project uses an Alibaba Cloud internal network, specify the value in the region format. For example, if your project resides in the China (Hangzhou) region, set the parameter to cn-hangzhou-internet. If your project uses the Internet, specify the value in the region-internet format. For more information about network types, see Select a network type. For more information about regions, see Region names for Logtail installation. The ID of the region where your project resides and the type of the network that your project uses. For more information, see Docker run reference. For more information, see Bug 1468249, Bug 1441737, and Issue 34538.Īdd -privileged to the startup parameters to grant Logtail the privileged permission. Otherwise, the container text file busy error may occur when you delete other containers.įor CentOS 7.4 or later except CentOS 8.0, set the fs.may_detach_mounts parameter to 1. Before you configure the parameters, you must complete one of the following configurations.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |