Timeline for Making logging more efficient and useful by categorizing data (and virtually not writining messages anymore)
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 20, 2017 at 17:46 | comment | added | t3chb0t | Yes, I can have gigabytes of logs and I really hope never have to read them (like you hope never have to make use of your insurance policy) but when something happens, you are glad you have it and you can bring it back online within minutes and not hours or days which sometimes would be a catasthropic scenario. Logging doesn't cost a penny nowadays ;-] | |
| Nov 20, 2017 at 17:43 | comment | added | t3chb0t | Not necesserily slow. I measured it many times and compared to the processing that my services need to perform, the impact of logging is barely noticeable but the data that gets logged is invaluable when something goes wrong and the service needs to run 24/7. I of course don't long everything like really everything, this would be crazy ;-) Just enough to be able to take proper measures if necessary. I have the impression that the message-only-logging is just a relict of some old times when you only had text files. Now with super-fast json/sql-databases etc why shouldn't I log more useful data? | |
| Nov 20, 2017 at 17:30 | history | answered | Simon B | CC BY-SA 3.0 |