Catalog product

Sumo Logic: Unlocking Self-Service Monitoring with Sensu Integration Catalog

Introducing the Sensu Integration Catalog – a market-like UX to simplify new user onboarding and deploy production-ready surveillance in minutes. The Sensu Integration Catalog is also an open marketplace where new and existing users can contribute by sharing Sensu configurations. Keep reading to find out more!

The modern era of cloud computing has democratized access to software products that deliver “turnkey” experiences, getting users up and running quickly, solving real business challenges in minutes. This ease of adoption has led to more companies consuming more software solutions than ever before, which has created a new challenge: how do you integrate all these products and services? This challenge is as true for sales teams that need integrated CRM solutions as it is for DevOps and SRE teams that need integrated observability solutions.

These days, almost every product we use to do business integrates with at least one other product or service. Some products only require a fixed number of integrations which can be configured when onboarding a new user or from the product or service settings menu. For products that need to integrate with dozens or hundreds of third-party systems, the seemingly inevitable outcome is to provide a “marketplace-like” user experience for discovering and activating integrations.

Here are some examples :

Even my text editor has a market!

(Microsoft Visual Studio Marketplace)

Introducing the Sensu Integration Catalog

The Sensu Integration Catalog is a self-service marketplace for turnkey integration with the products and services that power your Business. The catalog is packed with integrations for monitoring the systems you rely on (eg infrastructure and application monitoring) and integrations with your systems of record (eg chat, incident management, analytics) .

For existing Sensu users, this may not seem like news at all. After all, Sensu already provides integration with hundreds of third-party systems through over 500 community-developed Sensu plugins from hundreds of contributors. Sensu is also compatible with thousands of plugins, libraries and exporters from the Nagios, Telegraf, StatsD and Prometheus ecosystems (as well as many others). So Why does Sensu need a market? For several reasons :

  1. Better knowledge/discovery of available integrations (in-app + docs + website).

  2. Provision of recommendations/baseline configuration (i.e. how to use plugins) to facilitate the evaluation and deployment of Sensu solutions.

Realizing Sensu’s Original Vision

Since forming Sensu Inc and innovate on the next-generation Sensu platform, which has become Sensu Goour goal was to take everything from the original Sensu and make it Easierdo it portable (e.g. via monitoring reusable templates as code) and then make it self-contained (although that’s a blog post for another day). One of the main steps we had in mind in 2017 was to create an open market for self-service monitoring. Here is a slide from our original fundraising presentation:

We’ve been building the platform to enable the “add to watch” button since 2017. At the time, we were inspired by the growing popularity of Slack and the Slack buttonwhich prompted this comparison.

We didn’t just want a marketplace of integrations that users could manually configure and enable – we wanted to create a platform that could fully automate the entire monitoring lifecycle, from collection to processing. Fast forward to today’s launch of the Sensu Integration Catalog and we’re excited to bring this original vision to fruition.

What distinguishes Sensu’s market implementation from alternatives is not only that it is an open market (see: – the solutions available on the Sensu Marketplace are truly turnkey pushbutton integrations.

With the Sensu Integration Catalog, the install button doesn’t redirect you to documentation or further instructions for setting up collection – it configures everything for you and enables real-time collection.

Under the covers, the integrations in the Sensu integration catalog are watch-as-code models. A `sensu-resources.yaml` file containing Sensu API resources and a `sensu-integration.yaml` manifest which configures user input that should be overlaid on Sensu resources (e.g. updating a default configuration setting, etc.).

At the beginning of 2020, we launched this idea of ​​a public curation of Sensu solution templatesand these efforts allowed us to refine our thinking on how to achieve our initial vision, which resulted in the solution we are launching today.

Use cases and next steps

The primary use case for the Sensu Onboarding Catalog is to simplify the onboarding of new users. This includes net new Sensu users, as well as new teams within organizations that are already using Sensu. Getting started with Sensu should be simple enough that anyone who can install a monitoring agent can also deploy a complete infrastructure monitoring solution in minutes. And this solution must integrate seamlessly with their existing tools and services. This onboarding experience should look like this:

  1. Download and install Sensu (or access a new namespace in an existing Sensu deployment by your Sensu administrator)

  2. Deploy Sensu Agents to your multi-cloud infrastructure (e.g., on-premises servers and VMs, public cloud compute instances, Kubernetes pod sidecars, and daemon sets)

  3. Enable integrations with your existing systems of record using the Sensu integration catalog (e.g. Pagerduty for incidents, Slack or Microsoft Teams for basic alerts, Ansible Tower for self-healing, etc.)

  4. Enable monitors for the services you rely on to run your business using the Sensu integration catalog, including: host monitoring (Linux, Windows, Unix, etc.), cloud platforms (AWS, GCP, Azure, Kubernetes, etc.), third-party services (by example, NGINX), etc.

  5. Profit

Many Sensu customers are large enterprises with dozens or hundreds of product teams that need access to monitoring and observability solutions. In these organizations, our customers have requested more tools to help them provide “self-service monitoring” to their customers (other teams within the organization).

Register for our next webinar!

If you want to learn how to set up production-ready monitoring in minutes with the Sensu Integration Catalog, register for our on-demand webinar. You will receive the video when it becomes available on April 28, 2022.


Want to try the Sensu Integration Catalog? To visit to download Sensu Go version 6.7.0 and get started today!

Pay particular attention to the sensuous blog in the coming weeks, as we’ll have a lot more to say about the Sensu integration catalog, including:

  • Roll your own Pingdom with Sensu integration catalog (use cases)

  • Designing an Open Marketplace for Sensu: An In-Depth Technical Analysis of Sensu’s Integration Catalog Design and Architecture

  • How the Sensu community can contribute to integrations (with NEW SWAG!)

  • New integration announcements (many more to come!)

  • An update on Sensu Plus and the integration between Sensu Go and Sumo Logic Observability suite

Complete visibility for DevSecOps

Reduce downtime and move from reactive monitoring to proactive monitoring.