Dashboards & Visualizations

generated view xml file differ from documentation

urirosenberg
New Member

Hi,
I created a view (consists of a report and a graph).
the resulting xml file is as follows:




testsave
events
10
true

<chart>
  <searchName>Messages by minute last 3 hours</searchName>
  <title>graph</title>
  <option name="charting.chart">column</option>
  <option name="count">10</option>
  <option name="displayRowNumbers">true</option>
</chart>



I am following your instructions for embedding a dashboard (http://docs.splunk.com/Documentation/Splunk/5.0.1/AdvancedDev/3rdParty).
the xml file is completely different: no modules or parameters...
I am trying to embed the dashboard alone (without the splunck headers).
How should I modify the xml?
Thanks!

Tags (2)
0 Karma

Ayn
Legend

Splunk has two "modes" of XML - simple and advanced XML. What you've pasted is simple XML, which is what is generated by default for simple forms and dashboards. For more advanced purposes you really want to use advanced XML. More information on that here: http://docs.splunk.com/Documentation/Splunk/5.0/AdvancedDev/AdvancedIntro

Simple XML is translated to advanced XML automatically by Splunk - to get the equivalent advanced XML code for your view, add ?showsource=1 to the end of the URL for your view.

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Data Management Digest – August 2026

MichelleCorpora_1-1788182384472.png Welcome to the August 2026 edition of Data Management Digest! August was a ...

Your Feedback. Our Roadmap. Visit the PX Feedback Booth at .conf26

You use Splunk every day, come and help shape what's next.  Save Your Seat: Product-Focused Sessions at ...

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...