Uploads a batch of log events to the specified log stream.
You must include the sequence token obtained from the response of the previous call. An
upload in a newly created log stream does not require a sequence token. You can also get the
sequence token in the expectedSequenceToken field from
InvalidSequenceTokenException. If you call PutLogEvents twice
within a narrow time period using the same value for sequenceToken, both calls
might be successful or one might be rejected.
The batch of events must satisfy the following constraints:
The maximum batch size is 1,048,576 bytes. This size is calculated as the sum of
all event messages in UTF-8, plus 26 bytes for each log event.
None of the log events in the batch can be more than 2 hours in the future.
None of the log events in the batch can be older than 14 days or older than the retention
period of the log group.
The log events in the batch must be in chronological order by their timestamp. The
timestamp is the time the event occurred, expressed as the number of milliseconds after
Jan 1, 1970 00:00:00 UTC. (In Amazon Web Services Tools for PowerShell and the Amazon Web Services SDK for .NET, the
timestamp is specified in .NET format: yyyy-mm-ddThh:mm:ss. For example,
2017-09-15T13:45:30.)
A batch of log events in a single request cannot span more than 24 hours. Otherwise, the operation fails.
The maximum number of log events in a batch is 10,000.
There is a quota of 5 requests per second per log stream. Additional requests are throttled. This quota can't be changed.
If a call to PutLogEvents returns "UnrecognizedClientException" the most likely cause is an invalid Amazon Web Services access key ID or secret key.
example
Use a bare-bones client and the command you need to make an API call.
Uploads a batch of log events to the specified log stream.
You must include the sequence token obtained from the response of the previous call. An upload in a newly created log stream does not require a sequence token. You can also get the sequence token in the
expectedSequenceTokenfield fromInvalidSequenceTokenException. If you callPutLogEventstwice within a narrow time period using the same value forsequenceToken, both calls might be successful or one might be rejected.The batch of events must satisfy the following constraints:
The maximum batch size is 1,048,576 bytes. This size is calculated as the sum of all event messages in UTF-8, plus 26 bytes for each log event.
None of the log events in the batch can be more than 2 hours in the future.
None of the log events in the batch can be older than 14 days or older than the retention period of the log group.
The log events in the batch must be in chronological order by their timestamp. The timestamp is the time the event occurred, expressed as the number of milliseconds after Jan 1, 1970 00:00:00 UTC. (In Amazon Web Services Tools for PowerShell and the Amazon Web Services SDK for .NET, the timestamp is specified in .NET format: yyyy-mm-ddThh:mm:ss. For example, 2017-09-15T13:45:30.)
A batch of log events in a single request cannot span more than 24 hours. Otherwise, the operation fails.
The maximum number of log events in a batch is 10,000.
There is a quota of 5 requests per second per log stream. Additional requests are throttled. This quota can't be changed.
If a call to
PutLogEventsreturns "UnrecognizedClientException" the most likely cause is an invalid Amazon Web Services access key ID or secret key.Use a bare-bones client and the command you need to make an API call.
import { CloudWatchLogsClient, PutLogEventsCommand } from "@aws-sdk/client-cloudwatch-logs"; // ES Modules import // const { CloudWatchLogsClient, PutLogEventsCommand } = require("@aws-sdk/client-cloudwatch-logs"); // CommonJS import const client = new CloudWatchLogsClient(config); const command = new PutLogEventsCommand(input); const response = await client.send(command);PutLogEventsCommandInput for command's
inputshape.PutLogEventsCommandOutput for command's
responseshape.config for CloudWatchLogsClient's
configshape.