IN THIS ARTICLE
Outlines how to use Splunk with Qumulo Core audit logging
- Admin privileges required
- Cluster running Qumulo Core 2.12.0 and above
- Qumulo Core Audit Logging configured on your cluster
Audit logging in Qumulo Core provides a mechanism for tracking filesystem and cluster configuration operations.
Once configured, audit logging generates an audit log entry based upon any cluster configuration change or filesystem operation. This log message body consists of multiple fields in a CSV (comma separated) format as shown below:
If you have a cluster that is moderately busy, it is possible for audit logging to generate over 2GB of data within 1 to 2 days. With this amount of data, it becomes exceedingly difficult to parse through the logs to find the one event that you are looking for. And while Qumulo Core generates the audit logs, it does not parse, analyze, index or visualize the data contained in the logs. This is where a third party search analytics engine like Splunk can assist you.
Splunk captures, indexes, and correlates real-time data in a searchable repository to generate graphs, reports, alerts, dashboards, and visualizations. It then takes this real-time data so that you can search, monitor and examine the results via a web-style interface.
Set Up the Qumulo Source Type
- Log in to the Splunk Web UI as an Administrator.
- Select Settings -> Data -> Source Types.
- Click the New Source Type button.
- Set the name to Qumulo Audit Log.
- Click Save.
Set up the Data Input for Syslog over TCP
- Select Settings -> Data -> Data inputs.
- In the Local inputs, TCP section, click Add new.
- Set the TCP port. We chose 514 in our example which is the default syslog port. You could choose a different port as well.
- Click Next.
- Select Qumulo Audit Log as the source type.
- Select Search and reporting (or the App context of your choosing).
- Click Review.
- Click Submit.
Set up the Field Extraction for Qumulo's Logs
- Click Settings -> Fields.
- Click Add new in the Field extractions section.
- Select Destination app Search.
- Name the extraction. We named it “Qumulo Field Extraction”.
- Apply to sourcetype named “Qumulo Audit Log”.
- Set Type to Inline.
- Paste this regular expression into the Extraction/Transform field (this should all be one line in the Splunk text box.
<[0-9]+>[0-9] (?<timestamp>[^ ]+) (?<hostname>.*)?[-](?<node_id>[0-9]+) (?<app_name>[^ ]+) [-] [-] [-] (?<client_ip>[^,]+)[,]"(?<user>.*)?",(?<protocol>[^,]+),(?<op>[^,]+),(?<status>[^,]+),(?<id>[^,]+),"(?<object1>.*)?","(?<object2>.*)"
- Click Save.
Point the Qumulo Audit Log at the Splunk server
- Set up Audit to point at the Splunk server and port (514 in our case).
Review the Splunk Results
- Click Search & Reporting.
- Click Source types > Qumulo Audit Log.
- Take a look at all that data about who is doing what, when, and where on your Qumulo cluster via Splunk.
You should now be able to successfully use Splunk with Qumulo Core audit logging
Like what you see? Share this article with your network!