<?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: Issue with Postprocessing in Dashboards &amp; Visualizations</title>
    <link>https://community.splunk.com/t5/Dashboards-Visualizations/Issue-with-Postprocessing/m-p/95009#M5186</link>
    <description>&lt;P&gt;Yep.  Sideview Utils fills a lot of gaps like this.  In this particular case it has PostProcess module to replace HiddenPostProcess.   Not only can you do $foo$ substitution into PostProcess searches, but you don't have to think about intentions at all ever again -- the substitution is right from the raw tokens into the $foo$.  No intention middleman.   Also the Pulldown and TextField modules are much easier to use than the core equivalents.  remember to get the latest version (2.2.2) from the Sideview site.  The version on Splunkbase is actually quite old.&lt;/P&gt;</description>
    <pubDate>Thu, 18 Oct 2012 20:59:30 GMT</pubDate>
    <dc:creator>sideview</dc:creator>
    <dc:date>2012-10-18T20:59:30Z</dc:date>
    <item>
      <title>Issue with Postprocessing</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/Issue-with-Postprocessing/m-p/95007#M5184</link>
      <description>&lt;P&gt;Hello&lt;/P&gt;

&lt;P&gt;I am trying to use postprocessing and having issues with it. Can anyone please help me out in understanding where am I going wrong here.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;&amp;lt;?xml version='1.0' encoding='utf-8'?&amp;gt;
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;FORM&gt;
  &lt;LABEL&gt;Service Operation - Outages and Notification Dashboard&lt;/LABEL&gt;
  &lt;SEARCHTEMPLATE&gt;
    sourcetype="incident" record.groupDepartment="*" record.groupArea="*"  record.assignmentGroup="*"| dedup record.incidentId|timechart span=1hr count by record.eventType usenull=f | addtotals create , update | fields - create , update 
  &lt;/SEARCHTEMPLATE&gt;  
  &lt;FIELDSET autorun="false"&gt;
    &lt;INPUT type="dropdown" token="Dept" /&gt;
      &lt;LABEL&gt;Department: &lt;/LABEL&gt;
      &lt;DEFAULT&gt;*&lt;/DEFAULT&gt;
      &lt;CHOICE value="*"&gt;All&lt;/CHOICE&gt;
      &lt;CHOICE value="Systems"&gt;Systems&lt;/CHOICE&gt;
      &lt;CHOICE value="Agency"&gt;Agency&lt;/CHOICE&gt;
    
    &lt;INPUT type="dropdown" token="Area" /&gt;
      &lt;LABEL&gt;Area: &lt;/LABEL&gt;
      &lt;DEFAULT&gt;*&lt;/DEFAULT&gt;
      &lt;CHOICE value="*"&gt;All&lt;/CHOICE&gt;
      &lt;CHOICE value="Architecture and Engineering"&gt;Architecture and Engineering&lt;/CHOICE&gt;
      &lt;CHOICE value="Systems Technology"&gt;Systems Technology&lt;/CHOICE&gt;
      &lt;CHOICE value="Product Solutions"&gt;Product Solutions&lt;/CHOICE&gt;
      &lt;CHOICE value="Systems Projects"&gt;Systems Projects&lt;/CHOICE&gt;
      &lt;CHOICE value="Customer Connection Solutions"&gt;Customer Connection Solutions&lt;/CHOICE&gt;
      &lt;CHOICE value="Channel Support"&gt;Channel Support&lt;/CHOICE&gt;
      &lt;CHOICE value="General and Financial Services"&gt;General and Financial Services&lt;/CHOICE&gt;
      &lt;CHOICE value="Data &amp;amp; Information Strategies"&gt;Data  and amp; Information Strategies&lt;/CHOICE&gt;
      &lt;CHOICE value="P&amp;amp;C Claims Systems"&gt;P and amp;C Claims Systems&lt;/CHOICE&gt;
      &lt;CHOICE value="Customer Relationship Management"&gt;Customer Relationship Management&lt;/CHOICE&gt;
      &lt;CHOICE value="Not Defined"&gt;Not Defined&lt;/CHOICE&gt;
      &lt;CHOICE value="Product Solutions"&gt;Product Solutions&lt;/CHOICE&gt;
    
    &lt;INPUT type="text" token="WG" /&gt;
      &lt;LABEL&gt;WorkGroup: &lt;/LABEL&gt;
      &lt;DEFAULT&gt;*&lt;/DEFAULT&gt;
    
   &lt;/FIELDSET&gt;
  &lt;ROW&gt;
    &lt;CHART&gt;
      &lt;TITLE&gt;24 Hour History&lt;/TITLE&gt;
      &lt;SEARCHPOSTPROCESS&gt;earliest=-24h@h latest=@h | search record.groupDepartment="$Dept$" record.groupArea="$Area$"  record.assignmentGroup="$WG$" &lt;/SEARCHPOSTPROCESS&gt;
      Time
      column
      gaps
      stacked
      false
      right
      
      20
      true
      all
      &lt;/CHART&gt;
  &lt;/ROW&gt;
  &lt;ROW&gt;
    &lt;CHART&gt;
      &lt;TITLE&gt;31 day History&lt;/TITLE&gt;
      &lt;SEARCHPOSTPROCESS&gt;earliest=-31d@d latest=@d | search record.groupDepartment="$Dept$" record.groupArea="$Area$" record.assignmentGroup="$WG$"&lt;/SEARCHPOSTPROCESS&gt;
      Time
      column
      stacked
      
      10
      true
    &lt;/CHART&gt;
  &lt;/ROW&gt;
&lt;/FORM&gt;

&lt;P&gt;Regards&lt;/P&gt;

&lt;P&gt;theou&lt;/P&gt;</description>
      <pubDate>Thu, 18 Oct 2012 15:59:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/Issue-with-Postprocessing/m-p/95007#M5184</guid>
      <dc:creator>theouhuios</dc:creator>
      <dc:date>2012-10-18T15:59:28Z</dc:date>
    </item>
    <item>
      <title>Re: Issue with Postprocessing</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/Issue-with-Postprocessing/m-p/95008#M5185</link>
      <description>&lt;P&gt;You cant use values generated from selectors / intentions in post process.&lt;/P&gt;

&lt;P&gt;Its a limitation, and the bane of my life.&lt;/P&gt;

&lt;P&gt;sideview utils works around this - its a cool app.&lt;/P&gt;</description>
      <pubDate>Thu, 18 Oct 2012 19:58:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/Issue-with-Postprocessing/m-p/95008#M5185</guid>
      <dc:creator>jonuwz</dc:creator>
      <dc:date>2012-10-18T19:58:38Z</dc:date>
    </item>
    <item>
      <title>Re: Issue with Postprocessing</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/Issue-with-Postprocessing/m-p/95009#M5186</link>
      <description>&lt;P&gt;Yep.  Sideview Utils fills a lot of gaps like this.  In this particular case it has PostProcess module to replace HiddenPostProcess.   Not only can you do $foo$ substitution into PostProcess searches, but you don't have to think about intentions at all ever again -- the substitution is right from the raw tokens into the $foo$.  No intention middleman.   Also the Pulldown and TextField modules are much easier to use than the core equivalents.  remember to get the latest version (2.2.2) from the Sideview site.  The version on Splunkbase is actually quite old.&lt;/P&gt;</description>
      <pubDate>Thu, 18 Oct 2012 20:59:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/Issue-with-Postprocessing/m-p/95009#M5186</guid>
      <dc:creator>sideview</dc:creator>
      <dc:date>2012-10-18T20:59:30Z</dc:date>
    </item>
  </channel>
</rss>

