Question: Exception Monitoring and Instrumentation? How to?

Not to go into exhausting debate/details but where can we tap into to get better (or really any) access to runtime exception monitoring? Yes we can write try catch code around every activity implementation and call out into logging code but that's literally the antithesis of SRP and occludes the intention of the code base with infrastructure concerns. Most middleware, in the lower case sense of the word, not the DTF meaning, have pipelines wherein we can tap into this type of thing to provide runtime advice to deployed logic be it for monitoring, tracing, exception logging, auditing, etc and usually in a straight forward enough manner. I mean at a minimum some call to a taskhub worker hosting application provided code delegate providing the exception allowing inspection would suffice.

I'm totally willing to admit I could be missing this somewhere but between the out of date wiki content and samples there's nothing showing this. Cursory reading of the code also appears that at best we simply get the exception message and stacktrace passed off to LogHelper and that is it thus committing the cardinal sin of exception hiding by not at least walking the entire exception hierarchy (can't tell you how much I hate seeing an error log stating "Something bad happened-See inner exception for details" [looks at Entity Framework]).

Anyone with practical advice from an operational perspective? (we've resorted to using container based proxy tricks to work around this apparent issue but that's an unfortunate hack that we're able to leverage, not a feature.