Splunk Integration: Forward Alarms and Logs | Cloudmon

Splunk

Third Party Integration

Splunk

Forward Cloudmon alarms, audit events, and application logs to Splunk over Syslog or the Splunk HTTP Event Collector.

Overview

The Splunk integration forwards selected Cloudmon data to Splunk as it happens. You choose which data to send, how it is sent (Syslog, or the Splunk HTTP Event Collector), and the message format. Once the integration is enabled, the selected data sources are forwarded automatically.

To forward the same data to another SIEM platform, such as Microsoft Sentinel, IBM QRadar, or Elastic, see SIEM.

Data sourceWhat is forwarded
Forward AlarmsAlarms when they are raised, updated, and cleared. Selected by default.
Forward Audit EventsAudit events, which record the actions users take in Cloudmon. Selected by default.
Forward Application LogsCloudmon application logs at warning and error level. Not selected by default.

Before You Begin: Collect Details from Splunk

Decide how Splunk will receive the data, and collect the matching details.

MethodWhat you need
SyslogThe host and port of a syslog receiver in your Splunk environment. Use UDP port 514, or TCP for reliable delivery.
HTTP Event CollectorA Splunk HEC token. In Splunk Web, go to Settings → Data Inputs → HTTP Event Collector → New Token, and copy the token. Use the HTTP transport with port 8088. For details, see Set up and use HTTP Event Collector in Splunk Web.

Configuring the Splunk Integration

  1. Navigate to Settings → General Settings → Integrations. In the SIEM & Security group, click Add on the Splunk card.
  2. Complete the Connection, Log Format, and Data Sources sections, as described in the following tables.
  3. Click Test Connection to verify that Cloudmon can reach the receiver.
  4. Turn on Enable Splunk Integration.
  5. Click Save.

Connection fields: the fields depend on the Transport you select.

FieldDescription
Name*A name for the integration, such as the Splunk environment it sends to.
Transport*How Cloudmon sends the data: Syslog, or HTTP / HEC for the Splunk HTTP Event Collector.

With Syslog:

FieldDescription
Host*The address of the syslog receiver in your Splunk environment.
Port*The receiver port. The default is 514.
ProtocolUDP or TCP. Use TCP for reliable delivery.

With HTTP / HEC:

FieldDescription
URL*The HTTP Event Collector endpoint, for example https://<splunk-host>:8088/services/collector.
HEC Token*The HEC token you copied from Splunk. The token is stored encrypted and is never shown again after saving.
Verify SSL CertificateWhen on, Cloudmon checks the Splunk server certificate. On by default.

Log Format fields:

FieldDescription
Format*The message format: RFC 5424 Syslog, CEF (Common Event Format), or Splunk HEC JSON.
Splunk IndexThe Splunk index to write the events to. Shown with HTTP / HEC.
Source HostnameThe host name that identifies Cloudmon in the forwarded messages. If left empty, cloudmon-controller is used.

Data Sources: select the data to forward, as described in the Overview.

Troubleshooting

IssueWhat to check
Test Connection failsCheck the host and port, and that the protocol (UDP or TCP) matches the receiver. Confirm that the Controller can reach the receiver on that port through any firewall.
No data arrives in SplunkConfirm that Enable Splunk Integration is turned on and that at least one data source is selected. Check that the format matches the Splunk input that receives it.
The HEC token is needed againThe token is not shown again after saving. Create a new token in Splunk and enter it in the integration.