5 ms·
I've always preferred levels of logging rather than these arbitrary names (what's the difference between trace and debug, and which one is lower level?). Give
by hota_mazi 8y ago
I've always preferred levels of logging rather than these arbitrary names (what's the difference between trace and debug, and which one is lower level?).
Give me three levels of logging, 1, 2, and 3, and then warning, and error. Maybe allow to mix and match them, if this makes sense (the typical nomenclature makes them all mutually exclusive, which is dumb).
There are your five levels.
- delinka 8y agoDepending on your Coding Culture, you order them based on "priority" (FATAL would have priority over all others, and therefore numbered as 1), or "importance" (FATAL would be most important, and therefore numbered 5.) Alternatively, each is a flag in a number so that they can be combined, with FATAL being 1 or 16 depending on priority vs. importance. I would argue that the names do indeed suffice to tell you their "level" - TRACE is the noisiest, least important, least priority level. DEBUG is next, followed by INFO, WARN, ERROR, FATAL.
- zoomablemind 8y agoCuriously, in the days of OpenVMS this was called 'severity' level and was a global system concept [0] related to status code of execution. Info, Warning, and Error are degrees of Success or Fatal/Severe. The status would then be logged in a structured manner that shows a facility code, serverity, message. 0. https://h41379.www4.hpe.com/wizard/wiz_3582.html https://h41379.www4.hpe.com/wizard/wiz_3582.html