Feature request: Ability to test filters (and possibly mutators) ad-hoc

[cjchand]

One of the more common questions seen from the community involves debugging and understanding filter behavior. It would be very helpful if we were able to have an ad-hoc means of trialing filters against a given check result JSON, instead of having to enable significant levels of debugging in sensu-server (which might not be practical/possible in production).

Expected Behavior

I can foresee a couple of ways of going about this:

1. A hosted service, ala Grok Debugger, whereby people can toss in a check result JSON and relevant sensu-server config, which then get passed through the actual filter code to see what the end result is.
2. A CLI command added to sensu-server that takes in a check result JSON, then uses the on-box sensu-server config. If we went this route, we could potentially even add support for mutators, as well.

Current Behavior

Currently, there is no means of accomplishing this (at least to my knowledge - and that of other community members).

Possible Solution

See "Expected Behavior" section above.

Steps to Reproduce (for bugs)

N/A

Context

• Filtering-related questions are some of the most common in the Sensu Community Slack
• There a many blog posts, Gists, etc covering the topic of demistifying filtering

Your Environment

• Sensu version used: Any
• Active Sensu extensions (e.g. WizardVan 0.1.0): N/A
• Operating System and version (e.g. Ubuntu 14.04): Any
• Transport and runtime versions (e.g. RabbitMQ 3.6.2 on Erlang 18.2): N/A