Creating Dashboard Drilldowns with Time Range
An admin wants to create a dashboard that shows the count of errors by sourcetype over the last 7 days, with the ability to click on a sourcetype to drill down to a detailed search. Which visualization and configuration supports this?
Quick Answer
This scenario has two separate requirements bundled together, a visualization suited to comparing counts across categories, and a mechanism for letting a user click through to more detail, and each one is solved by a different part of the answer. A bar chart is the appropriate visualization choice because it's built for comparing discrete counts across categories, here, error counts by sourcetype, which is a comparison task, not a trend-over-time task the way a line chart would suggest, and not something a pie chart handles well once there are more than a handful of categories to compare. Drilldown, meanwhile, isn't something you configure inside the search string itself; it's a dashboard-level behavior defined in the dashboard XML, which tells Splunk what should happen when a user clicks an element of the visualization, in this case launching a more detailed search. Keeping these two concerns separate matters: the choice of chart type answers how the data should be displayed, while the drilldown configuration in the XML answers what happens when someone interacts with it, and conflating the two, for example expecting drilldown to be set via a search command or a link embedded in SPL, is a common mistake. When an exam question pairs a visualization requirement with an interactive drilldown requirement, expect the chart type and the XML drilldown setting to be evaluated as two distinct, separate answers.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use a bar chart and set the 'drilldown' option to 'search' in the dashboard XML.
A bar chart is suitable for comparing counts across sourcetypes and allows drilldown via the dashboard XML configuration. Option A is incorrect because a line chart is typically used for trends over time, not for comparing counts across categories, and drilldown is not configured via the search command but in the dashboard XML. Option C is incorrect because pie charts are less effective when there are many categories, and drilldown is not configured via the search command. Option D is incorrect because tables do support drilldown, but the configuration described is not standard; drilldown is set in the dashboard XML, not via a 'link' in the search string.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Use a line chart and set the 'drilldown' to 'search' in the search command.
Why it's wrong here
Line charts are for trends, and drilldown is configured in dashboard XML, not in the search command.
- ✓
Use a bar chart and set the 'drilldown' option to 'search' in the dashboard XML.
Why this is correct
Bar charts compare counts effectively and drilldown is configured in dashboard XML.
- ✗
Use a pie chart and set the 'drilldown' option to 'search' in the dashboard XML.
Why it's wrong here
Pie charts can have drilldown but are not ideal for many sourcetypes; also the configuration is correct.
- ✗
Use a table and set the 'link' in search string.
Why it's wrong here
Tables can have drilldown, but the configuration is typically done via dashboard XML, not in the search string.
Go deeper
Related to this question
About these practice questions
Courseiva writes every SPLK-1002 question from scratch — 475 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more way this is tested on SPLK-1002
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. An admin creates a dashboard with a timechart panel that drills down to a search for that time range. The drilldown search works but does not include the time range. What is the likely cause?
hard- ✓ A.The drilldown is set to 'search' without including tokens for time.
- B.The timechart uses a fixed time range in the search string.
- C.The dashboard's time input is disabled.
- D.The drilldown is configured to use 'range' token but the panel's time range is not passed.
Why A: When a drilldown is configured as a simple search without tokens to pass the time range, the time range from the panel is not inherited. The drilldown performs a search using the default time range (e.g., All time) instead of the panel's time range. To include the time range, tokens like $earliest$ and $latest$ must be added to the drilldown search string. Options B, C, and D are incorrect: B would maintain the time if fixed, C affects the dashboard overall but not necessarily the panel's drilldown, and D would actually pass the time range correctly.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This SPLK-1002 practice question is part of Courseiva's free Splunk certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SPLK-1002 exam.