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
One of the frustrating things about running into a Lambda timeout when using structured logs is that nothing is logged. Ideally, when using metric_scope, it should be able to flush the log before the timeout expires using context.get_remaining_time_in_millis(), perhaps setting a property indicating this was the case (since there's a possibility the function actually does complete after the flush occurs and some logging was lost)
The text was updated successfully, but these errors were encountered:
@benkehoe We have added this request to our queue and will look into it as soon as we can. Feel free to open a PR if you would like this change sooner and we can review it and publish for you.
One of the frustrating things about running into a Lambda timeout when using structured logs is that nothing is logged. Ideally, when using
metric_scope
, it should be able to flush the log before the timeout expires usingcontext.get_remaining_time_in_millis()
, perhaps setting a property indicating this was the case (since there's a possibility the function actually does complete after the flush occurs and some logging was lost)The text was updated successfully, but these errors were encountered: