Log Service (abbreviated to LOG) is a platform service specific to logs, which supports real-time collection, storage, and delivery of various types of logs. Besides, Log Service synchronizes data between MaxCompute tables and can ship logs to MaxCompute for big data analysis.
Besides the Log Service console, you can use Application Programming Interfaces (APIs) to write and query logs, and manage your projects and Logstores. Currently, the following APIs are available.
|Log||Basic concepts of logs and log groups|
|Config||List, Create, Delete, Get, and Update|
|GetAppliedMachineGroups (query the applied machine groups)|
|MachineGroup||List, Create, Delete, Get, and Update|
|Apply/Remove (apply/remove a configuration)|
|GetAppliedConfigs (query the list of applied configurations)|
|Logstore||List, Create, Delete, Get, and Update|
|GetLogs (query logs) and GetHistograms (query log distribution)|
|Shard||List, Split, and Merge|
|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:
- Collect logs based on configurations and machine groups.
- Create a Logstore. Then, write and read logs to/from the Logstore.
- Set access control rules for different users.
- Currently, APIs provide the RESTful style.
- To use APIs, you must know the API access address.
- Security verification is required for all API requests. For more information about the signature and process of API requests, see Request signature.
- Log Service supports Resource Access Management (RAM) and Security Token Service (STS). Similar to common cloud accounts, RAM sub-accounts can use APIs by using their AccessKey signature. To use the STS temporary identity, you must use the temporary AccessKey and enter a special HTTP header. For more information, see Public request header. This HTTP header must participate in the signature. For more information, see Request signature.