Reference: Events API event format - BlueCat Integrity - 26.1.0

Address Manager Administration Guide

ft:locale
en-US
Product name
BlueCat Integrity
Version
26.1.0

This section contains examples of JSON events sent by the Events API for each sink type (HTTP, Elasticsearch, Splunk, and Kafka). Events API JSON payloads are structured according to CloudEvents JSON specification 1.0.2. Fields and field order of the JSON payload varies slightly depending on the configured sink type.

Note: The id of the event is generated using the IDs of the transaction and resource associated with the operation in the format [transaction ID]-[resource ID]-[auto increment]. For example: 3067-100917-1. Events with no associated transaction will use a timestamp in place of transaction ID to maintain uniqueness.

HTTP event

{
  "specversion" : "1.0",
  "id": "3067-100917-1",
  "source": "/api/v2/transactions/3067",
  "type": "com.bluecatnetworks.integrity.event.v1",
  "hostname": "prot.bcn.com",
  "subject": "label-of-registry",
  "time": "2025-09-30T14:51:29Z",
  "data": {
    "transaction": {
        ...,
        "_links": {...}
    },
    "resource": {
        ...,
        "_links": {...}
    }
  }
}

Elasticsearch event

Elasticsearch events contain the same fields as HTTP events, as well as additional fields for path, source_type, and timestamp. The data field is also at the start of the JSON payload.

{
  "data": {
    "transaction": {
        ...,
        "_links": {...}
    },
    "resource": {
        ...,
        "_links": {...}
    }
  },
  "hostname": "prot.bcn.com",
  "id": "3067-100917-1",
  "path": "/",
  "source": "/api/v2/transactions/3067",
  "source_type": "http_server",
  "specversion" : "1.0",
  "subject": "label-of-registry",
  "time": "2025-09-30T14:51:29Z",
  "timestamp": "2025-09-30T14:51:29.794438053Z",
  "type": "com.bluecatnetworks.integrity.event.v1"
}

Splunk event

Splunk events contain the same fields as HTTP events, as well as additional fields for path and source_type. The data field is also at the start of the JSON payload.

{
  "data": {
    "transaction": {
        ...,
        "_links": {...}
    },
    "resource": {
        ...,
        "_links": {...}
    }
  },
  "hostname": "prot.bcn.com",
  "id": "3067-100917-1",
  "path": "/",
  "source": "/api/v2/transactions/3067",
  "source_type": "http_server",
  "specversion" : "1.0",
  "subject": "label-of-registry",
  "time": "2025-09-30T14:51:29Z",
  "type": "com.bluecatnetworks.integrity.event.v1"
}

Kafka event

Elasticsearch events contain the same fields as HTTP events, as well as additional fields for path, source_type, and timestamp. The data field is also at the start of the JSON payload.

{
  "data": {
    "transaction": {
        ...,
        "_links": {...}
    },
    "resource": {
        ...,
        "_links": {...}
    }
  },
  "hostname": "prot.bcn.com",
  "id": "3067-100917-1",
  "path": "/",
  "source": "/api/v2/transactions/3067",
  "source_type": "http_server",
  "specversion" : "1.0",
  "subject": "label-of-registry",
  "time": "2025-09-30T14:51:29Z",
  "timestamp": "2025-09-30T14:51:29.794438053Z",
  "type": "com.bluecatnetworks.integrity.event.v1"
}