Log Service provides the real-time consumption feature that allows you to consume data in real time by calling the API or by using SDKs. This topic provides an overview of the real-time consumption feature, including the concept, benefits, scenarios, billing, and consumers.

Real-time consumption

Real-time consumption refers to the real-time consumption of log data by entities such as third-party software, applications in different programming languages, cloud services, and stream computing frameworks. These entities call the API or use SDKs to consume the log data in Log Service in real time. This feature reads full data in the first-in, first-out (FIFO) order, which is similar to Apache Kafka.

Note Both the real-time consumption feature and the query and analysis feature are used to read data. For more information about the difference between the two features, see What are the differences between LogHub and LogSearch?.


Real-time consumption is suitable for scenarios such as stream computing and real-time computing. Real-time consumption is time-sensitive and allows data consumption in seconds. You can customize the data retention period.


Real-time consumption has the following benefits:
  • Centralized data storage

    Log Service stores log data that is collected from different machines. This way, you can directly consume the collected data in real time by using SDKs.

  • Data classification and management

    Log Service supports data classification and management, which allows different applications and services to consume data of different types in different projects in real time.


You are charged for real-time consumption based on multiple billable items, such as read and write traffic and requests. For more information, see Billable items.


The following table describes the consumers that are supported by real-time consumption.