You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What this means practically is that Lambda will succeed, returning a list of failed events, rather than throwing an error.
Which means that the aws.lambda.errors and aws.lambda.enhanced.errors metrics are both useless, because even if the whole batch of events fails to process, the invocation is marked as a success.
It would be great if we could have a metric driven by the number of failed events (size of the batchItemFailures array in the response).
The text was updated successfully, but these errors were encountered:
At our company, most of our Lambda functions are batching SQS events and using batchItemFailures for partial batch failures.
What this means practically is that Lambda will succeed, returning a list of failed events, rather than throwing an error.
Which means that the
aws.lambda.errors
andaws.lambda.enhanced.errors
metrics are both useless, because even if the whole batch of events fails to process, the invocation is marked as a success.It would be great if we could have a metric driven by the number of failed events (size of the
batchItemFailures
array in the response).The text was updated successfully, but these errors were encountered: