Repeat States JSON

SUSE Observability

Overview

This page describes the exact JSON messages that can be sent for the health synchronization Repeat States consistency model.

JSON property: "health"

Health can be sent to the SUSE Observability Receiver API using the "health" property of the common JSON object.

Example health `repeat_states` JSON

   "apiKey":"<STACKSTATE_RECEIVER_API_KEY>",
   "collection_timestamp":1585818978,
   "internalHostname":"lnx-343242.srv.stackstate.com",
   "events":{},
   "metrics":[],
   "service_checks":[],
   "health":[
      {
        "consistency_model": "REPEAT_STATES",
        "expiry": {
          "repeat_interval_s": 50,
          "expiry_interval_s": 100
        },
        "stream": {
          "urn": "urn:health:sourceId:streamId"
          //"sub_stream_id": "subStreamId" Optional
        },
        "check_states": [
          {
            "checkStateId": "checkStateId1",
            "message": "Server Running out of disk space",
            "health": "Deviating",
            "topologyElementIdentifier": "server-1",
            "name": "Disk Usage"
          },
          {
            "checkStateId": "checkStateId2",
            "message": "Provisioning failed. [Learn more](https://www.any-link.com)",
            "health": "critical",
            "topologyElementIdentifier": "server-2",
            "name": "Health monitor"
          }
        ]
      }
   ],
   "topologies":[]

Every health Repeat States data payload has the following details:

• expiry - Optional. An expiry update needs to be processed before processing check_states. This enables SUSE Observability to track how long the external checks should be present in the system if they aren't sent again. It carries the following fields as expiry metadata:

  • repeat_interval_s - Time in seconds. The frequency with which the external source will send health data to SUSE Observability. Max allowed value is 1800 (30 minutes).

  • expiry_interval_s - Time in seconds. The time to wait after the last update before an external check is deleted by SUSE Observability if the external check isn't observed again.

• stream - Object providing identification regarding which snapshots and check_states belong together. It has the following fields:

  • urn - Data source and stream ID encoded as a SUSE Observability URN that matches the following convention: urn:health:<sourceId>:<streamId> where <sourceId> is the name if the external data source and <streamId> is a unique identifier for the health data stream.

  • sub_stream_id - Optional. Identifier for a subset of the stream health data. When the stream data is distributed and reported by several agents, this allows snapshot lifecycles per sub_stream_id

• check_states - A list of check states. Each check state can have the following fields:

  • checkStateId - Identifier for the check state in the external system

  • message - Optional. Message to display in SUSE Observability UI. Data will be interpreted as markdown allowing to have links to the external system check that generated the external check state.

  • health - One of the following SUSE Observability Health state values: Clear, Deviating, Critical.

  • topologyElementIdentifier - Used to bind the check state to a SUSE Observability topology element.

  • name - Name of the external check state.

Send health to SUSE Observability

Health can be sent in one JSON message via HTTP POST. In the example below, a snapshot containing two check states is sent to SUSE Observability from a single external monitoring system.

curl -X POST \
 '<STACKSTATE_RECEIVER_API_ADDRESS>' \
 -H 'Content-Type: application/json' \
 -d '{
  "collection_timestamp": 1548857167,
  "internalHostname": "local.test",
  "health": [
    {
      "consistency_model": "REPEAT_STATES",
      "expiry": {
        "repeat_interval_s": 300,
        "expiry_interval_s": 600
      },
      "stream": {
        "urn": "urn:health:sourceId:streamId"
      },
      "check_states": [
        {
          "checkStateId": "checkStateId1",
          "message": "Server Running out of disk space",
          "health": "Deviating",
          "topologyElementIdentifier": "server-1",
          "name": "Disk Usage"
        },
        {
          "checkStateId": "checkStateId2",
          "message": "Provisioning failed. [Learn more](https://www.any-link.com)",
          "health": "critical",
          "topologyElementIdentifier": "server-2",
          "name": "Health monitor"
        }
      ]
    }
  ]
}'