DevOps, Observability, Continuous Delivery, Test in Production, Chaos Engineering, and Software Ownership are all major themes in software development today, but why? In an ideal world, we get everything right the first time, nothing breaks, no one DDOS’ us, and the weather report is “Cloudy With A Chance of Meatballs.” Reality of course is different – and better, to be honest.
Improving MSP Incident Alert ManagementAs the big game approaches this Sunday, I’ve been thinking about the NFL’s introduction of instant replay and how it makes the league much more enjoyable! Whether you’re rooting for the Patriots led by Tom Brady … or the Rams, you can’t deny that instant replay makes every Super Bowl much more efficient and adds more clarity to the game.
Better employee experience drives better business outcomes1. The result? Technology is no longer the driving force of IT — instead, the end-users’ digital experience is the key to unlocking business value and driving ROI. The challenge? Mending the gap between traditional metric-based monitoring and the need for real-time, contextual data about the end-user experience. Here’s how to get started.
One of the biggest software development shifts of the past decade has been the emergence of the DevOps movement. There is a growing demand for DevOps Engineers, and organizations that have embraced DevOps practices are becoming more efficient in iterating through service delivery.
In a world where consumer-level computing technology has been largely dominated by Windows, many users remain unaware of the need for administrators to configure and maintain network hardware and environments based on the Linux operating system. But Linux in its various distributions and the Unix operating system from which they derive have for decades provided the backbone for the core systems that make consumer-level computing and indeed many aspects of daily life possible.
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.
