I come from a world where strategy is best kept secret. Whether it be from a company who has a codename for literally everything, or the competitive culture of playing and coaching D1 athletics, confidentiality became a required skill. Meetings, trainings, code reviews, scouting reports… anything of significance happened behind closed doors. In other words, definitely not open source.

While Logz.io provides Kibana — the ELK Stack’s visualization tool — as part of its service, a lot of users have asked us to support Grafana. One of the leading open source visualization tools today, Grafana has some added value when compared to Kibana, especially around visualizing time-series data.

Errors. We all cause them all the time, which can make it difficult to figure out the person or team who should be responsible for fixing individual issues. Time that could be spent resolving an issue is instead spent tracking down who should be handling it and what it’s even about. This is a waste. It balloons time to resolution, often from minutes to hours or sometimes even days.

We’ve all been there — you’re on-call, fast asleep at 3 AM when suddenly, in comes the alerts–in overdrive. Your system is notifying you of some sort of abnormal behavior, but with all the alerts and data coming through, its difficult to figure out what your system is trying to tell you. Is there potential malicious behavior? Did someone write faulty code? Is it an important issue or can it wait? Is it nothing at all?

Every single app — large or small, open source or not — has room for improvement when it comes to performance. This is why we created Skylight for Open Source to give open source contributors the tools they need to find these issues. Over the next week, we'll show you three different open source apps running on Skylight, each with their own unique performance challenges, varying in complexity.

We’re glad to announce that StackStorm Vagrant box and Community OVA are available for general use and included as installation method in StackStorm Docs.

In order to successfully implement continuous testing, DevOps teams need the right mix of tools, people, and processes. Most importantly, they need fast and frequent feedback loops to guide their testing efforts. Learn how this can be implemented.