Repository navigation
Feature Request: Disable lambda_unhandled_exception_warning_message #139
Description
The lambda_unhandled_exception_warning_message (LAMBDA_WARNING: Unhandled exception...) is ~ 633 chars and adds little value to our debugging. I understand the desire to warn people the runtime may have changed underfoot, and that's why their code is raising exceptions, but I'd like a way to disable it.
A pr from me would probably be something like
_disable_unhandled_exception_warning = bool(os.environ.get("AWS_LAMBDA_EXCEPTION_WARNING_DISABLE"))
# SNIP ...
if _disable_unhandled_exception_warning:
from .lambda_literals import lambda_unhandled_exception_warning_message
log_sink.log(lambda_unhandled_exception_warning_message, _WARNING_FRAME_TYPE)
log_error(error_result, log_sink)
lambda_runtime_client.post_invocation_error(
invoke_id, to_json(error_result), to_json(xray_fault)
)
near
Perhaps you have a different idea? Or maybe this is a non-starter. Didn't want to clutter PRs before asking.
Activity
tlinhart commentedon Oct 1, 2024
Another reason one might want to disable this message is that CloudWatch merges this warning with the actual error and handles it as a single log event. When using ALC with JSON log format, this makes it hard to parse the log event as JSON (in my case it's streamed to Grafana Loki).
abillingsley commentedon Oct 10, 2024
like @tlinhart we are facing this issue with our Cloudwatch logs which are forwarded to DataDog for aggregation. Not only is the structured logging lost but the ERROR log is reported as an INFO log message making monitoring of "ERROR" logs more difficult
Downgrading to 2.0.8 with no other changes yields the following