how to log tracing::error with a custom message

[evbo]

I only receive the following non-descript error logs, despite calling tracing::error! with more specifics:

{
    "time": "2024-04-26T23:09:32.311Z",
    "type": "platform.initRuntimeDone",
    "record": {
        "initializationType": "on-demand",
        "phase": "init",
        "status": "error",
        "errorType": "Runtime.ExitError"
    }
}

Example of how I call tracing:

let err_info = format!("Something very very bad happened");
tracing::error!(name: "invalid_input", "Invalid input: {}", err_info);

[bnusunny]

This is a Lambda system log. Your function crashed during init and didn't reach your logging code.

[evbo]

@bnusunny you're very right about that!

So I set the new "advanced" log level to Error thinking I would see errors... but only after setting it to Info did it finally print the problem:

/var/task/bootstrap: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by /var/task/bootstrap)

Why would that be an INFO log?!!! :)

Or is this an AWS bug I'm ranting about?

[pbintcha]

@bnusunny you're very right about that!

So I set the new "advanced" log level to Error thinking I would see errors... but only after setting it to Info did it finally print the problem:

/var/task/bootstrap: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by /var/task/bootstrap)

Why would that be an INFO log?!!! :)

Or is this an AWS bug I'm ranting about?

I fix this GLIBC_2.28 not found error by updating the lambda runtime to Amazon Linux 2023

[evbo]

@pbintcha I fixed it by switching to musl arm target during build (instead of using --arm64). Cool idea upgrading I'll try that.

[bnusunny]

Newer Lambda runtimes are based on Amazon Linux 2023 with glibc 2.34. Older Lambda runtimes are based on Amazon Linux 2 with glibc 2.26. You can find out the OS version for each runtime here.

[github-actions]

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.