a data analytics platform that helps businesses collect, analyze, and visualize data. It's used for IT operations, cyber security, application management, and more...
Splunk is designed to accept an immense amount of syslog data from almost any device on the network. You can send firewall logs, windows event logs, switch logs, webiste logs, PowerShell queries and more.
Many features of Splunk like Data Collection & Ingestion, Search & Querying, Data Indexing & Storage, Dashboards & Visualization, Alerting & Monitoring, Security & Compliance, Observability & IT Operations, Cloud & Hybrid Deployments, Integration & Extensibility.
Splunk's architecture is designed to handle vast amounts of machine data in real-time, providing the infrastructure necessary for data collection, indexing, searching, and analysis. The core components of this architecture include Forwarders, Indexers, and Search Heads, each playing a vital role in the overall system's efficiency and scalability.
Splunk is a powerful platform for collecting, analyzing, and visualizing machine data in real-time. It helps businesses turn raw logs and events into actionable insights, improving security, IT operations, and business analytics. You can generate scheduled reports and even set alerts!
When installing Splunk, selecting the right architecture is critical to ensure optimal performance and scalability. The architecture depends on factors like the volume of data, the number of users, and the desired availability.
Taking a deeper look into Splunk and sharing some pointers. Other than the simplicity of centralized logging, real-time monitoring is the ability to try before you buy. I currently run Splunk in house using the limted free licnese. It is limited to 500MB of data per day but that’s quite a bit of information and perfect for testing or lab environments.
The setup of a basic Splunk server is quite simple; there is support for MS Windows, Linux and Containers.
Post Installation Steps:
Note:
You can test out Splunk and run Splunk on Windows workstations or run it as a
container on Linux which has been my preferred solution.
Check out my video...
Update the rsyslog.conf
sudo nano /etc/rsyslog.conf
Update with Splunk IP and Port:
*.* @@192.168.254.34:514
Restart Rsyslog
sudo systemctl restart rsyslog
Once you start seeing data in the index you created you could create queries like the one below to filter on specific data send from RHEL.
sourcetype=linux_syslog
You can install the UF provided free from Splunk to setup the forwarding of your Windows servers to Splunk. Another option is to configure group policy to forward event logs.
Just remember to click on the options durinig installation to select what you information to gather. It will not gather any information if you don't select it.
Copyright © 2025 Data Locks - All Rights Reserved.
Author: Scott W. Head