Docs

Torch Log Service

Host group

Create host group (IP address)

This topic describes how to create an IP address-based host group.

Prerequisites

A server is prepared as the log source. If the server is a VolcanoEngine ECS, it must be in the same region as the project.

If VolcanoEngine ECS is not enabled, install the latest version of LogCollector on servers before adding ECS servers to the host group in batches. For more details, see Install LogCollector (host machine).

Notice

You can create up to 200 host groups for each region under each VolcanoEngine main account, and each host group can have up to 1,000 IP addresses.

Currently, only Linux servers are supported.

Servers in a host group are identified and distinguished by IP address. By default, the IP address of the first network card is used for identification. You can also specify a different IP address via the ip parameter during initialization. For more details, see Install LogCollector (host machine).

Only LogCollector V1.0.8 and later versions support auto-upgrade. If you need to enable auto-upgrade, make sure all servers that are ready to join host group have the required version installed before you create the host group. Otherwise, LogCollectors that do not meet the version requirements can not be auto-upgraded. For LogCollector V1.0.7 and previous versions, refer to Upgrade LogCollector (host machine) for upgrade instructions.

LogCollector does not support auto-upgrade in container scenarios. If needed, replace the image manually.

Steps

Obtain the IP address of the host machine (configured when Volcano ECS is not enabled).

Servers in a host group are identified by IP address. Before creating IPaddress-based host group, obtain the IP address reported by LogCollector from the host machine or container. You can view this IP address in ip field under /usr/local/logcollector/agent_info.json file.

Description

If the Logcollector version is below v2.2.0, the configuration file path is /usr/local/filebeat-7.12.0/agent_info.json. To view LogCollector version, see 2. View software version.

As shown below, log in to the specified host machine and check the ip field in the /usr/local/logcollector/agent_info.json file.

hostname:/home # cat /usr/local/logcollector/agent_info.json
{
"hostname": "logcollector-dnwwc",
"ip": "10.56.*.*",
"logcollect_version": "2.2.1",
"update_time": "2025.01.14 15:19:29"
}

Tip

By default, LogCollector takes the IP address of the first network card as the IP address of current host or container and reports it to the server. You can also manually specify the IP address or modify the IP address obtaining policy in LogCollector. For more details, see Set IP addresses for hosts or containers.

Select the region where log service is located from the top navigation bar.

In the left navigation panel, select Resource management > Host Group.

On the Host group management page, click Create host group.

In the Create host group dialog box, enter the basic information for the host group, and then click Create.

Parameters	Description
Host group name	Name of the host group.
Host group type	Type of host group. Set this as the IP address.
Volcano ECS	If enabling Volcano ECS, VolcEngine ECS instances can be added to the current host group. After enabling, you must manually select the ECS instance that needs to be added. Only supports adding ECS instances with Cloud Assistant installed and both Cloud Assistant and the instance are in Running status. The system automatically installs LogCollector for the selected ECS instances. ECS instances that have started installing LogCollector cannot be stopped or uninstalled. Proceed with caution.
IP address	Server IP address. Tip Enter the server IP address you obtained in step 1. When adding multiple machines to the host group, you can separate IP addresses with Chinese commas, English commas, spaces, or newlines. Servers with Windows are not supported for now.
LogCollector service log	You can choose whether to enable the LogCollector service log. When enabled, the LogCollector client records information like runtime status and collection progress in real time during operation. For more details, see Service log overview.
LogCollector auto upgrade	LogCollector V1.0.8 and later versions support automatic upgrades. Once enabled, the log service will run an upgrade check at the specified time each day. If all upgrade criteria are met, LogCollector will upgrade automatically. No manual action is required. For automatic upgrades, we recommend that you set it during off-peak business hours. LogCollector may restart during the upgrade, but no logs will be lost. Versions before LogCollector V2.3.1: Click the switch to enable or disable the automatic upgrade feature. Set the automatic upgrade time after enabling the feature. If you need a higher version of LogCollector after disabling, refer to Upgrade LogCollector (host machine) for instructions. LogCollector V2.3.1 and later versions: After creating the host group, go to the LogCollector management tab on the host group details page to enable the feature. For details, see View host group.
IAM Project	Select the IAM project to which the currently created host group belongs from the dropdown list. If you have not created any IAM project or there is no other IAM to select, click Create project to create a new IAM project. If no IAM project is specified, TLS categorizes the host project into the IAM project named default.

View host group LogCollector connection status

The host machine with LogCollector installed regularly reports its heartbeat status to TLS. You can check whether LogCollector and TLS are connected properly based on the heartbeat status. After successfully creating a host group, you can view the overall heartbeat status on the host group management page.

The heartbeat status column displays the number of IP addresses and the number of servers in each status.

Normal: The connection between LogCollector on the server and TLS is normal.

Abnormal: Some machines in the host group are in abnormal status. To view the IP addresses of servers with heartbeat abnormalities, click the host group name.

Tip

After adding servers to the host group, the server heartbeat status will briefly show as Abnormal until LogCollector successfully reports the heartbeat status to TLS. If the server heartbeat status Exception persists for more than one minute, it is recommended to refer to How to troubleshoot host group heartbeat status Exception (host machine) step-by-step troubleshooting.

Last updated: 2026.07.29 15:02:31