What DB fields would you say are sometimes left out (or forgotten) when people make the tables for their Logging?
What about logging when a user does something unexpected? Or, meets an unexpected situation? Or, when something takes a little longer than it should? Or, when a user’s IP Address is changing?
There seems to be this in-between area where sometimes an ‘error’ isn’t really like – you know – an ERROR…. But, it’s definitely an error.
So, I am playing around with how to break down items that are true errors, items that are api errors, items that are user/app errors … sql errors … data errors … and, THEN the caught logic errors.
I find that the tables have ways of being related to the smaller mechanisms of the app, and am torn between all the ways of relating this data.
I don’t want to look at my DB when this is over and see 10 extra tables added, but it’s looking that way.
Anyone have any examples or thoughts that might help me finish thinking this through? Could be a fun conversation.
I want the app to sort of …. tell the story of its existence…everything it saw and everything that happened.
submitted by /u/naynay447
[link] [comments]