Circonus’ new Linux host monitoring dashboard is the most comprehensive host monitoring available in the market – yet also extremely easy to install and use, allowing users to more efficiently and accurately monitor their Linux hosts and diagnose and resolve issues. The turnkey dashboard uses our new Circonus Unified Agent (CUA) – a single collection agent that consolidates all host and services monitoring.

One year ago this month, I wrote a post about how the COVID-19 pandemic was going to greatly accelerate the pace of global, digital transformation. How literally overnight we were being forced to find new ways of working, meeting, shopping, managing healthcare, and even staying entertained. And how there would be a tremendous surge in demand for video conferencing, home delivery services, online learning, eCommerce, media streaming, eSports, and telemedicine.

Histograms (specifically the persistence of detailed information about the distributions of sampled data) have become increasingly important in the monitoring and observability industry. They are powerful tools that afford robust analysis while maintaining excellent economic value. However, there are a few challenges that are awkwardly technical in nature, but almost all of these challenges come down to compatibility of representations.

We’re excited to share today that we’ve partnered with Cloudbakers, a Google Cloud Premium Partner, in an exclusive partnership in which Cloudbakers will serve as the Google Cloud Platform reseller for Circonus, and Circonus will serve as the exclusive provider of GCP monitoring and analytics to Cloudbakers’ customers.

At Circonus, we love hearing (and sharing) how our customers are using our platform to tackle their monitoring challenges. It’s not because we want to congratulate ourselves. Rather, it reminds us that we have to continue listening to the pains that organizations — customers and non-customers alike — are having, so we can continue to enhance our platform with the capabilities they need. This is the approach we have taken since we built Circonus.

If you’re spending more than you expected on your Kubernetes deployment, you’re not alone. Many Kubernetes operators are experiencing higher Kubernetes costs than what they had predicted. That’s because, like many aspects of Kubernetes, identifying how to manage or lower costs can be challenging. In this article, we provide 5 essential tips for how you can achieve a more cost-efficient Kubernetes deployment.

The time has arrived to upgrade to TLS 1.2, if you have not already done so for any of your systems. At Circonus, we will be dropping support across our platform for all connections using TLS versions less than 1.2 on January 21, 2021. Virtually none of our customers will be impacted by this change, as this has been in the works for a very long time, and most customers will have made this transition already.

Welcome back to our series of Kubernetes monitoring guides. In part 1 of this series, we discussed the difficulties of managing a Kubernetes cluster, the challenges of conventional monitoring approaches in ephemeral environments, and what our goals should be as we think about how to approach Kubernetes monitoring.

Kubernetes can generate millions of new metrics every day. One of the most challenging aspects of monitoring your cluster’s health is filtering through which of these metrics are important to collect and pay attention to. The best way to approach this challenge is to first understand which high-value signals just about every Kubernetes operator should be concerned with. This is the approach one of our customers, Major League Baseball, took.

We recently surveyed 200 Kubernetes operators about their Kubernetes deployments, including their top challenges and goals as it relates to Kubernetes overall as well as monitoring specifically. Why? We wanted to better understand what capabilities were essential to our monitoring solution that could inform our product roadmap and better equip organizations to tackle their Kubernetes challenges as well as fulfill their Kubernetes goals.