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. Currently, the following APIs are available:
| Objects | Method |
|---|---|
| Log | Basic concepts of logs and log groups |
| Project | List, Create, Delete, Get |
| Project | GetProjectLogs. Count all the logs in a project. |
| Config (Configuration) | List, Create, Delete, Get, Update |
| GetAppliedMachineGroups(apply/remove a configuration) | |
| MachineGroup (Machine Group) | List, Create, Delete, Get, Update |
| Apply/Remove | |
| GetAppliedConfigs (query the list of applied configurations) | |
| LogStore (Logstore) | List, Create, Delete, Get, Update |
| GetLogs (query logs) and GetHistograms (query log distribution) | |
| Index | Create, Update, DeleteGetIndex |
| Shard (Partition) | List, Split, 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) | |
| ConsumerGroup | Create, Update, Delete, List |
| HeartBeat, GetCheckpoint, UpdateCheckpoint |
You can use the APIs to:
- Collect logs based on Logtail configuration and Machine group.
- Create Logstore. Then, write and read logs to/from the Logstore.
- Set access control rules for different users.
Note
- Currently, APIs provide the Rest style.
- To use APIs, you must know Service endpoint.
- 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 HTTP header, seePublic request header, This HTTP header must participate in the signature. For more information, see Request signature.