Entity reference

An entity represents anything that needs to be monitored, such as a server, container, or network switch, including the full range of infrastructure, runtime, and application types that compose a complete monitoring environment. Sensu uses agent entities and proxy entities.

Sensu’s free entity limit is 100 entities. All commercial features are available for free in the packaged Sensu Go distribution up to an entity limit of 100. If your Sensu instance includes more than 100 entities, contact us to learn how to upgrade your installation and increase your limit. See the announcement on our blog for more information about our usage policy.

Create and manage agent entities

When an agent connects to a backend, the agent entity definition is created from the information in the agent.yml configuration file. The default agent.yml file location depends on your operating system.

You can manage agent entities via the backend with sensuctl, the entities API, and the web UI, just like any other Sensu resource. This means you do not need to update the agent.yml configuration file to add, update, or delete agent entity attributes like subscriptions and labels.

NOTE: You cannot modify an agent entity with the agent.yml configuration file unless you delete the entity. The entity attributes in agent.yml are used only for initial entity creation unless you delete the entity.

If you delete an agent entity that you modified with sensuctl, the entities API, or the web UI, it will revert to the original configuration from agent.yml.

To maintain agent entities based on agent.yml, create ephemeral agent entities with the deregister attribute set to true. With this setting, the agent entity will deregister every time the agent process stops and its keepalive expires. When it restarts, it will revert to the original configuration from agent.yml You must set deregister: true in agent.yml before the agent entity is created.

If you change an agent entity’s class to proxy, the backend will revert the change to agent.

Agent entity example

This example shows the resource definition for an agent entity:

type: Entity
api_version: core/v2
metadata:
  annotations: null
  labels: null
  name: webserver01
  namespace: default
spec:
  deregister: false
  deregistration: {}
  entity_class: agent
  last_seen: 1542667231
  redact:
  - password
  - passwd
  - pass
  - api_key
  - api_token
  - access_key
  - secret_key
  - private_key
  - secret
  subscriptions:
  - entity:webserver01
  system:
    arch: amd64
    libc_type: glibc
    vm_system: kvm
    vm_role: host
    cloud_provider: null
    processes:
    - name: Slack
      pid: 1349
      ppid: 0
      status: Ss
      background: true
      running: true
      created: 1582137786
      memory_percent: 1.09932518
      cpu_percent: 0.3263987595984941
    - name: Slack Helper
      pid: 1360
      ppid: 1349
      status: Ss
      background: true
      running: true
      created: 1582137786
      memory_percent: 0.146866455
      cpu_percent: 0.30897618146109257
      hostname: sensu2-centos
    network:
      interfaces:
      - addresses:
        - 127.0.0.1/8
        - ::1/128
        name: lo
      - addresses:
        - 10.0.2.15/24
        - fe80::26a5:54ec:cf0d:9704/64
        mac: 08:00:27:11:ad:d2
        name: enp0s3
      - addresses:
        - 172.28.128.3/24
        - fe80::a00:27ff:febc:be60/64
        mac: 08:00:27:bc:be:60
        name: enp0s8
    os: linux
    platform: centos
    platform_family: rhel
    platform_version: 7.4.1708
  sensu_agent_version: 1.0.0
  user: agent
{
  "type": "Entity",
  "api_version": "core/v2",
  "metadata": {
    "name": "webserver01",
    "namespace": "default",
    "labels": null,
    "annotations": null
  },
  "spec": {
    "entity_class": "agent",
    "system": {
      "hostname": "sensu2-centos",
      "os": "linux",
      "platform": "centos",
      "platform_family": "rhel",
      "platform_version": "7.4.1708",
      "network": {
        "interfaces": [
          {
            "name": "lo",
            "addresses": [
              "127.0.0.1/8",
              "::1/128"
            ]
          },
          {
            "name": "enp0s3",
            "mac": "08:00:27:11:ad:d2",
            "addresses": [
              "10.0.2.15/24",
              "fe80::26a5:54ec:cf0d:9704/64"
            ]
          },
          {
            "name": "enp0s8",
            "mac": "08:00:27:bc:be:60",
            "addresses": [
              "172.28.128.3/24",
              "fe80::a00:27ff:febc:be60/64"
            ]
          }
        ]
      },
      "arch": "amd64",
      "libc_type": "glibc",
      "vm_system": "kvm",
      "vm_role": "host",
      "cloud_provider": "",
      "processes": [
        {
          "name": "Slack",
          "pid": 1349,
          "ppid": 0,
          "status": "Ss",
          "background": true,
          "running": true,
          "created": 1582137786,
          "memory_percent": 1.09932518,
          "cpu_percent": 0.3263987595984941
        },
        {
          "name": "Slack Helper",
          "pid": 1360,
          "ppid": 1349,
          "status": "Ss",
          "background": true,
          "running": true,
          "created": 1582137786,
          "memory_percent": 0.146866455,
          "cpu_percent": 0.308976181461092553
        }
      ]
    },
    "sensu_agent_version": "1.0.0",
    "subscriptions": [
      "entity:webserver01"
    ],
    "last_seen": 1542667231,
    "deregister": false,
    "deregistration": {},
    "user": "agent",
    "redact": [
      "password",
      "passwd",
      "pass",
      "api_key",
      "api_token",
      "access_key",
      "secret_key",
      "private_key",
      "secret"
    ]
  }
}

Create and manage proxy entities

Proxy entities are dynamically created entities that Sensu adds to the entity store if an entity does not already exist for a check result. Proxy entities allow Sensu to monitor external resources on systems where you cannot install a Sensu agent, like a network switch or website.

You can modify proxy entities via the backend with sensuctl, the entities API, and the web UI.

If you start an agent with the same name as an existing proxy entity, Sensu will change the proxy entity’s class to agent and update its system field with information from the agent configuration.

Proxy entity example

This example shows the resource definition for a proxy entity:

type: Entity
api_version: core/v2
metadata:
  name: sensu-docs
  namespace: default
  labels: null
spec:
  deregister: false
  deregistration: {}
  entity_class: proxy
  last_seen: 0
  subscriptions:
  - proxy
  system:
    network:
      interfaces: null
  sensu_agent_version: 1.0.0
{
  "type": "Entity",
  "api_version": "core/v2",
  "metadata": {
    "name": "sensu-docs",
    "namespace": "default",
    "labels": null
  },
  "spec": {
    "deregister": false,
    "deregistration": {},
    "entity_class": "proxy",
    "last_seen": 0,
    "subscriptions": [
      "proxy"
    ],
    "system": {
      "network": {
        "interfaces": null
      }
    },
    "sensu_agent_version": "1.0.0"
  }
}

Proxy entities and round robin scheduling

Proxy entities make round robin scheduling more useful. Proxy entities allow you to combine all round robin events into a single event. Instead of having a separate event for each agent entity, you have a single event for the entire round robin.

If you don’t use a proxy entity for round robin scheduling, you could have several failures in a row, but each event will only be aware of one of the failures.

If you use a proxy entity without round robin scheduling, and several agents share the subscription, they will all execute the check for the proxy entity and you’ll get duplicate results. When you enable round robin, you’ll get one agent per interval executing the proxy check, but the event will always be listed under the proxy entity. If you don’t create a proxy entity, it is created when the check is executed. You can modify the proxy entity later if needed.

Use proxy entity filters to establish a many-to-many relationship between agent entities and proxy entities if you want even more power over the grouping.

Manage entity labels

Labels are custom attributes that Sensu includes with observation data in events that you can use for response and web UI view searches. In contrast to annotations, you can use labels to filter API responses, sensuctl responses, and web UI search views.

Limit labels to metadata you need to use for response filtering and searches. For complex, non-identifying metadata that you will not need to use in response filtering and searches, use annotations rather than labels.

Agent entity labels

For new entities with class agent, you can define entity attributes in the /etc/sensu/agent.yml configuration file. For example, to add a url label, open /etc/sensu/agent.yml and add configuration for labels:

labels:
  url: sensu.docs.io

Or, use sensu-agent start configuration flags:

sensu-agent start --labels url=sensu.docs.io

NOTE: The entity attributes in agent.yml are used only for initial entity creation. Modify existing agent entities via the backend with sensuctl, the entities API, and the web UI.

Proxy entity labels

For entities with class proxy, you can create and manage labels with sensuctl. For example, to create a proxy entity with a url label using sensuctl create, first create a file named proxy-example.yml or proxy-example.json with an entity definition that includes labels:

---
type: Entity
api_version: core/v2
metadata:
  labels:
    url: docs.sensu.io
  name: sensu-docs
  namespace: default
spec:
  deregister: false
  deregistration: {}
  entity_class: proxy
  last_seen: 0
  subscriptions:
  - proxy
  system:
    network:
      interfaces: null
  sensu_agent_version: 1.0.0
{
  "type": "Entity",
  "api_version": "core/v2",
  "metadata": {
    "name": "sensu-docs",
    "namespace": "default",
    "labels": {
      "url": "docs.sensu.io"
    }
  },
  "spec": {
    "deregister": false,
    "deregistration": {},
    "entity_class": "proxy",
    "last_seen": 0,
    "subscriptions": [
      "proxy"
    ],
    "system": {
      "network": {
        "interfaces": null
      }
    },
    "sensu_agent_version": "1.0.0"
  }
}

Then run sensuctl create to create the entity based on the definition:

sensuctl create --file proxy-example.yml
sensuctl create --file proxy-example.json

To add a label to an existing entity, use sensuctl edit. For example, to add a proxy_type label to the sensu-docs entity you just created:

sensuctl edit entity sensu-docs

And update the metadata scope to include the proxy_type label:

type: Entity
api_version: core/v2
metadata:
  labels:
    url: docs.sensu.io
    proxy_type: website
  name: sensu-docs
  namespace: default
spec:
  '...': '...'

Proxy entity checks

Proxy entities allow Sensu to monitor external resources on systems or devices where a Sensu agent cannot be installed, like a network switch, website, or API endpoint. You can configure a check with a proxy entity name to associate the check results with that proxy entity. On the first check result, if the proxy entity does not exist, Sensu will create the entity as a proxy entity.

After you create a proxy entity check, define which agents will run the check by configuring a subscription. See Monitor external resources with proxy requests and entities for details about creating a proxy check for a proxy entity.

Entities specification

Top-level attributes

type
description Top-level attribute that specifies the sensuctl create resource type. Entities should always be type Entity.
required Required for entity definitions in wrapped-json or yaml format for use with sensuctl create.
type String
example 
type: Entity
{
  "type": "Entity"
}
api_version
description Top-level attribute that specifies the Sensu API group and version. For entities in this version of Sensu, this attribute should always be core/v2.
required Required for entity definitions in wrapped-json or yaml format for use with sensuctl create.
type String
example 
api_version: core/v2
{
  "api_version": "core/v2"
}
metadata
description Top-level collection of metadata about the entity, including name, namespace, and created_by as well as custom labels and annotations. The metadata map is always at the top level of the entity definition. This means that in wrapped-json and yaml formats, the metadata scope occurs outside the spec scope. See metadata attributes for details.
required Required for entity definitions in wrapped-json or yaml format for use with sensuctl create.
type Map of key-value pairs
example 
metadata:
  name: webserver01
  namespace: default
  created_by: admin
  labels:
    region: us-west-1
  annotations:
    slack-channel: "#monitoring"
{
  "metadata": {
    "name": "webserver01",
    "namespace": "default",
    "created_by": "admin",
    "labels": {
      "region": "us-west-1"
    },
    "annotations": {
      "slack-channel": "#monitoring"
    }
  }
}
spec
description Top-level map that includes the entity spec attributes.
required Required for entity definitions in wrapped-json or yaml format for use with sensuctl create.
type Map of key-value pairs
example 
spec:
  entity_class: agent
  system:
    hostname: sensu2-centos
    os: linux
    platform: centos
    platform_family: rhel
    platform_version: 7.4.1708
    network:
      interfaces:
      - name: lo
        addresses:
        - 127.0.0.1/8
        - "::1/128"
      - name: enp0s3
        mac: '08:00:27:11:ad:d2'
        addresses:
        - 10.0.2.15/24
        - fe80::26a5:54ec:cf0d:9704/64
      - name: enp0s8
        mac: '08:00:27:bc:be:60'
        addresses:
        - 172.28.128.3/24
        - fe80::a00:27ff:febc:be60/64
    arch: amd64
    libc_type: glibc
    vm_system: kvm
    vm_role: host
    cloud_provider: ''
    processes:
    - name: Slack
      pid: 1349
      ppid: 0
      status: Ss
      background: true
      running: true
      created: 1582137786
      memory_percent: 1.09932518
      cpu_percent: 0.3263987595984941
    - name: Slack Helper
      pid: 1360
      ppid: 1349
      status: Ss
      background: true
      running: true
      created: 1582137786
      memory_percent: 0.146866455
      cpu_percent: 0.30897618146109257
  sensu_agent_version: 1.0.0
  subscriptions:
  - entity:webserver01
  last_seen: 1542667231
  deregister: false
  deregistration: {}
  user: agent
  redact:
  - password
  - passwd
  - pass
  - api_key
  - api_token
  - access_key
  - secret_key
  - private_key
  - secret
{
  "spec": {
    "entity_class": "agent",
    "system": {
      "hostname": "sensu2-centos",
      "os": "linux",
      "platform": "centos",
      "platform_family": "rhel",
      "platform_version": "7.4.1708",
      "network": {
        "interfaces": [
          {
            "name": "lo",
            "addresses": [
              "127.0.0.1/8",
              "::1/128"
            ]
          },
          {
            "name": "enp0s3",
            "mac": "08:00:27:11:ad:d2",
            "addresses": [
              "10.0.2.15/24",
              "fe80::26a5:54ec:cf0d:9704/64"
            ]
          },
          {
            "name": "enp0s8",
            "mac": "08:00:27:bc:be:60",
            "addresses": [
              "172.28.128.3/24",
              "fe80::a00:27ff:febc:be60/64"
            ]
          }
        ]
      },
      "arch": "amd64",
      "libc_type": "glibc",
      "vm_system": "kvm",
      "vm_role": "host",
      "cloud_provider": "",
      "processes": [
        {
          "name": "Slack",
          "pid": 1349,
          "ppid": 0,
          "status": "Ss",
          "background": true,
          "running": true,
          "created": 1582137786,
          "memory_percent": 1.09932518,
          "cpu_percent": 0.3263987595984941
        },
        {
          "name": "Slack Helper",
          "pid": 1360,
          "ppid": 1349,
          "status": "Ss",
          "background": true,
          "running": true,
          "created": 1582137786,
          "memory_percent": 0.146866455,
          "cpu_percent": 0.30897618146109257
        }
      ]
    },
    "sensu_agent_version": "1.0.0",
    "subscriptions": [
      "entity:webserver01"
    ],
    "last_seen": 1542667231,
    "deregister": false,
    "deregistration": {},
    "user": "agent",
    "redact": [
      "password",
      "passwd",
      "pass",
      "api_key",
      "api_token",
      "access_key",
      "secret_key",
      "private_key",
      "secret"
    ]
  }
}

Metadata attributes

name
description Unique name of the entity, validated with Go regex \A[\w\.\-]+\z.
required true
type String
example 
name: example-hostname
{
  "name": "example-hostname"
}
namespace
description Sensu RBAC namespace that this entity belongs to.
required false
type String
default default
example 
namespace: production
{
  "namespace": "production"
}
created_by
description Username of the Sensu user who created the entity or last updated the entity. Sensu automatically populates the created_by field when the entity is created or updated.
required false
type String
example 
created_by: admin
{
  "created_by": "admin"
}
labels
description Custom attributes to include with observation data in events that you can use for response and web UI view filtering.

If you include labels in your event data, you can filter API responses, sensuctl responses, and web UI views based on them. In other words, labels allow you to create meaningful groupings for your data.

Limit labels to metadata you need to use for response filtering. For complex, non-identifying metadata that you will not need to use in response filtering, use annotations rather than labels.

NOTE: For labels that you define in agent.yml or backend.yml, the keys are automatically modified to use all lower-case letters. For example, if you define the label proxyType: "website" in agent.yml or backend.yml, it will be listed as proxytype: "website" in entity definitions.

Key cases are not modified for labels you define with a command line flag or an environment variable.
required false
type Map of key-value pairs. Keys can contain only letters, numbers, and underscores and must start with a letter. Values can be any valid UTF-8 string.
default null
example 
labels:
  environment: development
  region: us-west-2
{
  "labels": {
    "environment": "development",
    "region": "us-west-2"
  }
}

annotations
description Non-identifying metadata to include with observation data in events that you can access with event filters. You can use annotations to add data that’s meaningful to people or external tools that interact with Sensu.

In contrast to labels, you cannot use annotations in API response filtering, sensuctl response filtering, or web UI views.

NOTE: For annotations defined in agent.yml or backend.yml, the keys are automatically modified to use all lower-case letters. For example, if you define the annotation webhookURL: "https://my-webhook.com" in agent.yml or backend.yml, it will be listed as webhookurl: "https://my-webhook.com" in entity definitions.

Key cases are not modified for annotations you define with a command line flag or an environment variable.
required false
type Map of key-value pairs. Keys and values can be any valid UTF-8 string.
default null
example 
annotations:
  managed-by: ops
  playbook: www.example.url
{
  "annotations": {
    "managed-by": "ops",
    "playbook": "www.example.url"
  }
}

Spec attributes

entity_class
description Entity type, validated with Go regex \A[\w\.\-]+\z. Class names have special meaning. An entity that runs an agent is class agent and is reserved. Setting the value of entity_class to proxy creates a proxy entity. For other types of entities, the entity_class attribute isn’t required, and you can use it to indicate an arbitrary type of entity (like lambda or switch).
required true
type String
example 
entity_class: agent
{
  "entity_class": "agent"
}
subscriptions
description List of subscription names for the entity. The entity by default has an entity-specific subscription, in the format of entity:{name} where name is the entity’s hostname.
required false
type Array
default The entity-specific subscription.
example 
subscriptions:
- web
- prod
- entity:example-entity
{
  "subscriptions": [
    "web",
    "prod",
    "entity:example-entity"
  ]
}
system
description System information about the entity, such as operating system and platform. See system attributes for more information.

IMPORTANT: Process discovery is disabled in release 5.20.2. As of 5.20.2, new events will not include data in the processes attributes. Instead, the field will be empty: "processes": null.
required false
type Map
example 
system:
  arch: amd64
  libc_type: glibc
  vm_system: kvm
  vm_role: host
  cloud_provider: null
  processes:
  - name: Slack
    pid: 1349
    ppid: 0
    status: Ss
    background: true
    running: true
    created: 1582137786
    memory_percent: 1.09932518
    cpu_percent: 0.3263987595984941
  - name: Slack Helper
    pid: 1360
    ppid: 1349
    status: Ss
    background: true
    running: true
    created: 1582137786
    memory_percent: 0.146866455
    cpu_percent: 0.30897618146109257
  hostname: example-hostname
  network:
    interfaces:
    - addresses:
      - 127.0.0.1/8
      - ::1/128
      name: lo
    - addresses:
      - 93.184.216.34/24
      - 2606:2800:220:1:248:1893:25c8:1946/10
      mac: 52:54:00:20:1b:3c
      name: eth0
  os: linux
  platform: ubuntu
  platform_family: debian
  platform_version: "16.04"
{
  "system": {
    "hostname": "example-hostname",
    "os": "linux",
    "platform": "ubuntu",
    "platform_family": "debian",
    "platform_version": "16.04",
    "network": {
      "interfaces": [
        {
          "name": "lo",
          "addresses": [
            "127.0.0.1/8",
            "::1/128"
          ]
        },
        {
          "name": "eth0",
          "mac": "52:54:00:20:1b:3c",
          "addresses": [
            "93.184.216.34/24",
            "2606:2800:220:1:248:1893:25c8:1946/10"
          ]
        }
      ]
    },
    "arch": "amd64",
    "libc_type": "glibc",
    "vm_system": "kvm",
    "vm_role": "host",
    "cloud_provider": "",
    "processes": [
      {
        "name": "Slack",
        "pid": 1349,
        "ppid": 0,
        "status": "Ss",
        "background": true,
        "running": true,
        "created": 1582137786,
        "memory_percent": 1.09932518,
        "cpu_percent": 0.3263987595984941
      },
      {
        "name": "Slack Helper",
        "pid": 1360,
        "ppid": 1349,
        "status": "Ss",
        "background": true,
        "running": true,
        "created": 1582137786,
        "memory_percent": 0.146866455,
        "cpu_percent": 0.308976181461092553
      }
    ]
  }
}
sensu_agent_version
description Sensu Semantic Versioning (SemVer) version of the agent entity.
required true
type String
example 
sensu_agent_version: 1.0.0
{
  "sensu_agent_version": "1.0.0"
}
last_seen
description Timestamp the entity was last seen. In seconds since the Unix epoch.

NOTE: In the entity attributes for events created with the events API, the last_seen value is 0.
required false
type Integer
example 
last_seen: 1522798317
{
  "last_seen": 1522798317
}
deregister
description true if the entity should be removed when it stops sending keepalive messages. Otherwise, false.
required false
type Boolean
default false
example 
deregister: false
{
  "deregister": false
}
deregistration
description Map that contains a handler name to use when an entity is deregistered. See deregistration attributes for more information.
required false
type Map
example 
deregistration:
  handler: email-handler
{
  "deregistration": {
    "handler": "email-handler"
  }
}
redact
description List of items to redact from log messages. If a value is provided, it overwrites the default list of items to be redacted.
required false
type Array
default [“password”, “passwd”, “pass”, “api_key”, “api_token”, “access_key”, “secret_key”, “private_key”, “secret”]
example 
redact:
- extra_secret_tokens
{
  "redact": [
    "extra_secret_tokens"
  ]
}
user
description Sensu RBAC username used by the entity. Agent entities require get, list, create, update, and delete permissions for events across all namespaces.
type String
default agent
example 
user: agent
{
  "user": "agent"
}

System attributes

hostname
description Hostname of the entity.
required false
type String
example 
hostname: example-hostname
{
  "hostname": "example-hostname"
}
os
description Entity’s operating system.
required false
type String
example 
os: linux
{
  "os": "linux"
}
platform
description Entity’s operating system distribution.
required false
type String
example 
platform: ubuntu
{
  "platform": "ubuntu"
}
platform_family
description Entity’s operating system family.
required false
type String
example 
platform_family: debian
{
  "platform_family": "debian"
}
platform_version
description Entity’s operating system version.
required false
type String
example 
platform_version: 16.04
{
  "platform_version": "16.04"
}
network
description Entity’s network interface list. See network attributes for more information.
required false
type Map
example 
network:
  interfaces:
  - addresses:
    - 127.0.0.1/8
    - ::1/128
    name: lo
  - addresses:
    - 93.184.216.34/24
    - 2606:2800:220:1:248:1893:25c8:1946/10
    mac: 52:54:00:20:1b:3c
    name: eth0
{
  "network": {
    "interfaces": [
      {
        "name": "lo",
        "addresses": [
          "127.0.0.1/8",
          "::1/128"
        ]
      },
      {
        "name": "eth0",
        "mac": "52:54:00:20:1b:3c",
        "addresses": [
          "93.184.216.34/24",
          "2606:2800:220:1:248:1893:25c8:1946/10"
        ]
      }
    ]
  }
}
arch
description Entity’s system architecture. This value is determined by the Go binary architecture as a function of runtime.GOARCH. An amd system running a 386 binary will report the arch as 386.
required false
type String
example 
arch: amd64
{
  "arch": "amd64"
}
libc_type
description Entity’s libc type. Automatically populated upon agent startup.
required false
type String
example 
libc_type: glibc
{
  "libc_type": "glibc"
}
vm_system
description Entity’s virtual machine system. Automatically populated upon agent startup.
required false
type String
example 
vm_system: kvm
{
  "vm_system": "kvm"
}
vm_role
description Entity’s virtual machine role. Automatically populated upon agent startup.
required false
type String
example 
vm_role: host
{
  "vm_role": "host"
}
cloud_provider
description Entity’s cloud provider environment. Automatically populated upon agent startup if the --detect-cloud-provider flag is set. Returned empty unless the agent runs on Amazon Elastic Compute Cloud (EC2), Google Cloud Platform (GCP), or Microsoft Azure.

NOTE: This feature can result in several HTTP requests or DNS lookups being performed, so it may not be appropriate for all environments.
required false
type String
example 
"cloud_provider": ""
{
  "cloud_provider": ""
}
processes
description List of processes on the local agent. See processes attributes for more information.

IMPORTANT: Process discovery is disabled in release 5.20.2. As of 5.20.2, new events will not include data in the processes attributes. Instead, the field will be empty: "processes": null.
required false
type Map
example 
processes:
- name: Slack
  pid: 1349
  ppid: 0
  status: Ss
  background: true
  running: true
  created: 1582137786
  memory_percent: 1.09932518
  cpu_percent: 0.3263987595984941
- name: Slack Helper
  pid: 1360
  ppid: 1349
  status: Ss
  background: true
  running: true
  created: 1582137786
  memory_percent: 0.146866455
  cpu_percent: 0.30897618146109257
{
  "processes": [
    {
      "name": "Slack",
      "pid": 1349,
      "ppid": 0,
      "status": "Ss",
      "background": true,
      "running": true,
      "created": 1582137786,
      "memory_percent": 1.09932518,
      "cpu_percent": 0.3263987595984941
    },
    {
      "name": "Slack Helper",
      "pid": 1360,
      "ppid": 1349,
      "status": "Ss",
      "background": true,
      "running": true,
      "created": 1582137786,
      "memory_percent": 0.146866455,
      "cpu_percent": 0.308976181461092553
    }
  ]
}

Network attributes

network_interface
description List of network interfaces available on the entity, with their associated MAC and IP addresses.
required false
type Array NetworkInterface
example 
interfaces:
- addresses:
  - 127.0.0.1/8
  - ::1/128
  name: lo
- addresses:
  - 93.184.216.34/24
  - 2606:2800:220:1:248:1893:25c8:1946/10
  mac: 52:54:00:20:1b:3c
  name: eth0
{
  "interfaces": [
    {
      "name": "lo",
      "addresses": [
        "127.0.0.1/8",
        "::1/128"
      ]
    },
    {
      "name": "eth0",
      "mac": "52:54:00:20:1b:3c",
      "addresses": [
        "93.184.216.34/24",
        "2606:2800:220:1:248:1893:25c8:1946/10"
      ]
    }
  ]
}

NetworkInterface attributes

name
description Network interface name.
required false
type String
example 
name: eth0
{
  "name": "eth0"
}
mac
description Network interface’s MAC address.
required false
type string
example 
mac: 52:54:00:20:1b:3c
{
  "mac": "52:54:00:20:1b:3c"
}
addresses
description List of IP addresses for the network interface.
required false
type Array
example 
addresses:
- 93.184.216.34/24
- 2606:2800:220:1:248:1893:25c8:1946/10
{
  "addresses": [
    "93.184.216.34/24",
    "2606:2800:220:1:248:1893:25c8:1946/10"
  ]
}

Deregistration attributes

handler
description Name of the handler to call when an entity is deregistered.
required false
type String
example 
handler: email-handler
{
  "handler": "email-handler"
}

Processes attributes

IMPORTANT: Process discovery is disabled in release 5.20.2. As of 5.20.2, new events will not include data in the processes attributes. Instead, the field will be empty: "processes": null.

COMMERCIAL FEATURE: Access processes attributes with the discover-processes flag in the packaged Sensu Go distribution. For more information, see Get started with commercial features.

NOTE: The processes field is populated in the packaged Sensu Go distributions. In OSS builds, the field will be empty: "processes": null.

name
description Name of the process.
required false
type String
example 
name: Slack
{
  "name": "Slack"
}
pid
description Process ID of the process.
required false
type Integer
example 
pid: 1349
{
  "pid": 1349
}
ppid
description Parent process ID of the process.
required false
type Integer
example 
ppid: 0
{
  "ppid": 0
}
status
description Status of the process. See the Linux top manual page for examples.
required false
type String
example 
status: Ss
{
  "status": "Ss"
}
background
description If true, the process is a background process. Otherwise, false.
required false
type Boolean
example 
background: true
{
  "background": true
}
running
description If true, the process is running. Otherwise, false.
required false
type Boolean
example 
running: true
{
  "running": true
}
created
description Timestamp when the process was created. In seconds since the Unix epoch.
required false
type Integer
example 
created: 1586138786
{
  "created": 1586138786
}
memory_percent
description Percent of memory the process is using. The value is returned as a floating-point number where 0.0 = 0% and 1.0 = 100%. For example, the memory_percent value 0.19932 equals 19.932%.

NOTE: The memory_percent attribute is supported on Linux and macOS. It is not supported on Windows.
required false
type float
example 
memory_percent: 0.19932
{
  "memory_percent": 0.19932
}
cpu_percent
description Percent of CPU the process is using. The value is returned as a floating-point number where 0.0 = 0% and 1.0 = 100%. For example, the cpu_percent value 0.12639 equals 12.639%.

NOTE: The cpu_percent attribute is supported on Linux and macOS. It is not supported on Windows.
required false
type float
example 
cpu_percent: 0.12639
{
  "cpu_percent": 0.12639
}