Updated on 2025-08-05 GMT+08:00

Configuring Log Settings of a VM-Deployed Component

For VM-deployed components, you can view run logs on the AOM console. ServiceStage also allows you to configure log settings of a component deployed on an ECS bound to the environment using a VM and collect the component run logs to LTS for viewing and processing.

Configuring Log Settings of a VM-Deployed Component

  1. Choose Log Settings.
  2. Determine whether to collect component run logs to LTS by referring to the following table.

    Whether to Collect Component Run Logs to LTS

    Description

    Yes

    1. Select Auto connection to LTS.
    2. Enter a Log Collection Path.
      • Click Add Path to set multiple log data collection sources.
      • If no log collection path is set, logs in the /var/log/{instanceName}/*/start_app.log directory are collected by default. instanceName indicates the name of the current component instance.
    After a component is configured and deployed, the system automatically generates log group and log stream configurations, and generates access configurations and host groups on the Ingestion Management page of the LTS console.
    • Log Group: The naming rule is servicestage-{Application ID}. Use the ID of the application to which the component belongs.
    • Log Stream: The naming rule is lts-topic-{Component name}. Use the name of the component connected to LTS.
    • Ingestion: The naming rule is access-config-{Component name}. Use the name of the component connected to LTS.
    • Host Group: The naming rule is vm-{Instance ID}. Use the ID of the component instance connected to LTS.

    No

    Do not select Auto connection to LTS.

    • After the component is configured and deployed, you can view running logs on the AOM console. For details, see Viewing Log Files.
    • After the component is configured and deployed, you can collect component logs to LTS by referring to Managing Component LTS Logs.