I have tried to figure out some kind of unification between "collecting error state in a function", "logging error state", and "return error state to a parent".
replyI haven't found any satisfying solution to it all; collecting information for logging vs information that a caller would want... I've been meaning to investigate tracing_error to see if it brings it all together.
Regardless of language - if you find a good, clear answer - blog the hang out of it - I for one have been searching for the right way to manage this, and it's not (yet) clearer - other than what I've said so far
replydeleted
replyYou’re supposed to bubble errors up to the level that can appropriately deal with them? You don’t need to log them each step of the way.
replyYeah - but that's the same as my final point - you have to know who is supposed to manage the error/log - all the way up (and down) the call graph
replyedit: I've just finished debugging a multi system chain - FE -> SNS -> SQS -> Lambda -> DynamoDB -> Lambda -> Webhook -> My poor code
My code has multiple layers - and I was trying to find where in the very long chain of calls the data was being mangled
It turned out that there was an unlogged error, which was mismanaged by a caller - there's no shade here - the caller was handling the error how it was designed to, but by not logging that there was an error - it took a minute to understand.