Comment on page

Log Pipelines

A log pipeline refers to an instance or configuration of the Logging Service you can create using the REST API. To create an instance of Logging Service, you can request the designated endpoint, such as This is an example of an endpoint, and the actual endpoint may vary.
Within each pipeline instance, it is possible to define multiple log streams, where each stream functions as a separate log source. These log streams allow you to organize and manage different sources of logs within your logging system.
Note: Based on your pricing model, a specific limit is tied to each pipeline, which limits the log rate you can send to the log server.
To differentiate the log sources and enable effective reporting, it is necessary to provide a unique tag for each log source within the pipeline instance. The tag serves as an identifier or label for the log source, allowing you to distinguish and track the logs from different sources easily.
After the pipeline is set up, a unique endpoint is assigned to each pipeline, thus establishing a connection, either HTTP or TCP, with an independent log server. This endpoint serves as the designated destination for sending logs generated by all the log sources within the pipeline. However, to ensure proper categorization and differentiation, each pipeline configuration log source must utilize its designated tag. By adhering to this practice, the logs generated by each source can be accurately identified and traced, even when they are directed to the same endpoint.
Logging Service Overview Design