Splunk® Enterprise

Dashboards and Visualizations

Splunk Enterprise version 9.0 will no longer be supported as of June 14, 2024. See the Splunk Software Support Policy for details. For information about upgrading to a supported version, see How to upgrade Splunk Enterprise.

Upload and configure your data

Use the Splunk Web interface to upload the drought monitor data to your Splunk platform instance.

Prerequisite


Steps

Follow these steps to upload the drought monitor data to your Splunk platform instance:

  1. Unzip the us_drought_monitor.csv.zip file.
  2. Click Settings > Add Data.
  3. Click Upload files from my computer.
  4. Click Select Files and select us_drought_monitor.csv from your files.
  5. Click Open > Next.
  6. Ensure Source type is set to csv and that each of the fields is named correctly.
  7. Configure the timestamps according to the date of capture. In this file, this information is located in a field entitled MapDate.
    1. Click Timestamp.
    2. Select Extraction > Advanced.
    3. Enter MapDate in the Timestamp fields box.
    4. Under Timestamp format, enter the strptime() string %Y%m%d to allow the indexer to read in the date in the correct format. See Configure timestamp recognition in the Getting Data In Manual for more information about strptime() strings.
  8. (Optional) Save this configuration as a new input type.
    1. Click Save As to save this input type.
    2. Enter drought_csv in the Name field.
    3. Click Save.
  9. Click Next. Ensure the input settings are correct.
  10. Click Review and then click Submit to upload the file.
  11. Click Start Searching to view your data.

Next step

Download a California counties shapefile

Last modified on 01 August, 2019
Locate and download USDM data   Download a California counties shapefile

This documentation applies to the following versions of Splunk® Enterprise: 7.0.0, 7.0.1, 7.0.2, 7.0.3, 7.0.4, 7.0.5, 7.0.6, 7.0.7, 7.0.8, 7.0.9, 7.0.10, 7.0.11, 7.0.13, 7.1.0, 7.1.1, 7.1.2, 7.1.3, 7.1.4, 7.1.5, 7.1.6, 7.1.7, 7.1.8, 7.1.9, 7.1.10, 7.2.0, 7.2.1, 7.2.2, 7.2.3, 7.2.4, 7.2.5, 7.2.6, 7.2.7, 7.2.8, 7.2.9, 7.2.10, 7.3.0, 7.3.1, 7.3.2, 7.3.3, 7.3.4, 7.3.5, 7.3.6, 7.3.7, 7.3.8, 7.3.9, 8.0.0, 8.0.1, 8.0.2, 8.0.3, 8.0.4, 8.0.5, 8.0.6, 8.0.7, 8.0.8, 8.0.9, 8.0.10, 8.1.0, 8.1.1, 8.1.2, 8.1.3, 8.1.4, 8.1.5, 8.1.6, 8.1.7, 8.1.8, 8.1.9, 8.1.11, 8.2.0, 8.2.1, 8.2.2, 8.2.3, 8.2.4, 8.2.5, 8.2.6, 8.2.7, 8.2.8, 8.2.9, 8.2.10, 8.2.11, 8.2.12, 9.0.0, 9.0.1, 9.0.2, 9.0.3, 9.0.4, 9.0.5, 9.0.6, 9.0.7, 9.0.8, 9.0.9, 9.0.10, 9.1.0, 9.1.1, 9.1.2, 9.1.3, 9.1.4, 9.1.5, 9.1.6, 9.1.7, 9.2.0, 9.2.1, 9.2.2, 9.2.3, 9.2.4, 9.3.0, 9.3.1, 9.3.2, 8.1.10, 8.1.12, 8.1.13, 8.1.14


Was this topic useful?







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