Filters, the mechanism for allowing and denying events to be handled, have been given a refresh in Sensu Go. These new and improved JavaScript filters give you a way to express business logic through filtering, giving you more awareness of your environment, reducing alert fatigue, and improving performance. In this post, I’ll share what’s new with filters, using examples in Sensu Go. (If you haven’t already, you can download it here.)

As part of our mission to improve operator experiences, we’re pleased to announce Bonsai, the Sensu asset index! Bonsai makes discovering and sharing Sensu solutions easier than ever before, and already includes popular integrations like the Sensu Slack, InfluxDB, and PagerDuty handlers.

Wherever you’re at in your monitoring journey, you’ve probably used Nagios at one time or another. Love it or hate it, a legacy tool like Nagios played a critical role in establishing monitoring as a practice and helped train a generation of operators who required visibility into system dependencies and performance.

In case you missed it, Sensu Go became generally available in December 2018, and commercial support for Sensu Go became generally available just last month. With these major milestones now in our rearview mirror, it's time to help our customers reach their own milestones of migrating from Sensu to Sensu Go.

Even if you haven't heard of data described as a "time-series," you've probably seen examples out in the wild. As the name suggests, a time-series is a representation of an event over a period of time. That could mean representing many different changes: your application usage data, such as error rates over time or the growing number of activations per day.