LogHub supports multiple methods to collect logs, such as by using clients, Web pages, protocols, and SDKs/APIs (mobile devices and games). All the collection methods are based on Restful API. You can also implement new collection methods by using APIs/SDKs.
Collection source
| Type | Source | Access method | Others |
|---|---|---|---|
| Application | Program output | Logtail | Use case |
| Access log | Logtail | Nginx access | |
| Link tracking | Jaeger Collector and Logtail | ||
| Language | Java | SDK and Producer Library | |
| Log4J Appender | 1.x and 2.x | ||
| LogBack Appender | LogBack | ||
| C | Native C | ||
| Python | Python | ||
| PHP | PHP | ||
| C# | C# | ||
| Go | Go | ||
| NodeJS | NodeJs | ||
| JS | JS/Web Tracking | ||
| OS | Linux | Logtail | |
| Windows | Logtail | ||
| Mac/Unix | Native C | ||
| Docker file | Logtail file collection | ||
| Docker output | Logtail container output | ||
| Database | MySQL Binlog | Logtail MySQL | |
| JDBC Select | Logtail JDBC | ||
| Mobile | iOS/Android | iOS and Android | |
| Web page | JS/Web Tracking | ||
| Intelligent IoT | C Producer Library | Use case | |
| Others | HTTP round robin | Logtail HTTP | Nginx monitoring |
| Syslog | Logtail syslog | ||
| Cloud product | Elastic Compute Service (ECS) instance | Logtail | |
| Container Service | Logtail, FluentBit (provided by the customer) | Text,Output | |
| Object Storage Service (OSS) | Open a ticket to apply for a whitelist. | ||
| Server Load Balancer | Activate on the product page. | Introduction | |
| Content Delivery Network (CDN) | Open a ticket to apply for a whitelist. | ||
| Function Compute (FC) | Activate on the product page. | Introduction | |
| API Gateway | Activate on the product page. | Introduction | |
| Message Service (MNS) | Open a ticket to apply for a whitelist. | ||
| MaxCompute | Import DataWorks data | ||
| WAF | Open a ticket to apply for a whitelist. | ||
| Situation Awareness | Open a ticket to apply for a whitelist. | ||
| Server Guard | Open a ticket to apply for a whitelist. | ||
| Third-party software | Logstash | Logstash |
Select network and access point
Log Service provides access point in each region and each region provides two network access methods:
- Intranet (classic network)/private network (Virtual Private Cloud (VPC)): The service access in the current region, which has the best quality of link bandwidth (recommended).
- Internet (classic network): Accessible without any limits. The access speed depends on the link quality. We recommend that you use HTTPS to guarantee the transmission security.
FAQ:
Q: How to select the network for private line access?
A: Select the intranet/private network access point.
Q: How to select the network if I want to collect ECS logs from region A to the Log Service project in region B?
A: Install the Internet version Logtail of region B on the ECS instance in region A for Internet transmission.
Q: How to quickly determine whether it is accessible or not?
A: Run the following command. It is accessible if any information is returned.
curl $myproject.cn-hangzhou.log.aliyuncs.com
$myprojectindicates the project name andcn-hangzhou.log.aliuncs.comindicates the access point.