After weeks of rewriting the core aspect of Icinga for Windows – executing checks – we are happy to announce version 1.5.0 today. Why we changed the check handling? We are glad you asked and happy to share the new features!

Cerner Corp. is a supplier of healthcare information technology systems, services, and devices. The company, with $5.7 billion in annual revenue, empowers people and communities to engage in their own care. A key aspect of the business is surfacing data to enable their clients to make informed decisions about their healthcare. The 29,000 Cerner employees in 30 countries are on a mission to shape the healthcare of tomorrow.

You’re going to run into network issues during normal operations—in part because so many kinds of errors can cause noticeable problems in your network. Identifying the root cause of each issue is critical and to do so successfully, you want to make sure you have the right network troubleshooting solutions in your arsenal before wading in. This helps ensure you have a clear understanding of the scope of the problem before you attempt any network troubleshooting steps.

Traditional systems monitoring solutions poll various counters (typically simple network management protocol [SNMP]), pull in data and react to it. If an issue requiring attention is found, an event is triggered—perhaps an email to an administrator or the firing of an alert. The admin subsequently responds as needed. This centralized pull approach is resource-intensive. Due to the pull nature of the requests, it results in data gaps and data that may not be granular enough.

At Catchpoint, our mission is to provide customers with actionable data that will help them reduce MTTR and maintain a positive digital experience. We measure "from where the users are" to ensure the data reflects real end-user experience. As someone that's part of the Catchpoint on-call chain, this is extremely important to me. I do not want to be woken up at 2 AM because a server is misbehaving, only to find out that the application failed over gracefully and no users were impacted.

Excited to launch our first newsletter. We are delighted to have crossed 1.6k stars on GitHub, growing more than 30% last month. Catch up on what we're upto at SigNoz!

If Netflix was a series, it would be a blockbuster. Each season would be nothing short of dramatic to the chagrin of investors. Want to crunch some numbers? The video streaming service had an $11.5 billion valuation in January 2011. It had about 26 million subscribers at the end of that year. Ten years later, Netflix reported it had about 204 million subscribers and a valuation of over $220 billion. The Los Gatos, CA, giant made a staggering $25 billion in 2020 in annual revenue.

We recently released uptime monitoring, a pretty big addition to our set of features. Our customers have often requested it, and it was a logical next step for us to add uptime monitoring to our app. In today’s post, we’ll explain how we went from considering uptime monitoring impossible to build, to building it in a week. We’ll break down how seemingly over-engineering can really pay off in the end.

Network anomalies vary in nature. While some of them are easy to understand at first sight, there are anomalies that require investigation before a resolution can be made. The MITRE ATT&CK framework introduced in Kemp Flowmon ADS 11.3 streamlines the analysis process and gives security analyst additional insight by leveraging knowledge of adversaries' techniques explaining network anomalies via the ATT&CK framework point of view.

In modern cloud architecture applications are broken down into independent building blocks usually as microservices. These microservices allow teams to be more agile and deploy faster. Microservices form distributed systems in which communication between them is critical in order to create the unified system. A good practice for such communication is to implement an event-driven architecture.