Advanced Visualizations Overview. If you have ever stared at a spreadsheet of server logs and felt your brain go fuzzy, you know that numbers alone do not tell a story. Advanced visualisations solve that problem by turning raw data into interactive charts, graphs, and maps that reveal patterns, trends, and outliers at a glance — and for the SPLK-1003 exam, mastering them is the difference between a analyst who fumbles and one who delivers insights instantly.
Jump to a section
A simple way to picture Advanced Visualizations Overview
25 customers walked into your coffee shop between 8:00 and 9:00 AM on Tuesday, but only 18 of them ordered a latte. You have a basic tally sheet that tells you total customers and total sales, but you cannot see which pastry sells best with a cappuccino or whether your afternoon crowd is bigger than your morning crowd. That tally sheet is like a simple table or bar chart in Splunk — it gives you totals, but it cannot show you the deeper story.
Now imagine you install a digital board behind the counter that updates in real-time. It shows a heat map of the shop floor — red zones where customers queue the longest, green zones where they grab sugar and leave. It also displays a bubble chart where each bubble is a drink size, and the bubble's size shows profit margin. A single line graph tracks how long each customer waits, and next to it, a gauge shows your current stock of milk. You can click any bubble and instantly see which age group orders that drink. That board is an advanced visualisation — it turns raw numbers into a living picture that helps you decide in seconds, not hours. It reveals patterns your basic tally sheet never could: the latte-biscuit combo, the 9:30 AM rush, the silent favourite drink that nobody talks about but everyone buys. This is what advanced visualisations do for machine data — they transform logs and events into interactive, layered stories that surface hidden truths and speed up decision-making.
Without this detailed view, you would guess, not know. With it, you make informed choices — order extra oat milk, hire a second barista for the 9:30 rush, or create a new biscotti deal. Advanced visualisations give you that same superpower for your data: they turn guesswork into knowledge.
Advanced visualisations are a set of chart types and customisation options in Splunk that go beyond the basic bar, line, and pie charts. They include single-value gauges, radial gauges, heat maps, treemaps, choropleth maps, and more. Each visualisation type is designed to answer a specific kind of question about your data, and knowing when to use each one is a core skill for the Power User exam.
To understand why they exist, think about what happens when you search for something in Splunk. Your search command returns results in a table of events. That table is powerful, but it is not visual. A beginner might then use the 'statistics' command to calculate counts or averages, and then click the 'Visualization' tab to pick a bar chart. That works for simple questions — "How many errors per hour?" — but it fails for more complex ones like "Which error types cluster together by region and time of day?" or "How does server CPU usage correlate with memory usage?"
Advanced visualisations exist precisely for these complex questions. They replace a single flat chart with a layered, interactive dashboard component that can show multiple dimensions at once. For example, a heat map can display values across two categories (like day of week and hour of day) using colour intensity. A treemap can show hierarchical data (like website traffic by country, then by city, then by page) as nested rectangles. A gauge shows a single metric against a target range, perfect for monitoring service-level agreements.
Each advanced visualisation has specific configuration options called 'visualisation properties'. These let you adjust colours, labels, axis ranges, legend positions, and drill-down actions. You can format numbers (like showing percentages instead of raw counts), add trend lines, or set thresholds that change colour when a value goes above or below a limit. This customisation is what transforms a generic chart into a precise communication tool.
Here is a list of the most common advanced visualisations you will see on the exam:
Single Value: Shows one number, often with a trend indicator (up/down arrow) and a sparkline (a small line chart showing change over time). Use it for key metrics like "current active users" or "last hour's error count".
Radial Gauge: A semi-circular gauge that displays a value on a scale, often with coloured bands (green, yellow, red). Perfect for showing how close a metric is to a target threshold.
Markdown: Not a chart, but a panel that lets you add formatted text, images, or links to your dashboard. Use it for instructions, titles, or context.
Heat Map: A grid of coloured cells where each cell represents the intersection of two categories (like hour of day and day of week). Colour intensity shows the magnitude of the value. Great for spotting peaks and troughs over time.
Treemap: A space-filling chart of nested rectangles. Each rectangle represents a category, and its size shows a metric (like count or sum). Colours can show a different metric. Ideal for hierarchical data with many subcategories.
Choropleth Map: A geographic map where regions (countries, states, postcodes) are shaded based on a data value. Requires geographic data in your events (like IP addresses or coordinates).
Event Timeline: A visual representation of events over time, showing patterns and clusters. Useful for incident analysis.
To create an advanced visualisation, you start with a search that produces the right data structure. For a gauge, you need a single value. For a treemap, you need fields that form a hierarchy (like region > department > product). For a heat map, you need two categorical fields and one numeric field. If your data is not in the right shape, Splunk cannot draw the chart — you may need to use 'chart' or 'timechart' commands to reshape it.
Once the visualisation is on a dashboard, you can make it interactive by adding 'drilldown' actions. Drilldown lets a user click on a part of the chart (like a bar or a cell) to run a new search or open another dashboard. This turns a static chart into a live exploration tool.
Why does this matter for real-world work? Because IT professionals do not have time to sift through raw logs. They need to see at a glance whether a server is overheating, whether a website is slow in a specific region, or whether an attack is coming from one IP range. Advanced visualisations compress that information into a single glance, cutting investigation time from hours to seconds.
For the SPLK-1003 exam, you must know the names, use cases, and basic configuration of each advanced visualisation type. You must understand that each type requires a specific data shape, and that you can customise colours, labels, and thresholds. The exam loves to test your ability to pick the right visualisation for a given scenario — for example, "Which visualisation would best show the distribution of error codes by department?" The answer is often a treemap, not a pie chart, because the treemap can handle many categories and also show hierarchy.
1. Determine the analytic question
Before you pick a visualisation, decide what you need to learn from the data. Are you comparing two categories over time? That suggests a heat map. Are you looking at a single metric against a target? That is a gauge. This step prevents you from forcing data into the wrong chart.
2. Write a search that produces the correct data shape
Each visualisation expects a particular table structure. For a treemap, you need parent and child fields with a numeric measure. Use commands like 'chart', 'timechart', or 'stats' to reshape your data. For example, '... | stats count by region, department' produces two grouping fields and one numeric field, suitable for a treemap.
3. Select the visualisation type from the Visualization tab
After running your search, click the 'Visualization' tab and pick the type that matches your analytic question and data shape. Splunk will attempt to render it immediately. If the chart looks wrong, review your data shape.
4. Customise appearance and formatting
Use the 'Format' panel to change colours, labels, axis ranges, number formats, and threshold colours. For a radial gauge, you can set the green/yellow/red zones. For a heat map, you can choose a colour palette (like blue-white-red) and specify the range of values.
5. Add the visualisation to a dashboard and configure drilldown
Click 'Save As' and choose 'Dashboard Panel'. Give the panel a title. Then, in the dashboard editor, click 'Edit' on the panel and set a drilldown action — for example, 'link to search' that passes clicked field values. This makes your visualisation interactive.
6. Test interactivity and adjust
View the dashboard in 'View' mode and click on various parts of the visualisation (cells, rectangles, gauge segments). Ensure the drilldown opens the expected search or dashboard. Adjust colours or labels if the chart is hard to read.
Let us walk through a real scenario. You work at 'ShopFast', a mid-sized online retailer. The IT operations team gets an alert: the website is loading slowly for customers in Australia. The on-call engineer opens a Splunk dashboard that monitors web server performance. On this dashboard, there are several advanced visualisations.
First, a single-value panel shows 'Average Page Load Time (last 15 minutes)' with a sparkline. The number is 4.2 seconds — well above the 2-second target. The sparkline shows a sharp upward trend starting 20 minutes ago. This single panel tells the engineer: something changed recently and it is getting worse.
Next, the engineer looks at a heat map titled 'Page Load Time by Hour and Region'. The rows are hours of the day, the columns are regions (like Australia, Europe, North America). The engineer sees that the Australia row is dark red for the last three one-hour blocks, while other regions are green. This tells the engineer the problem is isolated to Australia, not a global issue.
Then, the engineer examines a treemap of 'Error Codes by Server Group'. Each rectangle is a server group (like 'Web Tier', 'Database', 'CDN'), and inside each rectangle are smaller rectangles for error codes. The engineer notices that a large rectangle labelled 'Database' is taking up most of the space, and inside it, a small orange rectangle says 'Connection Timeout'. This suggests the database servers in Australia (or serving Australian traffic) are timing out.
Using a radial gauge for 'Database CPU Utilization', the engineer sees the needle is in the red zone at 95%. That confirms the database is overloaded.
Finally, the engineer drills down: they click on the 'Database' rectangle in the treemap, which opens a new search showing all connection-timeout events from those servers. Within two minutes, the engineer knows the root cause: a database node in the Sydney data centre is failing and needs a restart. Without advanced visualisations, the engineer would have had to run half a dozen separate searches, compare numbers manually, and guess at correlations. The visualisations did the pattern-finding for them.
Here is a step-by-step of what the IT professional actually does with advanced visualisations in their day-to-day work:
Step 1: Define the question. For example, 'Is our website slow, and if so, where?'
Step 2: Build a search that returns the right shape of data. For the heat map, that means a search that returns a table with fields like _time, region, and average_load_time.
Step 3: Select the visualisation type that best answers the question. For showing a metric over two dimensions, they choose a heat map.
Step 4: Customise the visualisation properties — set colour palette to Red-Green diverging so high values are red, add axis labels, set the time range to last 4 hours.
Step 5: Add the visualisation to a dashboard and configure drilldown actions for deeper investigation.
Step 6: Share the dashboard with the team so everyone has the same real-time view.
This workflow is not just for troubleshooting. It applies to capacity planning, security monitoring, business analytics, and compliance reporting. Every IT professional who uses Splunk inevitably builds dashboards with advanced visualisations to communicate complex data clearly. The SPLK-1003 exam tests your ability to design these dashboards — to choose the right visualisation, format it correctly, and explain why one chart type is better than another.
The SPLK-1003 exam's Certified Power User test specifically assesses Objective 2.1: 'Create and customize advanced visualizations for data analysis.' This means you will get multiple-choice questions that ask you to identify visualisation types, match visualisations to use cases, and understand customisation options. Expect these exact concepts to appear:
Visualisation types: Single Value, Radial Gauge, Markdown, Heat Map, Treemap, Choropleth Map, Event Timeline. You must be able to name each one from a screenshot or description.
Use case matching: The exam loves a question like 'You need to show the distribution of error codes across server groups, with many subcategories. Which visualisation should you use?' The correct answer is Treemap, because it handles hierarchy and many categories without overflowing.
Data shape requirements: Questions will test your understanding of what each visualisation needs. For example, 'Which of the following is required to create a choropleth map?' Answer: A geographic field (like country or coordinates) and a numeric value.
Customisation properties: You need to know where to change colours, add trend lines, format numbers, and set threshold colours. The exam may present a screenshot of the Visualization editor and ask what settings are available.
Dashboard integration: You must understand how to add a visualisation to a dashboard, how to set drilldown actions, and how to link a visualisation to a new search.
Common traps the exam sets:
Trap: Offering a basic chart (like a bar chart) when the question describes hierarchical data. You must recognise that a treemap is more appropriate.
Trap: Confusing a radial gauge with a single value panel. A radial gauge shows a value on a scale with threshold zones; a single value panel shows just the number with optional sparkline.
Trap: Thinking that any visualisation works with any data. They will give you a scenario where the data has only two fields, and ask which visualisation is possible. For example, if you only have a field 'status_code' and a count, a heat map (which requires two categorical fields) would not work.
Trap: Forgetting that Markdown is a visualisation type. It is easy to dismiss as 'just text', but the exam counts it.
Here is a list of key definitions to memorise:
Single Value: One number, optional trend arrow and sparkline.
Radial Gauge: Semi-circular gauge with coloured threshold bands.
Markdown: Text panel with formatting (headings, links, images).
Heat Map: Coloured grid for two categorical dimensions.
Treemap: Nested rectangles for hierarchical data.
Choropleth Map: Shaded geographic regions.
Event Timeline: Graphical display of event sequences over time.
The exam also tests the 'Why' behind each visualisation. For instance, 'Why would you choose a heat map over a table?' The answer: a heat map uses colour to instantly show patterns that a table of numbers would hide. You need to be able to articulate that advantage.
Finally, be ready for questions about the 'Visualization' tab in the Search & Reporting app. They might ask which icon corresponds to which chart type, or what the 'Format' button does. Spend time in the lab practising with the Splunk interface before the exam. Hands-on experience is the best way to solidify these concepts.
Advanced visualisations are purpose-built for specific data structures, so always match the visualisation type to the shape of your search results.
A single value visualisation includes a sparkline and a trend arrow, giving you context about change over time, not just a static number.
A treemap uses nested rectangles to display hierarchical data, making it superior to a pie chart when you have more than a few categories.
A heat map uses colour intensity across two categorical dimensions to reveal patterns that would be hidden in a table of numbers.
Drilldown actions can be added to any advanced visualisation to make dashboards interactive and allow deeper data exploration.
Markdown panels are officially recognised as advanced visualisations and can hold formatted text, images, and links for dashboard context.
Choropleth maps require geographic fields (country, region, or coordinates) derived from data enrichment, not just raw IP addresses.
Customisation of colours, labels, thresholds, and number formatting is done in the Visualisation properties panel, not in the search itself.
These come up on the exam all the time. Here's how to tell them apart.
Single Value
Shows one number with a sparkline and trend arrow.
Lacks threshold zones or target markings.
Best for a quick headline metric without context of limits.
Radial Gauge
Displays value on a semi-circular scale with coloured threshold bands.
Explicitly shows how far the value is from a target.
Best for monitoring metrics against defined service-level agreements.
Heat Map
Uses colour intensity across a grid of two categorical dimensions.
Best for spotting peaks and troughs over time or across categories.
Requires exactly two grouping fields and one numeric measure.
Treemap
Uses nested rectangle size and colour to show hierarchy and magnitude.
Best for displaying many subcategories within broader groups.
Requires hierarchical parent-child data structure.
Choropleth Map
Shades geographic regions like countries or states.
Requires geographic fields (country, region, coordinates).
Best for location-based patterns (e.g., traffic by country).
Heat Map
Uses a grid non-geographic categories (e.g., day of week vs hour).
Requires two categorical fields (not necessarily geographic).
Best for temporal or cross-category patterns without geography.
Mistake
All advanced visualisations are just prettier versions of the same basic charts.
Correct
Each advanced visualisation type answers a fundamentally different kind of question — you cannot replace a treemap with a bar chart when you have hierarchical data.
Beginners often see visualisation as decoration rather than a tool for analysis. They think any chart will do, so they miss the structural requirement of each type.
Mistake
You can create any advanced visualisation from any search result without changing the data.
Correct
Every advanced visualisation requires a specific data shape — for example, a heat map needs exactly two categorical parent fields and one numeric measure field.
Splunk's interface lets you pick any visualisation type, but if your data is not shaped correctly, it either fails or produces a meaningless chart. Beginners assume 'it will work out' and waste time.
Mistake
The single value visualisation is just like a stat table value.
Correct
A single value panel includes a sparkline (trend graph) and can show a change indicator (up/down arrow), giving context that a raw number lacks.
Because the label says 'Single Value', beginners think it is simply a number on a dashboard, ignoring the built-in trend analysis that makes it advanced.
Mistake
Markdown panels are not real visualisations — they are just text notes.
Correct
Splunk officially classifies Markdown as an advanced visualisation type, and the exam tests your ability to use it for dashboard headings, help text, and embedded media.
Because Markdown does not involve numbers or charts, beginners mentally categorise it as 'not a visualisation', but it is explicitly listed in the exam objectives.
Mistake
Drilldown actions are only for basic bar charts.
Correct
You can add drilldown to any advanced visualisation — clicking a cell in a heat map or a rectangle in a treemap can trigger a new search or link to another dashboard.
Beginners assume interactivity is only for simple charts. They do not realise that advanced visualisations support the same drilldown logic, which is a key part of dashboard interactivity.
Mistake
A choropleth map works automatically if you have IP addresses in your data.
Correct
Splunk needs explicit geographic fields (like country, region, or latitude/longitude) to draw a choropleth map — IP-to-location lookup is a separate step using the 'iplocation' command.
Because maps seem magical, beginners think Splunk 'just knows' where data comes from. They do not understand the underlying data pipeline needed to enrich events with location.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
A radial gauge displays a value on a semi-circular scale with coloured threshold zones (green, yellow, red), ideal for monitoring against a target. A single value visualisation shows one number with a sparkline and trend arrow, perfect for a headline metric.
No, a heat map requires exactly two categorical 'parent' fields (like day and hour) and one numeric measure field. If you only have one category, use a bar chart instead.
Use the Markdown visualisation panel. In the panel source, write HTML or Markdown code, for example: 'Click <a href="https://example.com">here</a> for documentation.' Then save as a dashboard panel.
That usually means the field you selected for rectangle size (usually a count or sum) has the same value for all rows, or you accidentally selected a categorical field for the size dimension. Double-check your 'Split by' fields.
They work in both. You can preview them in the 'Visualization' tab of the Search & Reporting app, and then save them to a dashboard for persistent use.
A choropleth map shades geographic regions (like countries or states) based on a numeric value. Splunk requires geographic fields (country, region, or coordinates) that come from enrichment commands like 'iplocation' or lookups.
You've finished Advanced Visualizations Overview. Continue through the SPLK-1003 study guide to build a complete picture of the exam.
Done with this chapter?