Simple Log Service:GetLogs

Operation description

• The Host in the request syntax consists of the Project name and the Simple Log Service endpoint. You must specify the Project in the Host.

• Create and obtain an AccessKey pair. For more information, see AccessKey pair.

An Alibaba Cloud account AccessKey pair has access permissions on all API operations, which poses high security risks. We strongly recommend that you create and use a Resource Access Management (RAM) user for API access or routine O&M. The Resource Access Management (RAM) user must have access permissions to manage Simple Log Service EPS resources. For more information, see Create a RAM user and authorize the RAM user.

• Determine the Project name, region, and Logstore name for the logs you want to query. For more information, see Manage a Project and Manage a Logstore.

• Simple Log Service has usage limits for querying logs. Design proper query and analytic statements and set proper query time ranges. For more information, see Limits on log queries and Limits on log analysis.

• Before you query logs, configure indexes. For more information, see Create indexes.

• When the number of logs involved in a query changes significantly, the Simple Log Service API cannot predict how many times this operation must be invoked to obtain complete results. Check the x-log-progress status value in the response of each request to determine whether you need to invoke this operation again to obtain complete results. Each repeated invocation consumes the same number of query compute units (CUs).

• After logs are written to a Logstore, the latency before the query operations (GetHistograms and GetLogs) can query the logs varies based on the log type. Simple Log Service classifies logs into the following two types based on log UNIX timestamps:

  • Real-time data: The time point in the log is within the range of (-180 seconds, 900 seconds] relative to the current time on the server. For example, if the log time is UTC 2014-09-25 12:03:00 and the server receives the log at UTC 2014-09-25 12:05:00, the log is processed as real-time data. This generally occurs in normal scenarios.

  • Historical data: The time point in the log is within the range of [-7×86400 seconds, -180 seconds) relative to the current time on the server. For example, if the log time is UTC 2014-09-25 12:00:00 and the server receives the log at UTC 2014-09-25 12:05:00, the log is processed as historical data. This generally occurs in data backfill scenarios. The latency from writing real-time data to querying the data is approximately 3 seconds.

• Simple Log Service provides examples of using the GetLogs operation with the Java SDK and Python SDK. For more information, see Java SDK example for GetLogs and Python SDK example for GetLogs.

Authentication resources

The following table lists the authorization information corresponding to this API operation. You can add this information to the Action element of a RAM access policy statement to grant a Resource Access Management (RAM) user or RAM role the authorization to invoke this API operation.