Forward Cloudmon alarms, audit events, and application logs to Splunk over Syslog or the Splunk HTTP Event Collector.
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 source | What is forwarded |
| Forward Alarms | Alarms when they are raised, updated, and cleared. Selected by default. |
| Forward Audit Events | Audit events, which record the actions users take in Cloudmon. Selected by default. |
| Forward Application Logs | Cloudmon application logs at warning and error level. Not selected by default. |
Decide how Splunk will receive the data, and collect the matching details.
| Method | What you need |
| Syslog | The host and port of a syslog receiver in your Splunk environment. Use UDP port 514, or TCP for reliable delivery. |
| HTTP Event Collector | A 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. |
Connection fields: the fields depend on the Transport you select.
| Field | Description |
| 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:
| Field | Description |
| Host* | The address of the syslog receiver in your Splunk environment. |
| Port* | The receiver port. The default is 514. |
| Protocol | UDP or TCP. Use TCP for reliable delivery. |
With HTTP / HEC:
| Field | Description |
| 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 Certificate | When on, Cloudmon checks the Splunk server certificate. On by default. |
Log Format fields:
| Field | Description |
| Format* | The message format: RFC 5424 Syslog, CEF (Common Event Format), or Splunk HEC JSON. |
| Splunk Index | The Splunk index to write the events to. Shown with HTTP / HEC. |
| Source Hostname | The 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.
| Issue | What to check |
| Test Connection fails | Check 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 Splunk | Confirm 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 again | The token is not shown again after saving. Create a new token in Splunk and enter it in the integration. |