Container Compute Service:Configure application log collection by using pod environment variables

Use the console wizard

1. Log on to the ACS console. In the left-side navigation pane, click Clusters.

2. On the Clusters page, find the cluster and click its ID. In the left navigation pane, choose Workloads > Deployments.

3. On the Deployments page, select a namespace from the Namespace drop-down list, then click Create from Image in the upper-left corner.

   This example uses a stateless application. The steps are the same for other workload types.

4. On the Basic Information page, set Name, Replicas, and Type, then click Next to go to the Container page.

   Only log-related parameters are described here. For all other application parameters, see Create a stateless application using a Deployment.

5. In the Log section, configure log collection:

   1. Click Collection Configuration to add a configuration entry. Each entry requires two fields: Each collection configuration corresponds to one Logstore. Logs are collected line by line by default.

      • Logstore: The name of the Logstore where collected logs are stored. If the Logstore does not exist, ACS creates it automatically in the SLS project associated with the cluster. The default log retention period is 180 days.

      • Log Path in Container (Can be set to stdout): The path to collect logs from. Set to stdout to collect both stdout and stderr. Set to a file path (for example, /usr/local/tomcat/logs/catalina.*.log) to collect log files.

   2. Click Custom Tag to add key-value tags appended to every collected log entry. Use tags to mark logs with metadata such as a version number.

6. Complete the remaining wizard steps. For details, see Create a stateless application using a Deployment.

Use a YAML file

Configure log collection by adding environment variables prefixed with aliyun_logs_ to the container spec.

1. Log on to the ACS console. In the left-side navigation pane, click Clusters.

2. On the Clusters page, find the cluster and click its name. In the left navigation pane, choose Workloads > Deployments.

3. On the Deployments page, select a namespace from the Namespace drop-down list, then click Create from YAML in the upper-right corner.

   This example uses a stateless application. The steps are the same for other workload types.

4. Configure the YAML template. The following example pod demonstrates collection configuration and custom tags:

   • aliyun_logs_log-stdout — creates a Logstore named log-stdout and collects stdout/stderr from the container.

   • aliyun_logs_log-varlog — creates a Logstore named log-varlog and collects /var/log/*.log files.

   Important

   For any collection path other than stdout, add a corresponding volumeMounts entry to the container spec. The example above collects /var/log/*.log, so a volumeMounts for /var/log is required.

   apiVersion: v1
   kind: Pod
   metadata:
     name: my-demo
   spec:
     containers:
     - name: my-demo-app
       image: 'registry.cn-hangzhou.aliyuncs.com/log-service/docker-log-test:latest'
       env:
       # Log collection: send stdout to the "log-stdout" Logstore
       - name: aliyun_logs_log-stdout
         value: stdout
       # Log collection: collect /var/log/*.log files to the "log-varlog" Logstore
       - name: aliyun_logs_log-varlog
         value: /var/log/*.log
       # Custom tag: append tag1=v1 to all logs in the "mytag1" configuration
       - name: aliyun_logs_mytag1_tags
         value: tag1=v1
       command: ["sh", "-c"]
       args: ["echo 'Starting my demo app'; sleep 3600"]

   All log-related environment variables use the aliyun_logs_ prefix. The example above creates two collection configurations: Custom tags use the aliyun_logs_{key}_tags format. The {key} value can be any name that does not contain an underscore (_). For advanced log collection requirements, see Step 3: Advanced parameters.

5. Click Create to deploy the configuration to the cluster.