Timeline for Should I use a global logging variable?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 17, 2023 at 7:10 | comment | added | Matthieu M. | @SimonCrase: In my previous company the logging system I had made was used, in part, for "audit" logs which were tracked for regulatory purposes. Despite being called audit "logs", I always considered it a mistake to reuse the logging system for them: having been built to be unobtrusive, the system would discard logs if the queue got too full (with QoS, but still). If there are requirements for certain events/metrics to be tracked, I would argue a dedicated system is probably a better choice: different trade-offs need to be made. | |
| Jul 16, 2023 at 23:29 | comment | added | Simon Crase | "Logging is not part of the purpose of the application and should not influence the function of the application." Logging may be part of the requirements. I worked for a company that produced safety critical systems, and lawyers aborted at least one lawsuit when they showed the other side a transcript of the log-file (Our former customer claimed that we hadn't detected certain events; the log-file showed that there operator had been overriding warnings for 2 weeks...). | |
| Jul 16, 2023 at 18:18 | comment | added | Matthieu M. | @Basilevs: Those are fairly orthogonal, though it's easier to reconfigure dynamically with a global registry. The 3rd library I did had listeners, so it could be setup to log to file or to a distant server. The 4th doesn't, I don't need any yet... or for the foreseeable future. | |
| Jul 16, 2023 at 18:07 | comment | added | Basilevs | Nice! And no dynamic configuration/listeners? | |
| Jul 16, 2023 at 17:37 | history | answered | Matthieu M. | CC BY-SA 4.0 |