<?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: Is there a way to run search inspector from command line? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Is-there-a-way-to-run-search-inspector-from-command-line/m-p/42130#M7827</link>
    <description>&lt;PRE&gt;&lt;CODE&gt;./splunk show jobs &amp;lt;id&amp;gt;
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Also, when you spawn your search job, you could specify the search id to use via the &lt;CODE&gt;-id&lt;/CODE&gt; option.  However, you will have to make sure there are no name collisions.  &lt;/P&gt;

&lt;P&gt;In addition, if you spawn your job with &lt;CODE&gt;-detach 1&lt;/CODE&gt;, the CLI will output the search id of the job (but not emit the results, just like if you start a background process in the shell).&lt;/P&gt;</description>
    <pubDate>Fri, 11 Feb 2011 02:46:14 GMT</pubDate>
    <dc:creator>steveyz</dc:creator>
    <dc:date>2011-02-11T02:46:14Z</dc:date>
    <item>
      <title>Is there a way to run search inspector from command line?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Is-there-a-way-to-run-search-inspector-from-command-line/m-p/42129#M7826</link>
      <description>&lt;P&gt;I am finding that some scripts I use to automate searches are experiencing data fallout due to timeouts AND not reporting this fact (no errors messages nor error codes).  So I would like to add the following capability to the script:
Capture the job ID for my search in Splunk (I am sure I can figure out how to do this).
Once the search completes, launch the job inspector on my search to check if I have any timeouts or other errors before I report my results.&lt;/P&gt;

&lt;P&gt;Can this be done?&lt;/P&gt;</description>
      <pubDate>Thu, 10 Feb 2011 22:48:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Is-there-a-way-to-run-search-inspector-from-command-line/m-p/42129#M7826</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2011-02-10T22:48:14Z</dc:date>
    </item>
    <item>
      <title>Re: Is there a way to run search inspector from command line?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Is-there-a-way-to-run-search-inspector-from-command-line/m-p/42130#M7827</link>
      <description>&lt;PRE&gt;&lt;CODE&gt;./splunk show jobs &amp;lt;id&amp;gt;
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Also, when you spawn your search job, you could specify the search id to use via the &lt;CODE&gt;-id&lt;/CODE&gt; option.  However, you will have to make sure there are no name collisions.  &lt;/P&gt;

&lt;P&gt;In addition, if you spawn your job with &lt;CODE&gt;-detach 1&lt;/CODE&gt;, the CLI will output the search id of the job (but not emit the results, just like if you start a background process in the shell).&lt;/P&gt;</description>
      <pubDate>Fri, 11 Feb 2011 02:46:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Is-there-a-way-to-run-search-inspector-from-command-line/m-p/42130#M7827</guid>
      <dc:creator>steveyz</dc:creator>
      <dc:date>2011-02-11T02:46:14Z</dc:date>
    </item>
  </channel>
</rss>

