Splunk® Enterprise

Getting Data In

Download manual as PDF

Splunk Enterprise version 6.x is no longer supported as of October 23, 2019. See the Splunk Software Support Policy for details. For information about upgrading to a supported version, see How to upgrade Splunk Enterprise.
This documentation does not apply to the most recent version of Splunk. Click here for the latest version.
Download topic as PDF

About Windows data and Splunk Enterprise

Splunk Enterprise is an extensible, powerful tool. It can index many different kinds of Windows data. This data can be pretty much anything - a log file, a directory full of files, an event log channel, the Registry, or Active Directory.

Splunk provides several specialized inputs to monitor Windows data, including:

  • Windows Event Logs: Splunk can monitor logs generated by the Windows Event Log service on any event log channel that is available on the machine. You can collect logs on the local machine, or you can gather log data remotely using either a universal forwarder or Windows Management Instrumentation (WMI).
  • Performance monitoring: You can collect performance data on Windows machines with Splunk and then alert or report on that data. Any performance counter that is available in Performance Monitor is also available to Splunk. You can monitor performance locally or remotely through a universal forwarder or WMI.
  • Remote monitoring over WMI: Splunk can use WMI to access event log and performance data on remote machines.
  • Active Directory monitoring: Splunk can audit any changes to the Active Directory - including changes to user, group, machine, and group policy objects. You can forward Active Directory data to another Splunk Enterprise server.

These specialized inputs are available only on Windows installations of Splunk Enterprise. You also have available the standard set of Splunk Enterprise inputs, such as "files and directories," the network monitoring inputs, and scripted inputs.

The Splunk App for Windows

The Splunk App for Windows provides pre-built data inputs, searches, reports, alerts, and dashboards for Windows server and desktop management. You can monitor, manage, and troubleshoot Windows operating systems from one place. The app includes scripted inputs for CPU, disk I/O, memory, event logs, configurations, and user data, plus a web-based setup UI for indexing Windows event logs. This free app makes getting started with Splunk Enterprise on Windows easier.

Initial considerations for deploying Splunk Enterprise on Windows

When installing and deploying Splunk Enterprise on Windows, consider the following:

  • Authentication. To perform any operations on remote Windows machines in your network, Splunk Enterprise needs the appropriate access to your Active Directory domain or forest. This means that Splunk Enterprise must run as a user with those credentials. It is best practice to have these credentials available before proceeding with any kind of deployment. Review "Considerations for deciding how to monitor remote Windows data" for additional information about how best to accomplish this task.
  • Disk bandwidth. Splunk Enterprise indexers require lots of disk I/O bandwidth, particularly when indexing large amounts of data. You must pay particular attention to systems that have any program that intermediates between Splunk Enterprise and the operating system installed. This includes anti-virus software. Make sure that you configure any installed anti-virus software to avoid monitoring Splunk Enterprise directories or processes, as such scans will significantly reduce performance.
  • Shared servers. Before installing Splunk Enterprise on a server that runs other services, read "Hardware capacity planning for your Splunk deployment" in the Installation manual. This is particularly important if you plan to install Splunk on a domain controller, or a computer running memory-intensive services such as Exchange, SQL Server or a virtual host server.

The most efficient way to gather data from any Windows server is to install universal forwarders on the machines from which you want to gather data. Universal forwarders have a small footprint and use very limited resources. In some cases, such as Registry monitoring, you must use a forwarder, as you cannot poll Registry changes remotely.

Last modified on 22 October, 2014
Configure your inputs
What Splunk Enterprise does with your data (and how to make it do it better)

This documentation applies to the following versions of Splunk® Enterprise: 6.0, 6.0.1, 6.0.2, 6.0.3, 6.0.4, 6.0.5, 6.0.6, 6.0.7, 6.0.8, 6.0.9, 6.0.10, 6.0.11, 6.0.12, 6.0.13, 6.0.14, 6.0.15, 6.1, 6.1.1, 6.1.2, 6.1.3, 6.1.4, 6.1.5, 6.1.6, 6.1.7, 6.1.8, 6.1.9, 6.1.10, 6.1.11, 6.1.12, 6.1.13, 6.1.14

Was this documentation topic helpful?

Enter your email address, and someone from the documentation team will respond to you:

Please provide your comments here. Ask a question or make a suggestion.

You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters