ErrorEventContext refactored to ?
Cantor, Scott
cantor.2 at osu.edu
Mon Apr 28 14:02:30 EDT 2014
My intention with the error handling is that we basically do two things
from here:
- start checking log levels for sanity, I think we'll need to turn quite a
few things up or down
- replace any generic events that occur in significant cases with specific
events
We could certainly do all kinds of complex information tracking to attach
context to errors, but I think what we want to do is just make sure every
significant profile happening has its own event ID and just let the
templates switch on that (and/or map different events to different views).
Events that only happen when things are misconfigured badly or when code
is broken can stay generic and not really matter much.
-- Scott
More information about the dev
mailing list