Our community is more than just helping with questions, sharing experiences and tailoring monitoring together. We’ve grown so much in the past 10 years that we always seek to improve the conversation. You’ve seen our many Icinga Camps, keep following our social media channels, engage with developers on GitHub, read our blog … one thing is gladly missed: Our very own discussion platform which combines a forum with a mailing list and also enables quick chats known from IRC channels.

Back in the days of the wild wild web (www) and post JQuery era, one web framework stood above all others: AngularJS. A “ring to rule them all”, AngularJS consolidated quite a few micro-frameworks and provided many extensibility points of expansion if needed. Over time though, many performance and architectural questions began to arise, to the point of no return – when the guys @Google decided to migrate from AngularJS to Angular (a poor naming decision).

When developing PHP applications, error logs are under-used because of their apparent complexity. PHP error logs are helpful, especially when configured and used properly. While there are advanced tricks to truly squeeze every last drop of utility out of error logs, this article will cover the basics of configuration and the most common use cases so you can get up and running quickly.

Even after being in business for 9 years, I still wanted to keep everything: every email, every note, every design draft or mockup — all the small things that helped Monitive evolve into what it is today. Storage is not an issue these days, and by the looks of where technology is headed, that trend will not change anytime soon. There’s just one catch.

Kubernetes clusters can manage large numbers of unrelated workloads concurrently and organizations often choose to deploy projects created by separate teams to shared clusters. Even with relatively light use, the number of deployed objects can quickly become unmanageable, slowing down operational responsiveness and increasing the chance of dangerous mistakes.

Today, we are excited to announce PagerTree now officially supports Broadcast Responses! With PagerTree’s Mass Notification System (MNS) your organization will be prepared to easily communicate with speed and reliability during critical events.

The secret to exceptional network management is periodically identifying and diagnosing network problems. Putting your experts at the network operations center (NOC) all day watching for a device to go down isn’t the best use of your workforce’s time. There has to be a smarter way to view potential network pitfalls without being glued to the chair in your NOC.

Stop the presses! We've just added a small but really cool new feature to your Honeybadger account: search key autocomplete. You've always been able to search your errors by params, session and other nested fields. It's easy to find all errors where params.user.name is bob. But there's a catch. You had to know beforehand that params.user.name exists, and you had to type it in manually. This made it really difficult to do on-the-fly exploratory searches.

You know the saying: "better safe than sorry." In information technology, that phrase usually refers to backups and disaster recovery — having redundant data and infrastructure in place to help mitigate risk when something inevitably goes wrong.