What should be included in the state-of-the-art error and exception handling strategy? [closed]

Answer 1

I don't intend to win bounty but here are some strategies that I have used and were well received:

1. Extracting informatin from sub-components and mapping them to functional units helped our business analysts and end-users to understand the errors better

2. Assigning a business priority level will help depending upon the domain you are operating.

3. A Seperate Error Viewer App helped us view the errors before they were reported so my teams can start fixing them.

4. System level exceptions are better when they are not messed with.

5. Async logging of errors will help a great deal in the overall strategy and design.

6. Create Domain-driven error strategy: meaning the errors whould correspond to failure of some business logic. Of course, most should be handled by developers, but there are certain scenarios that you may run into if you are working on message routing between various enterprises in trading engines, etc