On our journey to democratize monitoring, we are proud to have open source at the core of both our products and our company values. What started as a project out of frustration for lack of existing alternatives (see anger-driven development), quickly became one of the most starred open-source projects on all of GitHub.
Modern applications are changing, and traditional testing practices are no longer up to the task. Learn more about the changing landscape of QA and how Chaos Engineering provides the necessary framework for testing modern applications. Chaos and Reliability Engineering techniques are quickly gaining traction as essential disciplines to building reliable applications. Many organizations have embraced Chaos Engineering over the last few years.
We created the Fleet Project to provide centralized GitOps-style management of a large number of Kubernetes clusters. A key design goal of Fleet is to be able to manage 1 million geographically distributed clusters. When we architected Fleet, we wanted to use a standard Kubernetes controller architecture. This meant in order to scale, we needed to prove we could scale Kubernetes much farther than we ever had.
By design and tradition, telecoms networks are built to last. But in a world where the rate of innovation seems to be accelerating, the end result is that a lot of legacy infrastructure needs to keep pace with, and accommodate, multiple ‘next generation’ phases. How long this can be maintained before the imperative to rip and replace becomes impossible to ignore is the multi-million-dollar question.
A few years ago, we realized that spending in our AWS product test environment had jumped significantly from one month to the next. We drilled down into the issue and traced it to some RDS database instances that had been spun up to test new product features. No one realized that these expensive instances were left running after the tests were complete, and subsequently racking up charges for several months.
That’s the question ops personnel have been asking for decades whenever something goes wrong in the production IT environment. Everything was working before, so the reasoning goes, and now it’s not. We have an incident. And to figure out what caused the incident – and hence, to have any idea how to fix it – we must know what changed. There’s just one problem with this approach. What if everything is subject to change, all the time?
PuTTY is a free program (MIT license) for x86 and AMD 64 architectures (now in experimental stages for ARM). It was developed in 1997!, by Simon Tatham, a British programmer. In this blog, we have been reviewing this useful program for several years, and even the great Pandora FMS team has confirmed it just now in 2020, in the list of network commands for Microsoft Windows® and GNU/Linux®. What if it deserves its own article? Read and judge for yourselves.
Serverless. It’s likely you’ve already come across this term somewhere, but what exactly does it mean? Well, to start, serverless, or serverless computing, doesn’t really mean there aren’t servers involved, because there are, rather it refers to the fact that the responsibility of having to manage, scale, provision, maintain, etc., those resources now belong to cloud providers, such as AWS Lambda, Google Cloud Platform, Microsoft Azure, and others.
Splunk is a machine data platform with advanced analytic capabilities that allows anyone to get valuable insights from their data. With unlimited use cases, you can leverage SPL to run any analytics you want. SPL has been supporting native machine learning capabilities for some time now. All you have to do is install the Splunk Machine Learning Toolkit (MLTK) and you are good to start predicting !
