#ICYMI: In case you missed it, Sensu Go is here! And, as I wrote previously, one of the hurdles with migrating workloads from the original version of Sensu to Sensu Go are the changes in the internal event data structure. The existing handlers and mutators in the community maintained Sensu Plugins collection might not work as expected in Sensu Go because of these event data model changes. But friends, I’m here to tell you that we’ve got this problem licked.
The new 3.0.0 release of the sensu-plugin gem has opt-in logic to help you transition workloads using existing Ruby mutators and handlers from the Sensu Community Plugins collection. Once the community plugins you rely on are updated to require the 3.0 sensu-plugin gem, you’ll have a much easier time migrating your existing workflows without having to write your own mutator for event data. This post marks the first in a series in which I help folks migrate their workloads to Sensu Go. https://goo.gl/5njk1K