Skip to content

Conversation

@adamantal
Copy link
Contributor

@adamantal adamantal commented Dec 29, 2025

Description

The log report introduced in #2011 does not fully provide the same log, as AWS prints the status field in case of a non-success execution.

This PR adds this piece of information to the report

Testing

Tested on a dev environment using a synthetic Lambda that times out after x seconds based on input.

Also verified that in case of a cold Lambda, it can be quite verbose (both init duration and status is there):

2025-12-29 14:36:41.795	
REPORT RequestId: 595492f6-5916-4b98-94e5-a1079dfab87b Duration: 5000.00 ms Billed Duration: 5579 ms Memory Size: 3008 MB Max Memory Used: 113 MB Init Duration: 578.07 ms Status: timeout

so the behaviour should be correct

@adamantal adamantal requested a review from a team as a code owner December 29, 2025 13:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants