<?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 Can somebody from Splunk please explain the changes to GUI search logging in Monitoring Splunk</title>
    <link>https://community.splunk.com/t5/Monitoring-Splunk/Can-somebody-from-Splunk-please-explain-the-changes-to-GUI/m-p/67799#M771</link>
    <description>&lt;P&gt;Prior to the 5.x (and possibly earlier), Splunk logged user searches from the GUI in a human readable format.  The event had the user name and something like search="search bla bla bla | stats count by bla...".  It was easy to read and audit.&lt;/P&gt;

&lt;P&gt;Now when I look in the _internal index for searches that I or other users have run, all the searches are URL encoded.  They are way more difficult to read and audit.  &lt;/P&gt;

&lt;P&gt;Why would you guys elect to make those logging events less human readable and what is the best method to advocate for changing the logging format back to something I can read?&lt;/P&gt;

&lt;P&gt;Thx.&lt;/P&gt;

&lt;P&gt;C&lt;/P&gt;</description>
    <pubDate>Tue, 18 Jun 2013 21:16:46 GMT</pubDate>
    <dc:creator>responsys_cm</dc:creator>
    <dc:date>2013-06-18T21:16:46Z</dc:date>
    <item>
      <title>Can somebody from Splunk please explain the changes to GUI search logging</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Can-somebody-from-Splunk-please-explain-the-changes-to-GUI/m-p/67799#M771</link>
      <description>&lt;P&gt;Prior to the 5.x (and possibly earlier), Splunk logged user searches from the GUI in a human readable format.  The event had the user name and something like search="search bla bla bla | stats count by bla...".  It was easy to read and audit.&lt;/P&gt;

&lt;P&gt;Now when I look in the _internal index for searches that I or other users have run, all the searches are URL encoded.  They are way more difficult to read and audit.  &lt;/P&gt;

&lt;P&gt;Why would you guys elect to make those logging events less human readable and what is the best method to advocate for changing the logging format back to something I can read?&lt;/P&gt;

&lt;P&gt;Thx.&lt;/P&gt;

&lt;P&gt;C&lt;/P&gt;</description>
      <pubDate>Tue, 18 Jun 2013 21:16:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Can-somebody-from-Splunk-please-explain-the-changes-to-GUI/m-p/67799#M771</guid>
      <dc:creator>responsys_cm</dc:creator>
      <dc:date>2013-06-18T21:16:46Z</dc:date>
    </item>
    <item>
      <title>Re: Can somebody from Splunk please explain the changes to GUI search logging</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Can-somebody-from-Splunk-please-explain-the-changes-to-GUI/m-p/67800#M772</link>
      <description>&lt;P&gt;I'm pretty sure you are referencing &lt;CODE&gt;$SPLUNK_HOME/var/log/splunk/searches.log&lt;/CODE&gt;, which was indeed retired in 5.0 because the same level of information (and then some) is available from audit.log and in the _audit index.&lt;/P&gt;

&lt;P&gt;The good news is it's pretty easy to gain access to the same level of information by searching the _audit index:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=_audit search=*
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;If you want to make it fancier and show more information such as the start and end time range of the search, you can use this search:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=_audit search=*
| eval earliest_time=if(like(apiStartTime,"%ZERO_TIME%"),"epoch",apiStartTime)
| eval latest_time=if(like(apiEndTime,"%ZERO_TIME%"),"now",apiEndTime)
| table _time user earliest_time latest_time search search_id
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Wed, 26 Jun 2013 18:23:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Can-somebody-from-Splunk-please-explain-the-changes-to-GUI/m-p/67800#M772</guid>
      <dc:creator>hexx</dc:creator>
      <dc:date>2013-06-26T18:23:20Z</dc:date>
    </item>
  </channel>
</rss>

