DevOps teams and site reliability engineers (SREs) contend with a never-ending flood of notifications and alerts about outages, potential threats, and other incidents. Companies rely on their DevOps teams to not only keep abreast of all the notifications but also to identify and prioritize the critical alerts and resolve problems in a timely manner. Yet in 2021, International Data Corporation (IDC) reported that companies with 500-1,499 employees ignored or failed to investigate 27% of all alerts.

Sensu is the complete cloud monitoring solution for observability at scale, designed to give you rich insight and ensure that you know what’s going on everywhere in your system. With true multi-tenancy, an enterprise datastore that keeps pace as you scale, and streaming handlers to process all those events, you can rely on Sensu for cloud, container, and application performance monitoring that provides deep visibility into your entire infrastructure.

To provide proper visibility into the health and status of your systems, observability tools require access to the internal and external services you’re using, and Sensu is no different. In the past, this could mean exposing sensitive authentication credentials like usernames and passwords with local environment variables or even by including the secret information in your monitoring configuration.

Mutual transport layer security (mTLS) is an important subject among security, reliability, and engineering professionals who need to secure API communication as well as communication between machines and the applications and services they run. And for good reason: in 2022, the global average cost of a data breach was US$4.35 million, and almost double that in the United States at US$9.44 million.

Sensu offers a complete solution for infrastructure monitoring and observability, designed to give you visibility into all of your important infrastructure components, including containers, applications, traditional server closets, and the cloud. Sensu Go is a commercial product based on an open source core that is freely available under a permissive MIT License and publicly available on GitHub.

Monitoring any type of resource can be challenging. But Kubernetes monitoring is a special kind of challenge. Not only are there a variety of different Kubernetes layers and resource types to monitor, but collecting monitoring data from Kubernetes can be difficult if you use a managed Kubernetes service that limits your access to the underlying infrastructure. For all of these reasons, Kubernetes monitoring requires a different approach.

The way businesses obtain infrastructure has changed dramatically over the past decade, as Infrastructure-as-a-Service (IaaS) has taken the place of self-hosted infrastructure for most IT deployments. At the same time, it has become common to build complex infrastructures that blend components from multiple providers – such as two or more public clouds (aka. multicloud infrastructure) or mixing an on-prem data center and a public cloud (aka. hybrid cloud infrastructure).

A Two Sigma engineer explains why we built Tensu, an open source TUI (text user interface)-based program for interacting with Sensu Go’s observability pipeline and backend API. In this article we will be putting a spotlight on Tensu, an open source terminal-based dashboard for interacting with and responding to events from the Sensu Go observability pipeline and backend API.

ICYMI: in Part 1 of this blog post, I introduced Sensu Catalog Integrations, one of the three components that make the Sensu marketplace work. In this post, I want to cover the second piece, the Catalog API generator. This is the tool that consumes the github.com/sensu/catalog repository content and renders static http API content the Sensu web app can consume.

ICYMI, the recent release of Sensu 6.7.0 introduced the Sensu Integration Catalog – an open marketplace for Sensu Go. Along with the release, we also hosted a webinar highlighting how the Sensu Integration Catalog unlocks self-service infrastructure monitoring. In the webinar, we talked about the “what and why?” – what problems does the Catalog solve, and why we decided to solve them with a marketplace.