Overview

Log Service SDKs are implemented based on Log Service APIs and provide the same capabilities as Log Service APIs. For more information about the Log Service APIs, see Overview.

Similar to Log Service APIs, you must have an enabled Alibaba Cloud AccessKey (consisting of AccessKey ID and AccessKey Secret) to use Log Service SDKs. For more information, see AccessKey.

To use Log Service SDKs, you must know the service endpoint of Log Service in each Alibaba Cloud region. For how to specify the root endpoint in an SDK, see SDK configurations.

Though the implementation details of Log Service SDKs vary with different languages, the SDKs can be considered as Log Service APIs encapsulated in different languages and basically implement the same functions as follows.

• Unified encapsulationof the Log Service APIs, removing your need to build specific API requests and parse responses. The interfaces in various languages are similar, facilitating your switch between different languages.
• Digital signature logic for the Log Service APIs , greatly reducing the complexity of using APIs as you can ignore details of the API signature logic.
• Encapsulation of logs collected to Log Service in the ProtoBuffer format, allowing you to write logs without caring about the details of Protocol Buffer format.
• Implementation of the compression method defined in the Log Service APIs, removing the need to focus on the compression details. SDKs in some languages allow you to specify whether or not to write logs in the compression mode. (By default, the compression mode is used.)
• Unifiederror handling method , allowing you to handle request exceptions in the method that languages are familiar with.
• Currently, SDKs in all languages only support synchronous requests.

The download addresses, usage instructions, and complete programming references of SDKs in different languages are as follows.