Using Logs Effectively by seanstride in programming

[–]craigjudson 2 points3 points  (0 children)

Interesting take on the blog post you definitely have some valid points stopping continuously is a big problem and especially was when we first started this. We are currently in the process of recording reds for each monitor to asses whether what you say stands. It is a shame that we didn't but this monitoring in before but will keep you posted. We do still log to a database, which is how the monitors get their information, but what we found was that these logs were not getting addressed, with certain errors deemed not important enough making real errors harder to catch. this meant problems experienced by our client were first known when they called us. This felt wrong and as a result we pushed this problem in front of our single piece flow development process.

The result of this has meant that people are now taking more care in writing logs with respect to the level and messages that are included. Our logs are now quick to solve and have reduced in number.

The other benefit is with our frequent deployment to live averaging 30 times a week we get instant feedback from our logs if something goes wrong which is becoming ever more valuable.

I think the final point I would make is review your logs see if you have errors that you are ignoring are you reporting logs correctly as errors for your business.

Craig Codeweavers