Skip to content

Feature Request: Disable lambda_unhandled_exception_warning_message #139

Open
Open
Feature Request: Disable lambda_unhandled_exception_warning_message#139

Description

@packplusplus
packplusplus
opened on Apr 11, 2024

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

aws-lambda-python-runtime-interface-client/awslambdaric/bootstrap.py

Line 217 in 056aa36

log_sink.log(lambda_unhandled_exception_warning_message, _WARNING_FRAME_TYPE)

Perhaps you have a different idea? Or maybe this is a non-starter. Didn't want to clutter PRs before asking.

Activity

  1. tlinhart commented on Oct 1, 2024

    @tlinhart
    tlinhart
    on 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).

    image

  2. abillingsley commented on Oct 10, 2024

    @abillingsley
    abillingsley
    on 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

    Screenshot 2024-10-09 at 8 26 38 PM

    Downgrading to 2.0.8 with no other changes yields the following

    Screenshot 2024-10-09 at 8 59 01 PM
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions