Monitor Business Services

COMMERCIAL FEATURE: Access business service monitoring (BSM) in the packaged Sensu Go distribution. For more information, read Get started with commercial features.

NOTE: Business service monitoring (BSM) is in public preview and is subject to change.

Sensu’s business service monitoring (BSM) provides high-level visibility into the current health of any number of your business services. Use BSM to monitor every component in your system with a top-down approach that produces meaningful alerts, prevents alert fatigue, and helps you focus on your core business services.

BSM requires two resources that work together to achieve top-down monitoring: service components and rule templates. Service components are the elements that make up your business services. Rule templates define the monitoring rules that produce events for service components based on customized evaluation expressions.

An example of a business service might be a company website. The website itself might have three service components: the primary webserver that publishes website pages, a backup webserver in case the primary webserver fails, and an inventory database for the shop section of the website. At least one webserver and the database must be in an OK state for the website to be fully available.

In this scenario, you could use BSM to create a current status page for this company website that displays the website’s high-level status at a glance. As long as one webserver and the database have an OK status, the website status is OK. Otherwise, the website status is not OK. Most people probably just want to know whether the website is currently available — it won’t matter to them whether the website is functioning with one or both webservers.

At the same time, the company does want to make sure the right person addresses any webserver failures, even if the website is technically still OK. BSM allows you to customize rule templates that apply a threshold for taking action for different service components as well as what action to take.

To continue the company website example, if the primary webserver fails but the backup webserver does not, you might use a rule template that creates a service ticket to address the next workday (in addition to the rule template that is emitting “OK” events for the current status page). Another monitoring rule might trigger an alert to the on-call operator should both webservers or the inventory database fail.

NOTE: BSM requires high event throughput. Configure a PostgreSQL datastore to achieve the required throughput and use the BSM feature.

Service component example

Here is an example service component definition that includes the account-manager and tessen services and applies a rule template named status-threshold by reference:

type: ServiceComponent
api_version: bsm/v1
  name: postgresql-1
  cron: ''
  - pagerduty
  - slack
  interval: 60
  - type: labelSelector
    value: region == 'us-west-1' && cmpt == psql
  - arguments:
      status: non-zero
      threshold: 25
    name: nonzero-25
    template: status-threshold
  - account-manager
  - tessen
  "type": "ServiceComponent",
  "api_version": "bsm/v1",
  "metadata": {
    "name": "postgresql-1"
  "spec": {
    "cron": "",
    "handlers": [
    "interval": 60,
    "query": [
        "type": "labelSelector",
        "value": "region == 'us-west-1' && cmpt == psql"
    "rules": [
        "arguments": {
          "status": "non-zero",
          "threshold": 25
        "name": "nonzero-25",
        "template": "status-threshold"
    "services": [

Rule template example

The status-threshold rule template (referenced in the service component example) could be configured as shown in this example:

type: RuleTemplate
api_version: bsm/v1
  name: status-threshold
  description: Creates an event when the percentage of events with the given status exceed the given threshold
      - threshold
        type: string
        default: non-zero
          - non-zero
          - warning
          - critical
          - unknown
        type: number
        description: Numeric value that triggers an event when surpassed
  eval: |
    var statusMap = {
      "non-zero": 1,
      "warning": 1,
      "critical": 2,
    function main(args) {
      var total =;
      var num =;
      if (num / total <= args.threshold) {
      return sensu.new_event({
        status: statusMap[args.status],
        /* ... */,
  "type": "RuleTemplate",
  "api_version": "bsm/v1",
  "metadata": {
    "name": "status-threshold"
  "spec": {
    "description": "Creates an event when the percentage of events with the given status exceed the given threshold",
    "arguments": {
      "required": [
      "properties": {
        "status": {
          "type": "string",
          "default": "non-zero",
          "enum": [
        "threshold": {
          "type": "number",
          "description": "Numeric value that triggers an event when surpassed"
    "eval": "var statusMap = {\n  \"non-zero\": 1,\n  \"warning\": 1,\n  \"critical\": 2,\n};\nfunction main(args) {\n  var total =;\n  var num =;\n  if (num / total <= args.threshold) {\n    return;\n  }\n  return sensu.new_event({\n    status: statusMap[args.status],\n    /* ... */,\n  });\n}"

Configure BSM via the web UI

The Sensu web UI BSM module allows you to create, edit, and delete service components and rule templates inside the web UI.

Configure BSM via APIs and sensuctl

BSM service components and rule templates are Sensu resources with complete definitions, so you can use Sensu’s service component and rule template APIs to create, retrieve, update, and delete service components and rule templates.

You can also use sensuctl to create and manage service components and rule templates via the APIs from the command line.