sensu-client.core — helpshift/sensu-client 0.13.0

send-alert clj

(send-alert status
            message
            &
            {:keys [host port name refresh proto prefix-length? occurrences
                    meta]
             :or {host "localhost"
                  port 3030
                  name "mycheck"
                  refresh 60
                  proto :tcp
                  prefix-length? true
                  occurrences 1
                  meta {}}})

Send a status, name, message to Sensu via TCP on host, port.

Make sure you catch for java.net.Connection exceptions when using TCP.

Takes the following optional keys:

 `:host` - hostname or IP to connect to, default localhost
 `:port` - port number to connect to, default 3030
 `:name` - check name to set in the alert being sent, default mycheck
 `:refresh` - how frequently to send alerts in seconds, default 60 seconds
 `:occurrences` - number of times this exception should happen before we alert
 `:proto` - intended for TCP/UDP, default UDP
 `:meta` - metadata map (merged at top-level)

Examples:

 (send-alert :critical "things have failed badly"
             :name "myservice"
             :proto :udp)

 (send-alert :critical "things have failed badly"
             :name "myservice"
             :proto :tcp
             :meta {:slack_ext
                     {:slack_channel "#dev-alerts"}})

Note: To be used for sensu-core agents

send-alert-sensu-go clj

(send-alert-sensu-go status
                     message
                     &
                     {:keys [host port name labels annotations handlers]
                      :as event-data
                      :or {host "localhost"
                           port 3031
                           name "mycheck"
                           labels {}
                           annotations {}
                           handlers []}})

Send a status and message to Sensu via HTTP API.

Takes the following optional keys: :host - hostname or IP to connect to, default localhost :port - api-port number to connect to, default 3031 :name - check name to set in the alert, default mycheck :labels - custom attributes to include with observation data in events :handlers - array of handlers that will handle the event on sensu :annotations - on-identifying metadata to include with observation data in events

For supported fields and how to use them in event, please refer: https://docs.sensu.io/sensu-go/latest/observability-pipeline/observe-schedule/checks/#top-level-attributes

Note: To be used for sensu-go agent.

sensu-status clj

Sensu status map.