Splunk Cloud

Dashboards and Visualizations

Download manual as PDF

Download topic as PDF

(Optional) Use Trellis view to visualize multiple aggregate functions

Sometimes it's useful to visualize more than one value shaded over the same map region. If you want to invoke multiple aggregate functions to create your choropleth statistics table, use the Trellis view to compare them side-by-side.

Prerequisites

Steps

  1. When you're constructing the search that generates your choropleth statistics table, invoke multiple functions in the stats command. In this example, we compare average, maximum, and minimum drought scores:

    source="us_drought_monitor.csv" State = CA date_year=2018 | rex field=County "(?<County>.+) County" | eval droughtscore=D1 + D2*2 + D3*3 + D4*4 | stats avg(droughtscore) as "Average 2018 Drought Score" max(droughtscore) as "Max 2018 Drought Score" min(droughtscore) as "Min 2018 Drought Score" by County

  2. Add the following to your search to use the geom command in your SPL search to add the corresponding geospatial polygons to your table:

    | geom ca_county_lookup featureIdField=County

  3. Run the search.
  4. In the Visualizations tab, notice that no shaded features appear because you have provided more than one aggregate value to map. Resolve this by selecting Trellis layout.
  5. Check the box labeled Use Trellis Layout.
  6. Under Split By, select Aggregations (3).
  7. Scroll and zoom to California in each map to compare the shading patterns of the three different values.
  8. Save the trellis map to your dashboard.

The Trellis map provides a visualization of three aggregate values side-by-side, to provide a fuller picture of drought conditions across California in 2018:

Screenshot of three side-by-side choropleth maps of average, minimum, and maximum California drought severity by county in 2018

PREVIOUS
Generate a choropleth map
  NEXT
Use trellis layout to split visualizations

This documentation applies to the following versions of Splunk Cloud: 7.2.7, 7.0.0, 7.0.2, 7.0.3, 7.0.8, 7.1.3, 7.1.6, 7.2.3, 7.2.4, 7.2.6, 7.0.5


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