@philipp  the reason why I had asked those question was to gauge how you can create re-usable sections in your dashboard. 1) Using tokens for SPLs inside same panel will help you a bit with the dropdown options running same search/panel but with different SPL with token. (All will still need to show all panels). 2. On similar lines as above, even Prebuilt Panel in your case will take the panels out of the current Simple XML and place them as separate code. It will only help you reduce actual lines of Simple XML code for various Dropdown options like Component and Environment as they can be passed to Prebuilt panels as tokens. 3. If you had slight design change to show same type of visualization like all Columns charts together and all Line charts together, you could have taken advantage of Trellis layout to split by Component and Environment. Then you will actually have only two panels searches one for Column Chart and another for Line chart and based on the dropdown value the Chart Splits will happen dynamically (including All condition). 4. Best fit seems to be Simple XML JS extension with Splunk JS stack to build viz based on options selected. Simple XML will only pass the Search to be executed and possibly chart type/config. While this would be helpful to reduce code if you have several searches and each search splitting out in several charts, you are right that code reduction will result in complexity introduced by the JS layer. You have to pick and choose how much Simple XML code you want to reduce vs option you can adopt. Also is the code reduction for reducing the disk usage by Simple XML dashboard or for better readability by developers (for the later Simple XML source code editor does provide the option to expand/collapse specific Simple XML element.) ... View more