When it comes to developing software we use the adagio: You built it, You run it, You love it. Same should hold for all the -ilities or non-functional requirements. So, one should love their logging.
One of the subjects that we did not really touch yet in our podcast is non-functionals. Today we take a closer look at logging. An aspect that typically fills some of the non-functionals or -ilities. Love your logs and Love the people after you.
For the first time in the history of the bol.com Techlab podcast, we are able to provide 5 free eBooks about today’s topic. Because that was the starter for this episode. We were contacted by the publisher of this book if we were interested in an episode about logging with the author of this book. So, we came up with the idea to combine it with the bol.com way of logging. During the episode, we will explain what’s needed to obtain one of these codes.
We start our logging journey talking about moving away from monoliths. This brings a challenge for logging and tracing. Next, we dive into the question: Logging for logging vs logging for alerting? All this is on the receiving end. What about the production of logging? What are the best practices for producers? And we wanted to learn how organisations deal with demanding teams. Last part is about the balancing act of engineering. And of course, we have our famous closings round: the most important takeaways.
- Phil Wilkins – has spent over 25 years in the software industry. Is a Senior Consultant and Tech Evangelist working for Cap Gemini. Specializing in cloud integration, APIs, and related technologies. Phil is TOGAF certified. Recognized by Oracle as an Ace Director (independent technology advocate) for his contributions to the integration and PaaS community. Has written a few books including the one we talk about today: Unified Logging with Fluentd.
- Tjebbe Vlieg – System Engineer, in his 4th year at bol.com and really enjoying it, strong in logging, monitoring and metrics.
Peter Paul van de Beek