Splunk® Enterprise

Dashboards and Visualizations

Acrobat logo Download manual as PDF


Splunk Enterprise version 7.2 is no longer supported as of April 30, 2021. 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® Enterprise. For documentation on the most recent version, go to the latest release.
Acrobat logo Download topic as PDF

Use IP addresses to generate a choropleth map

The iplocation command is often the easiest way to generate a map from events with associated IP addresses. If you have IP address data in your events, you can use iplocation to look up their location information in a third-party database and generate location fields in the search results.

Depending on the information available for the IP addresses in your data, iplocation can generate location fields including City, Country, Region, latitude, and longitude in your events. By setting the optional allfields argument to true, you can also add Continent, MetroCode (US only), and Timezone fields.

Geolocation using IP addresses is useful for determining approximate locations, rather than precise addresses. Your Splunk platform instance includes a copy of the GeoLite2-City .mmdb database file, which provides city-level location information for the listed IP addresses.

For more information about the GeoLite2-City file, including instructions for downloading and installing updated versions of the file, see the iplocation command topic in the Search Reference manual.

If you want to map data more precisely, you need to use data with more detailed location information than IP addresses and configure a geospatial lookup with your desired geographic boundaries. See Configure geospatial lookups in the Knowledge Manager Manual to learn more.

Prerequisites

  • Data with associated IP addresses, such as web access logs. The examples in this topic use the sourcetype=access_combined_wcookie data from the Search Tutorial. To follow along with the examples, see Download the tutorial data files and then Upload the tutorial data for instructions on uploading the data.
  • Perform field extraction to isolate the IP addresses as necessary. See Build field extractions with the field extractor in the Knowledge Manager Manual.
  • Familiarize yourself with geospatial visualizations. See Generate a choropleth map to learn more about choropleth maps.
  • Determine what geospatial lookup file you want to use for the boundaries in your choropleth map. To use a lookup other than the us_states and world_countries files that come with Splunk software, see Define a geospatial lookup in Splunk Web in the Knowledge Manager Manual.

Add geographic information to your data

You can retrieve geographic information associated with the IP addresses in your data from a third-party database using the iplocation command.

  1. Navigate to the Search view of the Search & Reporting App.
  2. Type the following into the search bar to refine your search to include the events that contain IP addresses.

    source="tutorialdata.zip" sourcetype=access_combined_wcookie clientip=*

  3. Add the following to your search to use the iplocation command with the name of the IP address field as the argument.

    | iplocation clientip

  4. Verify that new location fields have been added in the Interesting Fields column beside your events.
    In the tutorial data, the City, Country, Region, lat, and lon fields are added to the events.

Generate a choropleth map

Now that you have added fields with geographic information, you can use the stats and geom commands to create a choropleth map visualization.

  1. Building on the search you began in the previous task, use a transforming command to aggregate the data so that you have one row per feature in the geographic feature collection by which you want to map the data.

    | stats count by Country

  2. Add the following to your search to use the geom command to add geographic boundaries to the rows in your table.

    | geom geo_countries allFeatures=True featureIdField=Country

  3. Use the complete search to generate your map

    | stats count by Country| geom geo_countries allFeatures=True featureIdField=Country


    The following table explains the purpose of the two arguments included in this search:

    Argument Purpose
    allFeatures=true Ensures all features in the featureCollection are displayed on the map, even if the aggregated data does not have a value for each feature in the collection.
    featureIdField Provides the name of the field that maps to the features in your geospatial lookup if it has a name other than "featureId".
  4. Run the search.
  5. Select the Visualization tab and select Choropleth Map from the visualization options. If the feature you want to map is numeric, the choropleth visualization generates bins with corresponding shading. If it's categorical, the visualization designates a color for each category.
  6. Adjust the settings of your choropleth map as desired.
    • If the features aren't colored as you expected, it's possible that the values are too concentrated in a particular bin to display properly. Try adjusting the base search to eliminate outliers.
    • See Generate and configure your choropleth map for more information about how to configure your choropleth map.
  7. (Optional) Save your map to a report or dashboard.

The shading in the completed choropleth map represents the number of client IP addresses linked to each country on the map:
Screenshot of finished choropleth map of tutorial data client IP addresses

Last modified on 20 May, 2022
PREVIOUS
Configure a choropleth map
  NEXT
Cluster maps

This documentation applies to the following versions of Splunk® Enterprise: 7.0.0, 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.0.1, 7.3.7, 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.10, 8.1.11, 8.1.12, 8.1.13, 8.1.14, 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, 7.3.8


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