CLcloudamqp
Logs/Splunk v2

Add Splunk v2 log integration

Changed on

Add a Splunk v2 log integration. Broker and system logs are shipped to your Splunk HTTP Event Collector (HEC) endpoint via the OpenTelemetry Collector running on the cluster.

Create a HEC token at https://<your-splunk>/en-US/manager/search/http-eventcollector. Indexer acknowledgement must be disabled on the token.

Available on all LavinMQ clusters and RabbitMQ clusters running version 3.10.0 or later.

post/integrations/logs/splunk_v2

Request

  • Base URL
    https://api.cloudamqp.com/api
  • URL
    https://api.cloudamqp.com/api/integrations/logs/splunk_v2
  • Auth
    HTTP basic

Request body application/x-www-form-urlencoded

endpointstring required

Full HEC endpoint URL for incoming events

tokenstring required

HEC token used for authentication

sourcetypestring

(Optional) Source type assigned to forwarded events. When omitted the token's default source type is used. Allowed characters: letters, digits, underscore, dash, colon and dot (max 128 characters).

Example request

{
  "endpoint": "https://your-instance-id.splunkcloud.com:443/services/collector",
  "sourcetype": "cloudamqp"
}

Response

Integration created successfully

idinteger

Created integration ID

Example response

{
  "id": 10
}

Changes

  • 064cf050bff5Revision changes
    • breaking

      removed the success response with the status

    • info

      added the non-success response with the status

    • info

      added the success response with the status