-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to use on AWS Lambda #637
Comments
This works for me:
|
Any updates on this? Facing a similar issue. Ping : @akshayjshah |
Seems the issue is directly related to this one #328 |
If you are using the a standard The underlying issue is related to #328 -- unfortunately the Flush is not supported by |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm trying to use
zap
on AWS Lambda. With the following configuration:I am getting the following error when running it on Lambda:
when checking for an error on
logger.Sync
:So I tried changing the config to the following:
which now gives me another error (from the same call to
logger.Sync
):As far as I know, Lambda supports and recommends logging to stdout and stderr so I don't understand why it's not working. Is there a recommended way of fixing this?
The text was updated successfully, but these errors were encountered: