<?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: How to create multiple radial gauges from a singel query? in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/How-to-create-multiple-radial-gauges-from-a-singel-query/m-p/165172#M186069</link>
    <description>&lt;P&gt;Hi v920998,&lt;/P&gt;

&lt;P&gt;you can use &lt;CODE&gt;PostProcess&lt;/CODE&gt; for this in your dashboard, build a base search to provide a set of base events and use this set in &lt;CODE&gt;PostProcess&lt;/CODE&gt;.&lt;/P&gt;

&lt;P&gt;Here is a perfect Example for this: &lt;A href="http://docs.splunk.com/Documentation/Splunk/6.0/AdvancedDev/PostProcess"&gt;Use one search for a whole dashboard&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Most important for this is that your base search facilitates either a summary indexing command like: &lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;sistats&lt;/LI&gt;
&lt;LI&gt;sitimechart&lt;/LI&gt;
&lt;LI&gt;sitop&lt;/LI&gt;
&lt;LI&gt;sichart&lt;/LI&gt;
&lt;LI&gt;sirare&lt;/LI&gt;
&lt;/UL&gt;

&lt;P&gt;or you use primary reporting commands, such as &lt;CODE&gt;stat&lt;/CODE&gt;, &lt;CODE&gt;timechart&lt;/CODE&gt;, &lt;CODE&gt;top&lt;/CODE&gt;, &lt;CODE&gt;chart&lt;/CODE&gt;, and &lt;CODE&gt;rare&lt;/CODE&gt;. &lt;/P&gt;

&lt;P&gt;hope this helps ...&lt;/P&gt;

&lt;P&gt;cheers, MuS&lt;/P&gt;</description>
    <pubDate>Wed, 04 Dec 2013 07:22:42 GMT</pubDate>
    <dc:creator>MuS</dc:creator>
    <dc:date>2013-12-04T07:22:42Z</dc:date>
    <item>
      <title>How to create multiple radial gauges from a singel query?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-create-multiple-radial-gauges-from-a-singel-query/m-p/165171#M186068</link>
      <description>&lt;P&gt;I have a query that produces 4 field values. I am looking for a way to use thae gauge command to create multiple gauges, one for each result field of the query?&lt;/P&gt;</description>
      <pubDate>Wed, 04 Dec 2013 04:33:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-create-multiple-radial-gauges-from-a-singel-query/m-p/165171#M186068</guid>
      <dc:creator>v920998</dc:creator>
      <dc:date>2013-12-04T04:33:26Z</dc:date>
    </item>
    <item>
      <title>Re: How to create multiple radial gauges from a singel query?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-create-multiple-radial-gauges-from-a-singel-query/m-p/165172#M186069</link>
      <description>&lt;P&gt;Hi v920998,&lt;/P&gt;

&lt;P&gt;you can use &lt;CODE&gt;PostProcess&lt;/CODE&gt; for this in your dashboard, build a base search to provide a set of base events and use this set in &lt;CODE&gt;PostProcess&lt;/CODE&gt;.&lt;/P&gt;

&lt;P&gt;Here is a perfect Example for this: &lt;A href="http://docs.splunk.com/Documentation/Splunk/6.0/AdvancedDev/PostProcess"&gt;Use one search for a whole dashboard&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Most important for this is that your base search facilitates either a summary indexing command like: &lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;sistats&lt;/LI&gt;
&lt;LI&gt;sitimechart&lt;/LI&gt;
&lt;LI&gt;sitop&lt;/LI&gt;
&lt;LI&gt;sichart&lt;/LI&gt;
&lt;LI&gt;sirare&lt;/LI&gt;
&lt;/UL&gt;

&lt;P&gt;or you use primary reporting commands, such as &lt;CODE&gt;stat&lt;/CODE&gt;, &lt;CODE&gt;timechart&lt;/CODE&gt;, &lt;CODE&gt;top&lt;/CODE&gt;, &lt;CODE&gt;chart&lt;/CODE&gt;, and &lt;CODE&gt;rare&lt;/CODE&gt;. &lt;/P&gt;

&lt;P&gt;hope this helps ...&lt;/P&gt;

&lt;P&gt;cheers, MuS&lt;/P&gt;</description>
      <pubDate>Wed, 04 Dec 2013 07:22:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-create-multiple-radial-gauges-from-a-singel-query/m-p/165172#M186069</guid>
      <dc:creator>MuS</dc:creator>
      <dc:date>2013-12-04T07:22:42Z</dc:date>
    </item>
  </channel>
</rss>

