Log Service (Log) is a platform service specific to logs. Log supports real-time collection, storage and delivery of various types of logs. Besides, Log synchronizes data between tables for the MaxCompute and ships logs to the MaxCompute for analysis.
Besides operations on logs through the management console, Log allows you to use Application Programming Interfaces (APIs) to write and query logs, and manage your projects and LogStores. Currently, the following APIs are available.
|Log||A basic concept of Log|
|Config||List, Create, Delete, Get, and Update|
|GetAppliedMachineGroups (query the machine group applied)|
|MachineGroup||List, Create, Delete, Get, and Update|
|Apply/Remove (apply/remove an application)|
|GetAppliedConfigs (query the list of configurations applied)|
|LogStore||List, Create, Delete, Get, and Update|
|GetLogs (query logs), and GetHistograms (query log distribution)|
|Shard||List, Split, Merge, and Delete|
|PostLogStoreLogs (write a log)|
|GetCursor (locate the log location)|
|PullLogs (consume a log)|
|Shipper||GetShipperStatus (query the status of a LogShipper task)|
|RetryShipperTask (retry a failed LogShipper task)|
You can use the APIs to perform the following operations:
- Collect logs based on configuration and machine group.
- Create a LogStore, write a LogStore, and read a log.
- Set access control rules for different users.
- Currently, APIs support the Rest style.
- To use the APIs, you need to know the API access address.
- Security verification is required for all requests from APIs. Refer to Request signature to see API request signature mechanism and procedures.
- Similar to general cloud accounts, subaccounts of RAM, STS or RAM can use their AK signatures to call APIs on Log. The STS temporary identity consists of a temporary AK and a special HTTP header which needs to participate in the signature. For details, refer to Documentation.