Process your observation data

or click any element in the pipeline to jump to it.

In the process stage, Sensu executes handlers.

In the process stage of Sensu’s observability pipeline, the Sensu backend executes handlers to take action on your observation data. Your handler configuration determines what happens to the events that comes through your pipeline. For example, your handler might route incidents to a specific Slack channel or PagerDuty notification workflow, or send metrics to InfluxDB or Prometheus.

Sensu also checks your handlers for the event filters and mutators to apply in the filter and transform stages.

A few different types of handlers are available in Sensu. The most common are pipe handlers, which work similarly to checks and enable Sensu to interact with almost any computer program via standard streams.

Here’s an example resource definition for a pipe handler — read Send Slack alerts with handlers to learn how to configure your own version of this handler:

type: Handler
api_version: core/v2
  name: slack
  command: sensu-slack-handler --channel '#monitoring'
  filters: null
  handlers: null
  - sensu-slack-handler
  secrets: null
  timeout: 0
  type: pipe
  "type": "Handler",
  "api_version": "core/v2",
  "metadata": {
    "name": "slack"
  "spec": {
    "command": "sensu-slack-handler --channel '#monitoring'",
    "env_vars": [
    "filters": null,
    "handlers": null,
    "runtime_assets": [
    "secrets": null,
    "timeout": 0,
    "type": "pipe"

You can also use TCP/UDP handlers to send your observation data to remote sockets and handler sets to streamline groups of actions to execute for certain types of events.

Discover, download, and share Sensu handler dynamic runtime assets in Bonsai, the Sensu asset hub Read Use assets to install plugins to get started.