|
here's my log story: we couldn't figure out what the gently caress was going on because the genius that wrote these service components logged every single work step, including the ones that just said "sleeping for 1 second", so our logger was completely jammed with useless stuff. also stuff that was actually a problem was sometimes logged as info solution: lets stop logging so much trace poo poo! why not use the log level configuration per-environment to set this! it'll be great! what actually happened: all logging got disabled completely and now we can't tell what the gently caress is going on, but in a new and exciting way! also our logger is some home rolled poo poo that nobody knows how to install anymore so we have to hope it never breaks
|
#
¿
Feb 26, 2019 01:16
|
|
|
|
| # ¿ May 13, 2024 22:54 |
|
|
lancemantis those were some good posts that I can relate to a lot i spent 2+ hours this week on calls while various auditors asked to "take a screenshot of the code that would log an error" so that "we can check that data flows from system a to system b" they got some poor fucker to sit there grepping logs while the screenshot that too. they asked me if I could 'show them a log of a message' and I said "we don't retain them because that would be pointless" they also implied that we should archive all logs indefinitely so they could screenshot them from 6 months ago which is the last time we had an actual error what the actual gently caress
|
|
#
¿
Mar 2, 2019 17:33
|
|