Building Advanced Dashboards - Implementing Splunk: Big Data Reporting and Development for Operational Intelligence - page 207

• Modify the behavior of a downstream module
• Display an element on the dashboard
• Handle actions produced by clicks
It is also possible for a module to:
• Post process the events produced by a query
• Add custom JavaScript to the dashboard
Understanding layoutPanel
In an advanced XML dashboard, which panel a module is drawn to is determined
by the value of the layoutPanel attribute. This separation of logic and layout can
be useful—for instance, allowing you to reuse data generated by a query with
multiple modules—but displays the results on different parts of the page.
A few rules about this attribute are as follows:
• The layoutPanel attribute must appear on all immediate children of <view> .
• The layoutPanel attribute can appear on descendant child module tags.
• If a module does not have a layoutPanel attribute, it will inherit the value
from the closest upstream module that does.
• Modules that have visible output are added to their respective layoutPanel
attribute in the order they appear in the XML.
• Modules "low" in the panel they are placed. Most modules take the entire
width of the panel, but some do not, and flow left to right before wrapping.
Looking through our XML, we find these elements with the layoutPanel attribute
like this:
<module name="AccountBar" layoutPanel="appHeader"/>
<module name="AppBar" layoutPanel="navigationHeader"/>
<module name="Message" layoutPanel="messaging">
<module name="TitleBar" layoutPanel="viewHeader">
<module name="ExtendedFieldSearch" layoutPanel="viewHeader">
<module name="TimeRangePicker">
<module name="SubmitButton">
<module name="HiddenSearch" layoutPanel="panel_row1_col1">
...