Sensu Teams Handler

Overview
Usage examples
Configuration
Installation from source and contributing

Overview

The Sensu Teams Handler is a Sensu Event Handler that sends event data to a configured Teams channel. It is a rewrite by Sebastian Mildgrim of the Sensu Inc written sensu-slack-handler

Usage examples

Help output

Help:

Usage:
  sensu-teams-handler [flags]
  sensu-teams-handler [command]

Available Commands:
  help        Help about any command
  version     Print the version number of this plugin

Flags:
  -s, --sender string                 The name that messages will be sent as (default "Sensu")
  -d, --description-template string   The Teams notification output template, in Golang text/template format (default "{{ .Check.Output }}")
  -h, --help                          help for sensu-teams-handler
  -u, --sensu-url string              A URL to the Sensu dashboard (default "http://localhost:3000")
  -t, --is-test string                Specify if this is a test run (default "false")
  -w, --webhook-url string            The webhook url to send messages to

Environment variables

Argument	Environment Variable
--webhook-url	TEAMS_WEBHOOK_URL
--sender	TEAMS_SENDER
--is-test	TEAMS_IS_TEST
--sensu-url	TEAMS_SENSU_URL
--description-template	TEAMS_DESCRIPTION_TEMPLATE

Security Note: Care should be taken to not expose the webhook URL for this handler by specifying it on the command line or by directly setting the environment variable in the handler definition. It is suggested to make use of secrets management to surface it as an environment variable. The handler definition above references it as a secret. Below is an example secrets definition that make use of the built-in env secrets provider.

---
type: Secret
api_version: secrets/v1
metadata:
  name: teams-webhook-url
spec:
  provider: env
  id: TEAMS_WEBHOOK_URL

Templates

This handler provides options for using templates to populate the values provided by the event in the message sent via Teams. More information on template syntax and format can be found in the documentation

Annotations

All arguments for this handler are tunable on a per entity or check basis based on annotations. The annotations keyspace for this handler is sensu.io/plugins/teams/config.

NOTE: Due to check token substituion, supplying a template value such as for description-template as a check annotation requires that you place the desired template as a golang string literal (enlcosed in backticks) within another template definition. This does not apply to entity annotations.

Examples

To customize the sender for a given entity, you could use the following sensu-agent configuration snippet:

# /etc/sensu/agent.yml example
annotations:
  sensu.io/plugins/teams/config/sender: 'server1'

Configuration

Asset registration

Assets are the best way to make use of this handler. If you're not using an asset, please consider doing so! If you're using sensuctl 5.13 or later, you can use the following command to add the asset:

sensuctl asset add mildgrim/sensu-teams-handler

If you're using an earlier version of sensuctl, you can download the asset definition from this project's Bonsai Asset Index page.

Handler definition

Create the handler using the following handler definition:

---
api_version: core/v2
type: Handler
metadata:
  namespace: default
  name: teams
spec:
  type: pipe
  command: sensu-teams-handler --sensuUrl 'http://localhost:3000' --sender 'Sensu'
  filters:
  - is_incident
  runtime_assets:
  - sensu/sensu-teams-handler
  secrets:
  - name: TEAMS_WEBHOOK_URL
    secret: teams-webhook-url
  timeout: 10

Note: The library used in the Sensu SDK for this plugin requires that if your Teams webhook URL is listed as an environment variable, the URL cannot be surrounded by quotes.

Security Note: The Teams webhook URL should always be treated as a security sensitive configuration option and in this example, it is loaded into the handler configuration as an environment variable using a secret. Command arguments are commonly readable from the process table by other unprivaledged users on a system (ex: ps and top commands), so it's a better practise to read in sensitive information via environment variables or configuration files on disk. The --webhook-url flag is provided as an override for testing purposes.

Check definition

api_version: core/v2
type: CheckConfig
metadata:
  namespace: default
  name: dummy-app-healthz
spec:
  command: check-http -u http://localhost:8080/healthz
  subscriptions:
  - dummy
  publish: true
  interval: 10
  handlers:
  - teams

Proxy Support

This handler supports the use of the environment variables HTTP_PROXY, HTTPS_PROXY, and NO_PROXY (or the lowercase versions thereof). HTTPS_PROXY takes precedence over HTTP_PROXY for https requests. The environment values may be either a complete URL or a "host[:port]", in which case the "http" scheme is assumed.

Installing from source and contributing

Download the latest version of the sensu-teams-handler from releases, or create an executable from this source.

Compiling

From the local path of the sensu-teams-handler repository:

go build

To contribute to this plugin, see CONTRIBUTING

twocs / sensu-teams-handler