Log Service allows you to collect logs by using clients, web pages, protocols, SDKs, and APIs. These collection methods are implemented based on RESTful APIs. This topic describes the collection methods that are supported by Log Service.

Data sources

The following table describes the data sources from which Log Service can collect logs.
Type Source Collection method Reference
Application Program output Logtail None
Access log Logtail Collect and analyze NGINX access logs
Link tracking Jaeger Collector and Logtail None
Language Java Log Service SDK for Java and Java Producer Library None
Log4J Appender 1.x and 2.x None
LogBack Appender LogBack None
C Log Service C SDK None
Python Log Service Python SDK None
Python Logging Python Logging Handler None
PHP Log Service PHP SDK None
.Net Log Service csharp SDK None
C++ Log Service C++ SDK None
Go Log Service Go SDK and Golang Producer Library None
NodeJS NodeJs None
JS JS/Web Tracking None
OS Linux Logtail None
Windows Logtail None
Mac/Unix Native C None
Docker file Use Logtail to collect Docker files. None
Docker output Use Logtail to collect container logs. None
Database MySQL Binlog Collect MySQL binary logs None
JDBC Select Collect MySQL query results None
Mobile client iOS/Android Log Service SDK for Android and Log Service SDK for iOS None
Web page JS/Web Tracking None
Intelligent IoT C Producer Library None
Others HTTP polling Logtail HTTP Collect and analyze NGINX monitoring logs
Syslog Use Logtail to collect syslog logs. None
Data import MaxCompute Import data from MaxCompute to Log Service None
Object Storage Service (OSS) Import data from OSS to Log Service None
Flink Use Flink to write data to Log Service. Register Log Service resources
Third-party software Logstash Logstash None
Flume Use Flume to consume log data None
Alibaba Cloud services Elastic Compute Service (ECS) and OSS logs For more information, see Alibaba Cloud service logs. None

Select a network

Log Service provides endpoints for different Alibaba Cloud regions. For more information, see Endpoints. Each region allows access from the following networks:

  • Internal network (classic network or VPC): Recommended. Log Service can access other Alibaba Cloud services in the same region over a reliable link.
  • Internet: Internet can be accessed without limits. The transmission speed depends on the link quality. We recommend that you use HTTPS to ensure a secure data transmission.

FAQ

  • Which network do I select for private line access?

    We recommend that you select the internal network (classic network or VPC).

  • Can I collect public IP addresses when I collect Internet data?

    Yes, you can enable Log Service to record public IP addresses. For more information, see Create a Logstore.

  • Which network do I select if I want to collect ECS logs from Region A and write these logs to a Log Service project in Region B?

    You can install Logtail on the ECS instance in Region A for Internet transmission and specify the endpoint that is associated with Region B. For more information about how to select a network, see Select a network type.

  • How can I determine whether an endpoint is accessible?

    You can run the following command. The endpoint is accessible if a message is returned.

     curl $myproject.cn-hangzhou.log.aliyuncs.com

    $myproject specifies the project name and cn-hangzhou.log.aliuncs.com specifies the endpoint.