<?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: Creating a report that progressively narrows the data set in Dashboards &amp; Visualizations</title>
    <link>https://community.splunk.com/t5/Dashboards-Visualizations/Creating-a-report-that-progressively-narrows-the-data-set/m-p/18640#M628</link>
    <description>&lt;P&gt;I had something a little different in mind - one Advanced XML view with a tree of pulldowns. A bit like the SideviewUtils doc on "Pulldown - reusing searches with 'postProcess'", available under Key Techniques if you have Sideview Utils v2 (get it from &lt;A href="http://sideviewapps.com/apps/sideview-utils/"&gt;http://sideviewapps.com/apps/sideview-utils/&lt;/A&gt; - you really should!).&lt;/P&gt;</description>
    <pubDate>Wed, 31 Jul 2013 13:19:00 GMT</pubDate>
    <dc:creator>martin_mueller</dc:creator>
    <dc:date>2013-07-31T13:19:00Z</dc:date>
    <item>
      <title>Creating a report that progressively narrows the data set</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/Creating-a-report-that-progressively-narrows-the-data-set/m-p/18637#M625</link>
      <description>&lt;P&gt;Imagine that we are sending data that has the following fields in every event&lt;BR /&gt;
time, userid, thread ... &lt;/P&gt;

&lt;P&gt;Would like to create a forms where the on call engineer can &lt;/P&gt;

&lt;OL&gt;
&lt;LI&gt;Start by selecting a time range&lt;/LI&gt;
&lt;LI&gt;He/she is now able to view all the user ids in that time range in a drop down&lt;/LI&gt;
&lt;LI&gt;Now the engineer can select a user. On doing that the engineer is able to view the list of all the thread ids that this user has made requests in the given time period (again a dropdown) &lt;/LI&gt;
&lt;LI&gt;And so on...&lt;/LI&gt;
&lt;/OL&gt;

&lt;P&gt;To finally arrive at a small subset of logs that he/she should inspect. Is this doable? Could you point me to a sample?&lt;/P&gt;</description>
      <pubDate>Tue, 30 Jul 2013 15:37:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/Creating-a-report-that-progressively-narrows-the-data-set/m-p/18637#M625</guid>
      <dc:creator>amanteja</dc:creator>
      <dc:date>2013-07-30T15:37:48Z</dc:date>
    </item>
    <item>
      <title>Re: Creating a report that progressively narrows the data set</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/Creating-a-report-that-progressively-narrows-the-data-set/m-p/18638#M626</link>
      <description>&lt;P&gt;That's doable.&lt;/P&gt;

&lt;P&gt;In short, this could be an approach:&lt;/P&gt;

&lt;OL&gt;
&lt;LI&gt;time range picker&lt;/LI&gt;
&lt;LI&gt;feed time range into a search for user ids, populating a pulldown&lt;/LI&gt;
&lt;LI&gt;feed time range and user id into a search for thread ids, populating a pulldown&lt;/LI&gt;
&lt;LI&gt;and so on&lt;/LI&gt;
&lt;LI&gt;feed all params to the final search, yielding your desired events&lt;/LI&gt;
&lt;/OL&gt;

&lt;P&gt;Depending on your data, it's probably smart to have commonly used fields filled from prepared lookups to speed things up.&lt;/P&gt;</description>
      <pubDate>Wed, 31 Jul 2013 12:53:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/Creating-a-report-that-progressively-narrows-the-data-set/m-p/18638#M626</guid>
      <dc:creator>martin_mueller</dc:creator>
      <dc:date>2013-07-31T12:53:08Z</dc:date>
    </item>
    <item>
      <title>Re: Creating a report that progressively narrows the data set</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/Creating-a-report-that-progressively-narrows-the-data-set/m-p/18639#M627</link>
      <description>&lt;P&gt;Thanks. &lt;BR /&gt;
In the second form-  as soon as the user has picked a userid (prepopulated by query) how does one transition to the next form WITHOUT showing the results to the user and having him click on that as documented here &lt;A href="http://docs.splunk.com/Documentation/Splunk/5.0.3/Viz/Dynamicdrilldownindashboardsandforms#Dynamic_drilldown_examples"&gt;http://docs.splunk.com/Documentation/Splunk/5.0.3/Viz/Dynamicdrilldownindashboardsandforms#Dynamic_drilldown_examples&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 31 Jul 2013 13:10:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/Creating-a-report-that-progressively-narrows-the-data-set/m-p/18639#M627</guid>
      <dc:creator>amanteja</dc:creator>
      <dc:date>2013-07-31T13:10:06Z</dc:date>
    </item>
    <item>
      <title>Re: Creating a report that progressively narrows the data set</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/Creating-a-report-that-progressively-narrows-the-data-set/m-p/18640#M628</link>
      <description>&lt;P&gt;I had something a little different in mind - one Advanced XML view with a tree of pulldowns. A bit like the SideviewUtils doc on "Pulldown - reusing searches with 'postProcess'", available under Key Techniques if you have Sideview Utils v2 (get it from &lt;A href="http://sideviewapps.com/apps/sideview-utils/"&gt;http://sideviewapps.com/apps/sideview-utils/&lt;/A&gt; - you really should!).&lt;/P&gt;</description>
      <pubDate>Wed, 31 Jul 2013 13:19:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/Creating-a-report-that-progressively-narrows-the-data-set/m-p/18640#M628</guid>
      <dc:creator>martin_mueller</dc:creator>
      <dc:date>2013-07-31T13:19:00Z</dc:date>
    </item>
  </channel>
</rss>

