How to install and configure LoongCollector on Linux - Simple Log Service

LoongCollector is a collector from Simple Log Service. To collect logs from a Linux server, you must install the LoongCollector client on it. The installation method you choose depends on the relationship between your server and the Simple Log Service project.

Limits

Supported Linux operating systems

The following 64-bit (x86-64) Linux servers are supported.
- Alibaba Cloud Linux 2 and 3
- Anolis OS 7 and 8
- CentOS Linux 6, 7, and 8
- Debian GNU/Linux 8, 9, 10, 11, and 12
- Red Hat Enterprise Linux 6, 7, 8, and 9
- openSUSE 15.1, 15.2, and 42.3
- SUSE Linux Enterprise Server 11, 12, and 15
- Ubuntu 14.04, 16.04, 18.04, 20.04, 22.04, and 24.04
- Other Linux operating systems based on glibc 2.6 or later
- The CPU must support the sse4_2 and avx instruction sets.
The following 64-bit Linux ARM servers are supported.
- Alibaba Cloud Linux 3.2 (ARM)
- Anolis OS 8.2 (ARM) and later
- CentOS 8.4 (ARM)
- Debian 11.2 and 12.2 (ARM)
- Ubuntu 20.04, 22.04, and 24.04 (ARM)
- The minimum required CPU architecture is ARMv8.2-A.

Prerequisites

Permissions

If you log on with an Alibaba Cloud account, you have all permissions by default and can perform these operations directly.

If you log on with a Resource Access Management (RAM) user, ask the Alibaba Cloud account owner to grant you the following system policies. These policies provide the permissions required to manage Simple Log Service, ECS, and OOS resources.

AliyunLogFullAccess: Grants permissions to manage Simple Log Service.
AliyunOOSFullAccess: Grants permissions to manage OOS. This lets you use OOS orchestration to automatically install LoongCollector.
AliyunECSFullAccess: Grants permissions to manage ECS. This lets you run Cloud Assistant commands to install LoongCollector in batches.

If the system policies do not meet your needs, you can create custom policies for fine-grained permission management. For more information, see Create a custom permission policy.

Replace ${projectName} in the Resource field with the name of the project you want to access.

{
  "Version": "1",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": [
        "ecs:DescribeTagKeys",
        "ecs:DescribeTags",
        "ecs:DescribeInstances",
        "ecs:DescribeInvocationResults",
        "ecs:RunCommand",
        "ecs:DescribeInvocations",
        "ecs:InvokeCommand"
      ],
      "Resource": "*"
    },
    {
      "Effect": "Allow",
      "Action": [
        "oos:ListTemplates",
        "oos:StartExecution",
        "oos:ListExecutions",
        "oos:GetExecutionTemplate",
        "oos:ListExecutionLogs",
        "oos:ListTaskExecutions"
      ],
      "Resource": "*"
    },
    {
      "Effect": "Allow",
      "Action": [
        "log:ListProject",
        "log:GetAcceleration",
        "log:ListDomains",
        "log:GetLogging",
        "log:ListTagResources"
      ],
      "Resource": [
        "acs:log:*:*:project/*"
      ]
    },
    {
      "Effect": "Allow",
      "Action": [
        "log:GetProject"
      ],
      "Resource": [
        "acs:log:*:*:project/${projectName}"
      ]
    },
    {
      "Effect": "Allow",
      "Action": [
        "log:ListLogStores",
        "log:GetLogStore",
        "log:GetLogStoreHistogram",
        "log:GetIndex",
        "log:CreateIndex",
        "log:UpdateIndex",
        "log:ListShards",
        "log:GetCursorOrData",
        "log:ListSavedSearch",
        "log:GetLogStoreLogs",
        "log:ListDashboard",
        "log:GetLogStoreContextLogs"
      ],
      "Resource": [
        "acs:log:*:*:project/${projectName}/*"
      ]
    },
    {
      "Effect": "Allow",
      "Action": [
        "log:*"
      ],
      "Resource": [
        "acs:log:*:*:project/${projectName}/logtailconfig/*",
        "acs:log:*:*:project/${projectName}/machinegroup/*"
      ]
    }
  ]
}

Create a project

If you do not have a project, follow these steps to create one. For more information, see Manage a project.

Log on to the Simple Log Service console, click Create Project, complete the following basic configurations, and keep other configurations as default:

Region: Select an appropriate Alibaba Cloud region based on the log source and other requirements. The region cannot be modified after the project is created.
Project Name: Set a name that is globally unique within the Alibaba Cloud region. The name cannot be modified after the project is created.

Create a logstore

If you do not have an active logstore, follow these steps to create one. For more information, see Manage a logstore.

Log on to the Simple Log Service console, and click the target project in the Project List.
On the Log Storage > Logstores tab, click the + icon.
Enter the logstore name, and keep other configurations as default.

Server network requirements

The server where LoongCollector is installed must have outbound port 80 (HTTP) and port 443 (HTTPS) open to allow LoongCollector to upload data.
The server where LoongCollector is installed must be able to connect to the following endpoints:
1. Log on to the Simple Log Service console. In the project list, click the destination project.
2. Click the icon next to the project name to go to the project overview page.
3. On the Endpoints tab, view the domain name for the current project. Replace the placeholders in the command and then run it.
  - If you select the Same account and same region or Different account and same region installation method, data is transmitted over the internal network. Replace ${project_name} with the project name and ${domain_name} with the internal domain name.
  - If you select the Same account, different region or Other cloud/self-managed server installation method, data is transmitted over the public network. Replace ${Project name} with the project name and ${domain_information} with the public domain name.
```
curl https://${projectName}.${domainName}
```
4. If a response similar to {"Error":{"Code":"OLSInvalidMethod","Message":"The script name is invalid : /","RequestId":"5D****09"}} is returned, the network connection is normal. Otherwise, check if the destination address is blocked and review other network settings, such as DNS configurations and security group rules.
  The error message is returned because the access URL is missing required parameters. This test only verifies network connectivity and does not use a complete URL. An error message indicates that the network is functioning correctly.

Choose an installation method

Installation method	Scenarios
Same account and region	This applies only when the server is an Alibaba Cloud ECS instance that belongs to the same Alibaba Cloud account and is in the same region as the Project.
Same account, different region	This applies when the server is an Alibaba Cloud ECS, and both the ECS and the Project belong to the same Alibaba Cloud account, but are not in the same region.
Different account, same region	This applies when the server is an Alibaba Cloud ECS instance, and the ECS instance and the Project are in the same region but in different Alibaba Cloud accounts.
Other cloud or on-premises server	This method applies when the server is not an Alibaba Cloud ECS instance, such as an on-premises server or a server from another cloud provider. An Alibaba Cloud ECS instance can be considered a self-managed server if the instance and the Project do not belong to the same Alibaba Cloud account and are not in the same region.

Same account and region

If your server is an ECS instance that is in the same region and belongs to the same Alibaba Cloud account as your project, you can use Simple Log Service to install LoongCollector with a single click. This process uses the orchestration capabilities of OOS and eliminates the need to log on to the ECS instance to perform the installation manually.

The one-click installation feature is integrated into the data ingestion templates of Simple Log Service. Simple Log Service provides various text log ingestion templates, such as regex, single-line, and multi-line templates. These templates differ only in their processing plugins, and you can add or delete plugins within a template. Select a template that matches the format of the logs you want to collect. Alternatively, you can select any text log template and then configure its processing plugins to suit your logs.

Perform the following steps:

Log on to the Simple Log Service console. In the project list, click the destination project.
Click Log Storage. In the Logstore list, click the icon next to the destination Logstore to expand it.
Click the icon next to Data Ingestion to open a dialog box. In the dialog box, select the Single-line - Text Log Ingestion Template and click Ingest Now.
Click Create Machine Group. Select one or more ECS instances that are in the same region as the project, and then click Install And Create Machine Group.
Wait for the installation to complete. Enter a name and click OK. If the installation fails, click Recreate Installation Task and select the ECS instances again. Make sure that the ECS instances are in the same region as the project.
Click Next. If the heartbeat status is FAIL, click Auto Retry and wait about two minutes until the status changes to OK.
The one-click installation is now complete. Click Next to proceed with the collection configuration.

Same account, different region

If the server is an ECS instance, and the instance and project are under the same Alibaba Cloud account but in different regions, you must manually download the installation package and use data transfer over the internet or transfer acceleration in the installation command.

Perform the following steps:

Download the installation package by running the following command on the server. In the example, you can replace ${region_id} with cn-hangzhou. To accelerate the download, see Region IDs and replace ${region_id} with the ID of the region where your ECS instance is located.
```
wget https://aliyun-observability-release-${region_id}.oss-${region_id}.aliyuncs.com/loongcollector/linux64/latest/loongcollector.sh -O loongcollector.sh;
```
Select a transfer method and run the installation command. Replace ${region_id} with the Region ID of the region where the project is located.
- Internet: This method is suitable for most scenarios, such as cross-region collection or collection from other cloud or on-premises servers. However, it is limited by bandwidth and may be unstable.
```
chmod +x loongcollector.sh; ./loongcollector.sh install ${region_id}-internet
```
- Transfer acceleration: This method is used for cross-region transfers, such as from the Chinese mainland to a region outside China. It uses CDN to improve performance and avoid the high latency and instability of the Internet. However, it incurs additional traffic fees.
  You must first enable the cross-domain log transfer acceleration feature for the project, and then run the installation command.
```
chmod +x loongcollector.sh; ./loongcollector.sh install ${region_id}-acceleration
```
Check the startup status by running the command. If loongcollector is running is returned, the startup is successful.
```
sudo /etc/init.d/loongcollectord status
```
Configure a machine group: Simple Log Service uses machine groups to discover custom identifiers and establish heartbeat connections with LoongCollector on hosts.
1. On the server, write the custom string user-defined-test-1 to the custom identifier file. This string is used in subsequent steps.
```
# Write a custom string to the specified file. If the directory does not exist, create it manually. The file path and name are fixed by Simple Log Service and cannot be customized.
echo "user-defined-test-1" > /etc/ilogtail/user_defined_id 
```
2. Log on to the Simple Log Service console. In the project list, click the destination project.
3. Click Resource, and then click Machine Groups.
4. Click the icon to the right of Machine Groups, and then click Create Machine Group.
5. Configure the following parameters and click OK.
  - Machine Group Name: Enter a name that is unique within the project. The name must be 3 to 128 characters in length, start and end with a lowercase letter or a digit, and contain only lowercase letters, digits, hyphens (-), and underscores (_).
  - Machine Group Identifier: Select Custom Identifier.
  - Custom Identifier: Enter the custom identifier that you configured. It must be the same as the custom string in the custom identifier file on the server. In this example, the value is user-defined-test-1.
After the machine group is created, click the machine group in the list. On the Machine Group Status tab, check the Heartbeat status. If the status is FAIL, wait about two minutes and manually refresh the page. If the status is OK, the machine group is created successfully.
After the installation is complete, you must also configure collection settings to collect logs.

Different account, same region

If your server is an Alibaba Cloud ECS instance that is in the same region as the project but belongs to a different Alibaba Cloud account, you must manually download the installation package. You must also use the internal network transfer method in the installation command and configure a user ID.

Perform the following steps:

Download the installation package by running the following command on the server. In the example, you can replace ${region_id} with cn-hangzhou. To accelerate the download, see Region IDs and replace ${region_id} with the ID of the region where your ECS instance is located.
```
wget https://aliyun-observability-release-${region_id}.oss-${region_id}.aliyuncs.com/loongcollector/linux64/latest/loongcollector.sh -O loongcollector.sh;
```
Run the installation command. Replace ${region_id} with the Region ID of the region where the project is located.
If a connection timeout occurs, the ${region_id} may be incorrect. An internal network connection cannot be established between different regions, which causes a timeout. You must correct the region ID and run the installation command again.
```
chmod +x loongcollector.sh; ./loongcollector.sh install ${region_id}
```
Check the startup status by running the command. If loongcollector is running is returned, the startup is successful.
```
sudo /etc/init.d/loongcollectord status
```
Configure a user ID. The user ID file contains the ID of the Alibaba Cloud account to which the project belongs. This ID grants the account permission to access and collect logs from this server.
You only need to configure a user ID when collecting logs from an ECS instance that does not belong to your account, an on-premises server, or a server from another cloud provider. If multiple accounts collect logs from the same server, you can create multiple user ID files on that server.
1. Log on to the Simple Log Service console. Move the pointer over your profile picture in the upper-right corner. In the tab that appears, view and copy the account ID. Make sure to copy the ID of the Alibaba Cloud account.
2. On the server where LoongCollector is installed, create a user ID file. Use the Alibaba Cloud account ID as the filename.
```
touch /etc/ilogtail/users/{Alibaba Cloud account ID} # If the /etc/ilogtail/users directory does not exist, create it manually. The user ID file only needs a filename, not a file extension.
```
Configure a machine group: Simple Log Service uses machine groups to discover custom identifiers and establish heartbeat connections with LoongCollector on hosts.
1. On the server, write the custom string user-defined-test-1 to the custom identifier file. This string is used in subsequent steps.
```
# Write a custom string to the specified file. If the directory does not exist, create it manually. The file path and name are fixed by Simple Log Service and cannot be customized.
echo "user-defined-test-1" > /etc/ilogtail/user_defined_id 
```
2. Log on to the Simple Log Service console. In the project list, click the destination project.
3. Click Resource, and then click Machine Groups.
4. Click the icon to the right of Machine Groups, and then click Create Machine Group.
5. Configure the following parameters and click OK.
  - Machine Group Name: Enter a name that is unique within the project. The name must be 3 to 128 characters in length, start and end with a lowercase letter or a digit, and contain only lowercase letters, digits, hyphens (-), and underscores (_).
  - Machine Group Identifier: Select Custom Identifier.
  - Custom Identifier: Enter the custom identifier that you configured. It must be the same as the custom string in the custom identifier file on the server. In this example, the value is user-defined-test-1.
After the machine group is created, click the machine group in the list. On the Machine Group Status tab, check the Heartbeat status. If the status is FAIL, wait about two minutes and manually refresh the page. If the status is OK, the machine group is created successfully.
After the installation is complete, you must also configure collection settings to collect logs.

Other cloud or on-premises server

If your server is hosted by another cloud provider or is an on-premises server, you must manually download the installation package. You must also use public network transfer or transfer acceleration in the installation command and configure a user ID. An ECS instance is also considered an on-premises server if the instance and the project do not belong to the same Alibaba Cloud account or are not in the same region.

Note

For server limits, see Supported Linux operating systems.

Perform the following steps:

Download the installation package by running the following command on the server. In the example, you can replace ${region_id} with cn-hangzhou. To accelerate the download, see Region IDs and replace ${region_id} with the ID of the region where your ECS instance is located.
```
wget https://aliyun-observability-release-${region_id}.oss-${region_id}.aliyuncs.com/loongcollector/linux64/latest/loongcollector.sh -O loongcollector.sh;
```
Select a transfer method and run the installation command. Replace ${region_id} with the Region ID of the region where the project is located.
- Internet: This method is suitable for most scenarios, such as cross-region collection or collection from other cloud or on-premises servers. However, it is limited by bandwidth and may be unstable.
```
chmod +x loongcollector.sh; ./loongcollector.sh install ${region_id}-internet
```
- Transfer acceleration: This method is used for cross-region transfers, such as from the Chinese mainland to a region outside China. It uses CDN to improve performance and avoid the high latency and instability of the Internet. However, it incurs additional traffic fees.
  You must first enable the cross-domain log transfer acceleration feature for the project, and then run the installation command.
```
chmod +x loongcollector.sh; ./loongcollector.sh install ${region_id}-acceleration
```
Check the startup status by running the command. If loongcollector is running is returned, the startup is successful.
```
sudo /etc/init.d/loongcollectord status
```
Configure a user ID. The user ID file contains the ID of the Alibaba Cloud account to which the project belongs. This ID grants the account permission to access and collect logs from this server.
You only need to configure a user ID when collecting logs from an ECS instance that does not belong to your account, an on-premises server, or a server from another cloud provider. If multiple accounts collect logs from the same server, you can create multiple user ID files on that server.
1. Log on to the Simple Log Service console. Move the pointer over your profile picture in the upper-right corner. In the tab that appears, view and copy the account ID. Make sure to copy the ID of the Alibaba Cloud account.
2. On the server where LoongCollector is installed, create a user ID file. Use the Alibaba Cloud account ID as the filename.
```
touch /etc/ilogtail/users/{Alibaba Cloud account ID} # If the /etc/ilogtail/users directory does not exist, create it manually. The user ID file only needs a filename, not a file extension.
```
Configure a machine group: Simple Log Service uses machine groups to discover custom identifiers and establish heartbeat connections with LoongCollector on hosts.
1. On the server, write the custom string user-defined-test-1 to the custom identifier file. This string is used in subsequent steps.
```
# Write a custom string to the specified file. If the directory does not exist, create it manually. The file path and name are fixed by Simple Log Service and cannot be customized.
echo "user-defined-test-1" > /etc/ilogtail/user_defined_id 
```
2. Log on to the Simple Log Service console. In the project list, click the destination project.
3. Click Resource, and then click Machine Groups.
4. Click the icon to the right of Machine Groups, and then click Create Machine Group.
5. Configure the following parameters and click OK.
  - Machine Group Name: Enter a name that is unique within the project. The name must be 3 to 128 characters in length, start and end with a lowercase letter or a digit, and contain only lowercase letters, digits, hyphens (-), and underscores (_).
  - Machine Group Identifier: Select Custom Identifier.
  - Custom Identifier: Enter the custom identifier that you configured. It must be the same as the custom string in the custom identifier file on the server. In this example, the value is user-defined-test-1.
After the machine group is created, click the machine group in the list. On the Machine Group Status tab, check the Heartbeat status. If the status is FAIL, wait about two minutes and manually refresh the page. If the status is OK, the machine group is created successfully.
After the installation is complete, you must also configure collection settings to collect logs.

Install LoongCollector in batches

If the ECS instances and the project belong to the same account and are in the same region, you can select multiple ECS instances during the automatic installation.
For other scenarios, you can use Cloud Assistant to run one-time tasks using commands. This lets you run LoongCollector installation commands on multiple ECS instances in batches.
For the download and installation commands, see the installation scenarios described previously. For more information about how to use Cloud Assistant, see Create and run a command.

FAQ

How do I install LoongCollector if the server cannot connect to an external network?

Run uname -m on the server where you want to install LoongCollector to check the system architecture. Then, on a server that can access the Internet, run the corresponding download command. You must replace ${region_id} with the Region ID of the region where the project is located.

ARM architecture:

wget https://aliyun-observability-release-${region_id}.oss-${region_id}.aliyuncs.com/loongcollector/linux64/latest/loongcollector.sh;wget http://aliyun-observability-release-${region_id}.oss-${region_id}.aliyuncs.com/loongcollector/linux64/latest/aarch64/main/loongcollector-linux64.tar.gz;

x86-64 architecture:

wget https://aliyun-observability-release-${region_id}.oss-${region_id}.aliyuncs.com/loongcollector/linux64/latest/loongcollector.sh;wget http://aliyun-observability-release-${region_id}.oss-${region_id}.aliyuncs.com/loongcollector/linux64/latest/x86_64/main/loongcollector-linux64.tar.gz;

Copy the downloaded installation script and installation package to the server where you want to install LoongCollector, and then run the following command. Replace ${region_id} with the Region ID of the region where the project is located.
```
chmod +x loongcollector.sh; ./loongcollector.sh install-local ${region_id}-internet
```
Run the check command. If loongcollector is running is returned, the startup is successful.
```
sudo /etc/init.d/loongcollectord status
```
Because the server cannot access the Internet, you also need to configure a proxy to connect to the Internet.

One-click installation failure

Automatic installation is supported only when the ECS instance and the project belong to the same account and are in the same region. If this condition is not met, choose another installation method. If the condition is met, check whether the permission and network requirements in the Prerequisites section are met.

How do I resolve the 'No Heartbeat' or 'FAIL Heartbeat' issue?

If the heartbeat status is FAIL, it may be because the initial heartbeat connection takes some time. Wait about two minutes and then refresh the heartbeat status. If the status is still FAIL, perform the following checks:

Confirm the relationship between the server and the Simple Log Service project. Different relationships correspond to different installation procedures.
- If you find that you selected the wrong procedure, run the chmod +x loongcollector.sh; sudo ./loongcollector.sh uninstall; command on the server to uninstall LoongCollector. Then, select the correct procedure and run it.
If you selected the correct procedure but the heartbeat status is FAIL, check whether the /usr/local/ilogtail/ilogtail_config.json file on the server where LoongCollector is installed contains region information that matches the Region ID of the Simple Log Service project's region.
- If they do not match, replace ${region_id} in the installation command and run the command again. LoongCollector updates the content of the file.
  This method performs an overwrite installation and causes the original configuration to be lost. Use this method with caution on servers that already have collection configurations.
- If the information is consistent or the heartbeat status is still FAIL after reinstallation, proceed with the following checks.
If the procedure requires you to set a user ID file for cross-account scenarios, check the following:
- The user ID must be the ID of the Alibaba Cloud account. If it is not, modify it.
- The Alibaba Cloud account ID must be the ID of the account to which the Simple Log Service project belongs, not the ID of the account to which the ECS server belongs.
Check whether the custom identifier configured in the machine group in the Simple Log Service console is consistent with the content in the custom identifier file on the server. If they are not consistent, modify one of them to ensure they match.
If the heartbeat status is still FAIL, check whether the network requirements in the Prerequisites section are met.

Differences between IP-based and custom ID-based machine groups

Although custom ID-based machine groups are more complex to configure than IP-based machine groups, they are applicable to a wider range of scenarios. Therefore, all installation methods except for the one-click installation recommend using a custom ID-based machine group. The one-click installation uses an IP-based machine group to simplify the process.

IP-based machine groups

When you use an IP-based machine group, you must add the IP address of the server to the machine group to associate them.

This method is simpler to create and configure.
An IP address conflict or a change in the IP address can cause heartbeat failure and affect data collection.

Custom ID-based machine groups

You can associate a server by configuring a custom string as an identifier in the machine group and adding that string to an identifier file on the server. You can configure multiple custom identifiers in the identifier file on a server. Separate the identifiers with line feeds.

The configuration process is more complex than for IP-based machine groups. However, in custom network environments such as a VPC, IP address conflicts can cause collection to fail. Custom identifiers can prevent this issue.
You can implement automatic elastic scaling for machine groups. If you configure the same custom identifier for a new server, Simple Log Service automatically detects and adds the server to the machine group. If you no longer need to collect logs from a server, you can simply delete the identifier file on the server, and the machine group automatically removes the server.
A business system usually consists of multiple modules, and each module can be scaled horizontally, which means you can add multiple servers. To efficiently collect and categorize log data, we recommend that you create a separate machine group for each module. For example, a typical website is divided into an HTTP request module, a logic module, and a storage module. Their custom identifiers can be defined as http_module, logic_module, and store_module, respectively.

References

Regions

Log on to the Simple Log Service console. In the project list, click the destination project.
Click the icon next to the project name to go to the project overview page.
In the Basic Information section, you can view the region name of the current project. For the mapping between region names and region IDs, see the following table.
A region is the geographical location of the physical data center where Alibaba Cloud services are hosted. A Region ID is the unique identifier for an Alibaba Cloud service region.

Region and Region ID mapping

Region Name	Region ID
China (Qingdao)	cn-qingdao
China (Beijing)	cn-beijing
China (Zhangjiakou)	cn-zhangjiakou
China (Hohhot)	cn-huhehaote
China (Ulanqab)	cn-wulanchabu
China (Hangzhou)	cn-hangzhou
China (Shanghai)	cn-shanghai
China (Nanjing - Local Region - Decommissioning)	cn-nanjing
China (Fuzhou - Local Region - Decommissioning)	cn-fuzhou
China (Shenzhen)	cn-shenzhen
China (Heyuan)	cn-heyuan
China (Guangzhou)	cn-guangzhou
Philippines (Manila)	ap-southeast-6
South Korea (Seoul)	ap-northeast-2
Malaysia (Kuala Lumpur)	ap-southeast-3
Japan (Tokyo)	ap-northeast-1
Thailand (Bangkok)	ap-southeast-7
China (Chengdu)	cn-chengdu
Singapore	ap-southeast-1
Indonesia (Jakarta)	ap-southeast-5
China (Hong Kong)	cn-hongkong
Germany (Frankfurt)	eu-central-1
US (Virginia)	us-east-1
US (Silicon Valley)	us-west-1
UK (London)	eu-west-1
UAE (Dubai)	me-east-1
SAU (Riyadh - Partner Region)	me-central-1

LoongCollector network transfer types

An endpoint is the domain name used to access Simple Log Service. It is the URL for accessing a project and its log data, and it is related to the region where the project is located. Simple Log Service provides internal, public, and transfer acceleration endpoints. You can view the endpoints as follows:

Log on to the Simple Log Service console. In the project list, click the destination project.
Click the icon next to the project name to go to the project overview page.
On the Endpoints tab, you can view the domain name for the current project. Different network transfer types correspond to different endpoints. Choosing the right network transfer type helps ensure faster and more stable log data transmission.

Network type	Corresponding endpoint type	Description	Scenarios
Alibaba Cloud internal network	Private domain name	The Alibaba Cloud internal network is a shared gigabit network. Transferring log data over the Alibaba Cloud internal network is faster and more stable than over the Internet. The internal network includes VPCs and the classic network.	The ECS instance and the Simple Log Service project are in the same region, or you have connected an on-premises server to the internal network. Note We recommend creating a Simple Log Service project in the same region as your ECS instance. This lets you collect logs from the ECS instance over the Alibaba Cloud internal network without consuming public bandwidth.
Internet	Public endpoint	Transferring log data over the Internet is not only limited by network bandwidth but can also be affected by network jitter, latency, and packet loss, which impact the speed and stability of data collection.	You can choose to transfer data over the Internet in the following two cases. The ECS instance and the Simple Log Service project are in different regions. The server is from another cloud provider or is an on-premises IDC.
Transfer acceleration	Acceleration endpoint	This method uses Alibaba Cloud CDN points of presence (POPs) to accelerate log collection. It offers significant advantages in terms of network latency and stability compared to collection over the Internet. However, it incurs additional traffic fees.	If your business server and Simple Log Service project are in a domestic region and an international region, respectively, transferring data over the Internet may cause high network latency and instability. In this case, you can choose to use transfer acceleration. For more information, see Transfer acceleration.