Log Service allows you to collect and manage logs by using the Log Service console. In addition, you can use API operations to write logs, query logs, and manage your projects and Logstores.

The following table lists the available API operations.

Object Operation
Log Basic concepts, such as log and log group
Project List, Create, Delete, Get, and Update
GetProjectLogs (Queries all logs in a project)
Config (Logtail configuration file) List, Create, Delete, Get, and Update
GetAppliedMachineGroups (Queries the machine groups to which a Logtail configuration file is applied)
MachineGroup List, Create, Delete, Get, and Update
Apply and Remove (Deletes a Logtail configuration file)
GetAppliedConfigs (Queries the applied Logtail configuration files)
LogStore List, Create, Delete, Get, and Update
GetLogs (Queries logs) and GetHistograms (Queries the distribution of logs)
Index Create, Update, Delete and GetIndex
Shard List, Split, and Merge
PostLogStoreLogs (Writes logs)
GetCursor (Locates a log)
PullLogs (Consumes a log)
Shipper (LogShipper rules) GetShipperStatus (Queries the status of a LogShipper task)
RetryShipperTask (Re-runs a failed LogShipper task)
Consumer group Create, Update, Delete, and List
HeartBeat (Sends heartbeat package), GetCheckpoint and UpdateCheckpoint

You can use the API operations to perform the following operations:

  • To use the API operations, you must specify the endpoints. For more information, see Endpoints.
  • Security verification is required for all API requests. For information about the signature algorithm and process, see Request signatures.
  • You can manage Log Service resources by using Resource Access Management (RAM) and Security Token Services (STS). If you are a RAM user, you must provide an AccessKey pair to call the API operations. To use the STS temporary identity, you must provide the STS token and a specific HTTP header. For more information, see Common request headers. This HTTP header is used to sign the request. For more information, see Request signatures.