Aggregates API

Reference documentation

• The /aggregates API endpoint
  • /aggregates (GET)
• The /aggregates/:name API endpoints
  • /aggregates/:name (GET)
  • /aggregates/:name (DELETE)
• The /aggregates/:name/clients API endpoint
  • /aggregates/:name/clients (GET)
• The /aggregates/:name/checks API endpoint
  • /aggregates/:name/checks (GET)
• The /aggregates/:name/results/:severity API endpoint
  • /aggregates/:name/results/:severity (GET)

The /aggregates API endpoint

The /aggregates API endpoint provides HTTP GET access to named aggregate data.

/aggregates (GET)

EXAMPLES

The following example demonstrates a /aggregates API query which results in a JSON Array of JSON Hashes containing named check aggregates.

$ curl -s http://localhost:4567/aggregates | jq .
[
  {"name": "check_http"},
  {"name": "check_web_app"},
  {"name": "elasticsearch_health"}
]

API specification

[
  {"name": "check_http"},
  {"name": "check_web_app"},
  {"name": "elasticsearch_health"}
]

The /aggregates/:name API endpoints

The /aggregates/:name API endpoints provide HTTP GET and HTTP DELETE access to check aggregate data for a named aggregate.

/aggregates/:name (GET)

EXAMPLES

The following example demonstrates a /aggregates/:name API query for the check result data for the aggregate named example_aggregate.

$ curl -s http://localhost:4567/aggregates/example_aggregate | jq .
{
  "clients": 15,
  "checks": 2,
  "results": {
    "ok": 18,
    "warning": 0,
    "critical": 1,
    "unknown": 0,
    "total": 19,
    "stale": 0
  }
}

API specification

{
  "clients": 15,
  "checks": 2,
  "results": {
    "ok": 18,
    "warning": 0,
    "critical": 1,
    "unknown": 0,
    "total": 19,
    "stale": 0
  }
}

/aggregates/:name (DELETE)

EXAMPLES

The following example demonstrates a /aggregates/:name API request to delete named aggregate data for the aggregate named example_aggregate, resulting in a 204 (No Content) HTTP response code (i.e. HTTP/1.1 204 No Content).

$ curl -s -i -X DELETE http://localhost:4567/aggregates/example_aggregate
HTTP/1.1 204 No Content
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET, POST, PUT, DELETE, OPTIONS
Access-Control-Allow-Credentials: true
Access-Control-Allow-Headers: Origin, X-Requested-With, Content-Type, Accept, Authorization
Connection: close
Server: thin

API specification

HTTP/1.1 204 No Content
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET, POST, PUT, DELETE, OPTIONS
Access-Control-Allow-Credentials: true
Access-Control-Allow-Headers: Origin, X-Requested-With, Content-Type, Accept, Authorization
Connection: close
Server: thin

The /aggregates/:name/clients API endpoint

The /aggregates/:name/clients API endpoint provides HTTP GET access to the Sensu client members of a named aggregate.

/aggregates/:name/clients (GET)

EXAMPLES

The following example demonstrates a /aggregates/:name/clients API query for the client members of an aggregate named elasticsearch.

$ curl -s http://localhost:4567/aggregates/elasticsearch/clients | jq .
[
  {
    "name": "i-424242",
    "checks": [
      "elasticsearch_service",
      "elasticsearch_cluster_health"
    ]
  },
  {
    "name": "1-424243",
    "checks": [
      "elasticsearch_service"
    ]
  },
]

API specification

[
  {
    "name": "i-424242",
    "checks": [
      "elasticsearch_service",
      "elasticsearch_cluster_health"
    ]
  },
  {
    "name": "1-424243",
    "checks": [
      "elasticsearch_service"
    ]
  }
]

The /aggregates/:name/checks API endpoint

The /aggregates/:name/checks API endpoint provides HTTP GET access to the Sensu check members of a named aggregate.

/aggregates/:name/checks (GET)

EXAMPLES

The following example demonstrates a /aggregates/:name/checks API query for the check members of an aggregate named elasticsearch.

$ curl -s http://localhost:4567/aggregates/elasticsearch/checks | jq .
[
  {
    "name": "elasticsearch_service",
    "clients": [
      "i-424242",
      "i-424243"
    ]
  },
  {
    "name": "elasticsearch_cluster_health",
    "clients": [
      "i-424242"
    ]
  }
]

API specification

[
  {
    "name": "elasticsearch_service",
    "clients": [
      "i-424242",
      "i-424243"
    ]
  },
  {
    "name": "elasticsearch_cluster_health",
    "clients": [
      "i-424242"
    ]
  }
]

The /aggregates/:name/results/:severity API endpoint

The /aggregates/:name/results/:severity API endpoint provides HTTP GET access to check result members of a named aggregate, by severity.

/aggregates/:name/results/:severity (GET)

EXAMPLES

The following example demonstrates a /aggregates/:name/results/:severity API query for the critical check results of an aggregate named elasticsearch.

$ curl -s http://localhost:4567/aggregates/elasticsearch/results/critical | jq .
[
  {
    "check": "elasticsearch_cluster_health",
    "summary": [
      {
        "output": "Everything is Broken!",
        "total": 1,
        "clients": ["i-424242"]
      }
    ]
  }
]

API specification

[
  {
    "check": "elasticsearch_cluster_health",
    "summary": [
      {
        "output": "Everything is Broken!",
        "total": 1,
        "clients": ["i-424242"]
      }
    ]
  }
]