Uploads a batch of log events to the specified log stream.
The sequence token is now ignored in
actions are always accepted and never return
DataAlreadyAcceptedException even if the sequence token is not valid. You can use
PutLogEvents actions on the same log stream.
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 more than 14 days in the past. Also, none of the log events can be from earlier 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 that the event occurred, expressed as the number of milliseconds
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,
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.
The quota of five requests per second per log stream
has been removed. Instead,
PutLogEvents actions are throttled based on a
per-second per-account quota. You can request an increase to the per-second throttling
quota by using the Service Quotas service.
If a call to
PutLogEvents returns "UnrecognizedClientException" the most
likely cause is a non-valid Amazon Web Services access key ID or secret key.