Splunk Cloud

Getting Data In

Acrobat logo Download manual as PDF


Acrobat logo Download topic as PDF

What data can I index?

The Splunk platform can index any kind of data. In particular, the Splunk platform can index any and all IT streaming, machine, and historical data, such as Microsoft Windows event logs, web server logs, live application logs, network feeds, metrics, change monitoring, message queues, archive files, and so on.

Types of data sources in Splunk Cloud

Splunk Cloud provides tools to configure many kinds of data inputs, including those that are specific to particular application needs. Splunk Cloud also provides the tools to configure any arbitrary data input types. In general, you can categorize Splunk Cloud inputs as follows:

  • Files and directories
  • Network events
  • Windows sources
  • HTTP Event Collector (HEC)
  • Metrics

Files and directories

A lot of data comes directly from files and directories. You can use universal and heavy forwarders to monitor those files and directories and send them to Splunk Cloud. As a best practice, install universal forwarders on every machine where you want to monitor files and directories and send that data to a heavy forwarder which then sends the data to Splunk Cloud. To monitor files and directories, see Get data from files and directories.

Network events

You might want to collect data from network ports, such as network data from machines that run syslog. To do this in Splunk Cloud, use a heavy or universal forwarder to collect the network data and then send that data to Splunk Cloud. To get data from network ports, see Get data from TCP and UDP ports.

Windows sources

To get data from Windows sources into Splunk Cloud, install the Splunk Add-on for Windows on your universal forwarder. In this scenario, you can use a deployment server to deliver the Splunk Add-on for Windows to the Windows machines you want to monitor. The add-on collects the data and sends it to Splunk Cloud.

For additional information on getting Windows data into Splunk Cloud, see Get Windows Data into Splunk Cloud in the Splunk Cloud Admin Manual.

HTTP Event Collector

In Splunk Cloud, you can use the HTTP Event Collector to get data directly from a source with the HTTP or HTTPS protocols. For more information, see The HTTP Event Collector endpoint.

Metrics

You can also get metrics data from your technology infrastructure, security systems, and business applications. For more information, see Metrics.

Types of data sources in Splunk Enterprise

Because Splunk Enterprise is on-premises, you can either get data into the instance directly or use universal or heavy forwarders to get data in. In general, you can categorize Splunk Enterprise inputs as follows:

  • Files and directories
  • Network events
  • Windows data
  • Other sources

Files and directories

You can use the files and directories monitor input processor to get data from files and directories. To monitor files and directories, see Get data from files and directories.

Network events

You can index data from any network port, such as remote data from syslog-ng or any other application that transmits over the TCP protocol. It can also index UDP data, but use TCP whenever possible for enhanced reliability.

Splunk Enterprise can also receive and index SNMP events and alerts fired off by remote devices.

To get data from network ports, see Get data from TCP and UDP ports in this manual.

To get SNMP data, see Send SNMP events to your Splunk deployment in this manual.

Windows data

The Windows version of Splunk Enterprise accepts a wide range of Windows-specific inputs directly. With Splunk Web, you can configure the following Windows-specific input types:

  • Windows Event Log data
  • Windows Registry data
  • Windows Management Instrumentation (WMI) data
  • Active Directory data
  • Performance monitoring data

To index and search Windows data on a non-Windows instance of Splunk Enterprise, you must first use a Windows instance to gather the data. See Considerations for deciding how to monitor remote Windows data.

For a more detailed introduction to using Windows data in Splunk Enterprise, see Monitoring Windows data in this manual.

Other sources

Splunk Enterprise can collect the following data sources directly:

  • You can use the HTTP Event Collector to get data directly from a source with the HTTP or HTTPS protocols. See The HTTP Event Collector endpoint.
  • You can also get metrics data from your technology infrastructure, security systems, and business applications. See Metrics.
  • You can monitor First In, First Out (FIFO) queues. See Monitor First In, First Out (FIFO) queues.
  • You can get data from APIs and other remote data interfaces and message queues. See Scripted inputs.
  • You can define a custom input capability to extend the Splunk Enterprise framework. See Modular inputs.

Get started with getting data in

Now that you know what kind of data the Splunk platform can index, you can start getting data in to the Splunk platform. See Get started with getting data in.

Last modified on 31 March, 2021
  NEXT
Get started with getting data in

This documentation applies to the following versions of Splunk Cloud: 7.0.13, 8.2.2106, 8.0.2006, 8.0.2007, 8.1.2008, 8.1.2009, 8.1.2011, 8.1.2012 (latest FedRAMP release), 8.1.2101, 8.1.2103, 8.2.2104, 8.2.2105


Was this documentation topic helpful?

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