Event logging with fluentd: How we did it

Hello! I’m Baran, working as the Head of Engineering at Volt Lines. Since we are disrupting our way of how we make things almost daily on Tech side here in Volt Lines, we are learning lots of stuff while we are having issues on the road. We thought that sharing our best practices will be helpful for you. I’m holding the Engineering team’s flag by writing our first blog post about what we did for our Operational Disturbance module under our Mission Control app (and Burcu, aka our Product Manager, is summarizing what we had done for the third quarter of the year here). Let’s dive into details.

We’re a tech company that runs mostly on data. All the decisions that we make are data-driven, and for that reason, it’s super important to collect this data first. Aside from gaining flexibility in making decisions, monitoring allows you to see the potential problems before they happen and improve what has to be improved to have better output.

I’ll explain through an example to help you understand better. Recently, we needed to see whether our drivers take necessary actions during the correct time or not, so we wanted to implement a sample dashboard to see the results. The sunny side of the picture: We only had three days to make it work. We immediately had a quick meeting with the team and focused on a few options:

To continue reading, please visit: Volt Lines Official Blog