<?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 Splunk command to find out configuration errors or typos? in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Is-there-a-Splunk-command-to-find-out-configuration-errors-or/m-p/330088#M98260</link>
    <description>&lt;P&gt;btool just outputs to standardout, so you see its output immediately on the commandline after entering that command.&lt;/P&gt;

&lt;P&gt;For more convenient viewing, you can redirect the output to a file, or pipe it to a viewer like &lt;CODE&gt;less&lt;/CODE&gt; or &lt;CODE&gt;more&lt;/CODE&gt; the usual way.&lt;/P&gt;</description>
    <pubDate>Mon, 17 Dec 2018 10:19:53 GMT</pubDate>
    <dc:creator>FrankVl</dc:creator>
    <dc:date>2018-12-17T10:19:53Z</dc:date>
    <item>
      <title>Is there a Splunk command to find out configuration errors or typos?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Is-there-a-Splunk-command-to-find-out-configuration-errors-or/m-p/330081#M98253</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I was wondering is there a Splunk command to find out configuration errors? For example, LINE_BrEAKER  in props has a typo. So is there anyway we could find out  these types of errors?&lt;/P&gt;</description>
      <pubDate>Mon, 27 Feb 2017 19:52:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Is-there-a-Splunk-command-to-find-out-configuration-errors-or/m-p/330081#M98253</guid>
      <dc:creator>kteng2024</dc:creator>
      <dc:date>2017-02-27T19:52:04Z</dc:date>
    </item>
    <item>
      <title>Re: Is there a Splunk command to find out configuration errors or typos?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Is-there-a-Splunk-command-to-find-out-configuration-errors-or/m-p/330082#M98254</link>
      <description>&lt;P&gt;use &lt;CODE&gt;btool&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;In a terminal on the Splunk server, use the command&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;$ SPLUNK_HOME/bin/splunk btool check&lt;/CODE&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 27 Feb 2017 19:55:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Is-there-a-Splunk-command-to-find-out-configuration-errors-or/m-p/330082#M98254</guid>
      <dc:creator>rjthibod</dc:creator>
      <dc:date>2017-02-27T19:55:45Z</dc:date>
    </item>
    <item>
      <title>Re: Is there a Splunk command to find out configuration errors or typos?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Is-there-a-Splunk-command-to-find-out-configuration-errors-or/m-p/330083#M98255</link>
      <description>&lt;P&gt;Other useful variants are&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;$SPLUNK_HOME/bin/splunk btool validate-strptime
$SPLUNK_HOME/bin/splunk btool validate-regex
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Just run $SPLUNK_HOME/bin/splunk btool to see full syntax and options.&lt;/P&gt;</description>
      <pubDate>Mon, 27 Feb 2017 20:03:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Is-there-a-Splunk-command-to-find-out-configuration-errors-or/m-p/330083#M98255</guid>
      <dc:creator>somesoni2</dc:creator>
      <dc:date>2017-02-27T20:03:21Z</dc:date>
    </item>
    <item>
      <title>Re: Is there a Splunk command to find out configuration errors or typos?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Is-there-a-Splunk-command-to-find-out-configuration-errors-or/m-p/330084#M98256</link>
      <description>&lt;P&gt;See also &lt;A href="http://docs.splunk.com/Documentation/Splunk/6.5.2/Troubleshooting/Usebtooltotroubleshootconfigurations"&gt;Use btool to troubleshoot configurations&lt;/A&gt; in the Splunk Enterprise &lt;EM&gt;Troubleshooting Manual&lt;/EM&gt;.&lt;/P&gt;</description>
      <pubDate>Mon, 27 Feb 2017 21:06:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Is-there-a-Splunk-command-to-find-out-configuration-errors-or/m-p/330084#M98256</guid>
      <dc:creator>ChrisG</dc:creator>
      <dc:date>2017-02-27T21:06:52Z</dc:date>
    </item>
    <item>
      <title>Re: Is there a Splunk command to find out configuration errors or typos?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Is-there-a-Splunk-command-to-find-out-configuration-errors-or/m-p/330085#M98257</link>
      <description>&lt;P&gt;@kteng2024 - Did the answer provided by rjthibod help provide a working solution to your question? If yes, please don't forget to resolve this post by clicking "Accept" and upvote any helpful comments. If no, please leave a comment with more feedback. Thank you.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Apr 2017 04:49:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Is-there-a-Splunk-command-to-find-out-configuration-errors-or/m-p/330085#M98257</guid>
      <dc:creator>aaraneta_splunk</dc:creator>
      <dc:date>2017-04-21T04:49:55Z</dc:date>
    </item>
    <item>
      <title>Re: Is there a Splunk command to find out configuration errors or typos?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Is-there-a-Splunk-command-to-find-out-configuration-errors-or/m-p/330086#M98258</link>
      <description>&lt;P&gt;Where do i might see the log files for BTOOL?&lt;/P&gt;</description>
      <pubDate>Mon, 17 Dec 2018 09:55:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Is-there-a-Splunk-command-to-find-out-configuration-errors-or/m-p/330086#M98258</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2018-12-17T09:55:15Z</dc:date>
    </item>
    <item>
      <title>Re: Is there a Splunk command to find out configuration errors or typos?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Is-there-a-Splunk-command-to-find-out-configuration-errors-or/m-p/330087#M98259</link>
      <description>&lt;P&gt;I found out that for checking the log fil i used &amp;gt; file.txt&lt;/P&gt;</description>
      <pubDate>Mon, 17 Dec 2018 10:01:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Is-there-a-Splunk-command-to-find-out-configuration-errors-or/m-p/330087#M98259</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2018-12-17T10:01:55Z</dc:date>
    </item>
    <item>
      <title>Re: Is there a Splunk command to find out configuration errors or typos?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Is-there-a-Splunk-command-to-find-out-configuration-errors-or/m-p/330088#M98260</link>
      <description>&lt;P&gt;btool just outputs to standardout, so you see its output immediately on the commandline after entering that command.&lt;/P&gt;

&lt;P&gt;For more convenient viewing, you can redirect the output to a file, or pipe it to a viewer like &lt;CODE&gt;less&lt;/CODE&gt; or &lt;CODE&gt;more&lt;/CODE&gt; the usual way.&lt;/P&gt;</description>
      <pubDate>Mon, 17 Dec 2018 10:19:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Is-there-a-Splunk-command-to-find-out-configuration-errors-or/m-p/330088#M98260</guid>
      <dc:creator>FrankVl</dc:creator>
      <dc:date>2018-12-17T10:19:53Z</dc:date>
    </item>
  </channel>
</rss>

