Middleware-sample-logging to have a switch not to print uncaught errors

[lkhari]

This is a Feature Proposal

Description

• Middleware-sample-logging print all uncaught lambda errors. In certain sitatuations you don't want the uncaught errors to log out an error, like in the context of Step functions and Lambdas tied to appsync. I'm suggesting being able to configure if it does or not.

Similar or dependent issues:

• Support custom loggers #98

[theburningmonk]

@lkhari while I think it's a good option to have, I don't understand why you wouldn't want an error log message in the case of Step Functions and AppSync resolver functions. Can you clarify?

[lkhari]

An example is, on the site i'm working we have very little frontend validation. So often the requests come to the backend through appsync and aren't suited due to incorrect dates etc. I can't return the message back through graphql since it's expecting a specific entity, so I throw a validation error.

I use error logging as more high priority issues which require fixing urgently, which these validation errors are often not an issue so i log them as warnings.

That's my reason, but I can also see people wanting to be able to format the message diffferently like in issue #98

Note: if you have a better way of returning validation errors, i'm happy to hear.

[theburningmonk]

mm.. I see, the problem here is that when something does go wrong (not related to validation) then you also won't have those error log messages, which captures the invocation event, etc.

#98 is a different case, the core problem (here) is that they have a specific logging convention so want to override the log message itself & also increment a custom metric, something that they'd be able to do easily with a custom logger.

[lkhari]

Yea, that is true. I think, to be honest, if you have made the decision to turn off the error catching in this package, then you most likely going to understand that you must handle errors in your code.

[theburningmonk]

fixed by #146