Software engineering teams that adopt “as-code” practices, like using configuration files and automated workflows instead of manual configuration and tools, gain major improvements in velocity. But even companies that enjoy the success of as-code practices for development and delivery lag behind in applying them to operational concerns like monitoring and observability.
Establishing your business’s online presence has become a fundamental need rather than a secondary step. In the wake of the 2019 pandemic, a large chunk of interaction, social and business, has escalated online. The user’s journey is as important as functionality to stand out in the crowded digital marketplace.
If you have worked in any part of the application delivery lifecycle long enough, there’s a very good chance you have directly used or been a consumer of Nagios. For a period of time in the early 2000s, it was the go-to solution for basic server monitoring and alerts. Fast forward 20 years and you might be surprised how many organizations still rely on Nagios for mission critical workloads — although not without a fair amount of duct tape and super glue challenges.
Observability is a new term that’s slowly entered the mainstream over the last two years. Today it’s used in the context of monitoring, but it’s much more than that. And it also goes way beyond visibility. So, in this blog, we set out to explore observability vs visibility and find out, what’s the difference? In a recent podcast, our friends at Riverbed neatly explained that seeing and observing are two different things, and can be compared to hearing vs listening.
Big data is transforming the relationship between companies and customers. Analyzing large amounts of data for marketing purposes is not new, but recent advancements in big data technology have given advertisers powerful new ways of understanding consumers’ behaviors, needs and preferences. Big data helps you optimize each customer’s demands and convert them into prospective purchasers.
We started the Feedback Week, because we wanted to hear what your thoughts around the Icinga Universe are. Whether it is about Icinga as a company, the products or the Community: in order to know what you feel and think about Icinga, we can develop the best possible monitoring tool for you. So here we are, recently finished off the second Feedback Week with a total of nearly 1300 votes all over Social Media and the Community!
Site Reliability Engineering (SRE) practice was established by Google nearly 20 years ago, and was popularized with Google’s monumental SRE Book. Everyone’s been attempting to follow that iconic path ever since.