<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: XML dashboard errors at startup in Dashboards &amp; Visualizations</title>
    <link>https://community.splunk.com/t5/Dashboards-Visualizations/XML-dashboard-errors-at-startup/m-p/23133#M841</link>
    <description>&lt;P&gt;I'd suspect that the unescaped &lt;CODE&gt;&amp;lt;&lt;/CODE&gt; and &lt;CODE&gt;&amp;gt;&lt;/CODE&gt; are causing the XML validator to complain. A quick fix would be to wrap the searchString in a CDATA block or individually XML escape the unsafe characters. Alternately, you could refer to a saved search by name, which might be considered cleaner.&lt;/P&gt;</description>
    <pubDate>Sat, 08 Jan 2011 11:45:36 GMT</pubDate>
    <dc:creator>Stephen_Sorkin</dc:creator>
    <dc:date>2011-01-08T11:45:36Z</dc:date>
    <item>
      <title>XML dashboard errors at startup</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/XML-dashboard-errors-at-startup/m-p/23132#M840</link>
      <description>&lt;P&gt;I can successfully run the following search from within Splunk:&lt;/P&gt;

&lt;P&gt;sourcetype=ossim "Event received" ((plugin_id&amp;gt;=1001 AND plugin_id&amp;lt;=1131) OR plugin_id=1597) | lookup ossim_plugins plugin_id OUTPUT plugin_name | timechart count by plugin_name&lt;/P&gt;

&lt;P&gt;I've tried to insert this search into a dashboard as follows:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;  &amp;lt;chart&amp;gt;
    &amp;lt;title&amp;gt;IDS Events by Plugin (60 Minutes)&amp;lt;/title&amp;gt;
    &amp;lt;searchString&amp;gt;sourcetype=ossim "Event received" ((plugin_id&amp;gt;=1001 AND plugin_id&amp;lt;=1131) OR plugin_id=1597) | lookup ossim_plugins plugin_id OUTPUT plugin_name | timechart count by plugin_name&amp;lt;/searchString&amp;gt;
    &amp;lt;earliestTime&amp;gt;-1h&amp;lt;/earliestTime&amp;gt;
    &amp;lt;option name="charting.chart"&amp;gt;area&amp;lt;/option&amp;gt;
    &amp;lt;option name="charting.legend.placement"&amp;gt;right&amp;lt;/option&amp;gt;
    &amp;lt;option name="charting.chart.stackMode"&amp;gt;stacked&amp;lt;/option&amp;gt;
    &amp;lt;option name="charting.chart.nullValueMode"&amp;gt;connect&amp;lt;/option&amp;gt;        
  &amp;lt;/chart&amp;gt;
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;When I restart Splunk, I see the following message from the console:&lt;/P&gt;

&lt;P&gt;Error while parsing &lt;EM&gt;path to file&lt;/EM&gt; not well-formed (invalid token): line 6, column 88&lt;/P&gt;

&lt;P&gt;What am I doing wrong here?&lt;/P&gt;

&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Sat, 08 Jan 2011 07:48:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/XML-dashboard-errors-at-startup/m-p/23132#M840</guid>
      <dc:creator>jambajuice</dc:creator>
      <dc:date>2011-01-08T07:48:17Z</dc:date>
    </item>
    <item>
      <title>Re: XML dashboard errors at startup</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/XML-dashboard-errors-at-startup/m-p/23133#M841</link>
      <description>&lt;P&gt;I'd suspect that the unescaped &lt;CODE&gt;&amp;lt;&lt;/CODE&gt; and &lt;CODE&gt;&amp;gt;&lt;/CODE&gt; are causing the XML validator to complain. A quick fix would be to wrap the searchString in a CDATA block or individually XML escape the unsafe characters. Alternately, you could refer to a saved search by name, which might be considered cleaner.&lt;/P&gt;</description>
      <pubDate>Sat, 08 Jan 2011 11:45:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/XML-dashboard-errors-at-startup/m-p/23133#M841</guid>
      <dc:creator>Stephen_Sorkin</dc:creator>
      <dc:date>2011-01-08T11:45:36Z</dc:date>
    </item>
  </channel>
</rss>

