A typical workday for your IT team may go from calm to all hands on deck. When a problem occurs on your servers, you may not know the cause right away, but before you can start figuring it out, customers are blowing up your phone and monitoring systems. Everything you do from this point has a timestamp attached to it. If you wait five minutes to put up a status page, that could equal 100 people who have submitted tickets. The longer you wait, the more people you will have to get back to.

We already wrote about monitoring posgresql queries, at the time we thought that we completely understood how PostgreSQL works with various server resources. Working regularly with the statistics of PostgreSQL queries, we noticed some anomalies and decided to dig a bit deeper for better understanding. Through this process, we found that while the behavior of postreSQL is kind of strange at first glance (or at least very peculiar), the clarity of its source code is quite admirable.

Icinga is coming to Berlin for the 3rd time next week, and we are super excited to share the latest developments with you. And of course to meet again with our awesome community and have a couple of G&Ts :) If you can’t make it, our first Icinga Camp New York happens on March 16th the week after!