<?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 REST API search issue in Postman in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/REST-API-search-issue-in-Postman/m-p/426941#M74810</link>
    <description>&lt;P&gt;I have the Authorization figured working, but every time I run a search, I get the following error:&lt;BR /&gt;
(NOTE the AAA/BBB/nnn stuff is just to mask actual values in this post)&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;&amp;lt;messages&amp;gt;
        &amp;lt;msg type="DEBUG"&amp;gt;Configuration initialization for /var/splunkhot/splunk/etc took 112ms when dispatching a search (search ID: 1556216662.24755_33CF52FC-F282-491A-875E-F8EC1EB01F4C)&amp;lt;/msg&amp;gt;
        &amp;lt;msg type="DEBUG"&amp;gt;Invalid eval expression for 'EVAL-url_length' in stanza [pan:threat]: The expression is malformed. Expected LIKE.&amp;lt;/msg&amp;gt;
        &amp;lt;msg type="DEBUG"&amp;gt;base lispy: [ AND host::AAAAAAA source::/app/jboss/BBBBBB/log/server.log ]&amp;lt;/msg&amp;gt;
        &amp;lt;msg type="DEBUG"&amp;gt;search context: user="nnnnnnn", app="search", bs-pathname="/var/splunkhot/splunk/etc"&amp;lt;/msg&amp;gt;
    &amp;lt;/messages&amp;gt;
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;The actual search I have in the body of the POST is:&lt;BR /&gt;&lt;BR /&gt;
 &lt;CODE&gt;search=search+host%3DAAAAAAA+source%3D%2Fapp%2Fjboss%2BBBBBB%2Flog%2Fserver.log+%7C+search+ERROR+earliest%3D-4h&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;I've even done just a SIMPLE search:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;search=search+host%3DAAAAAAA
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;and I STILL get an error.&lt;/P&gt;

&lt;P&gt;Any ideas what the issue is??&lt;/P&gt;</description>
    <pubDate>Thu, 25 Apr 2019 18:40:55 GMT</pubDate>
    <dc:creator>gartnerj</dc:creator>
    <dc:date>2019-04-25T18:40:55Z</dc:date>
    <item>
      <title>REST API search issue in Postman</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/REST-API-search-issue-in-Postman/m-p/426941#M74810</link>
      <description>&lt;P&gt;I have the Authorization figured working, but every time I run a search, I get the following error:&lt;BR /&gt;
(NOTE the AAA/BBB/nnn stuff is just to mask actual values in this post)&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;&amp;lt;messages&amp;gt;
        &amp;lt;msg type="DEBUG"&amp;gt;Configuration initialization for /var/splunkhot/splunk/etc took 112ms when dispatching a search (search ID: 1556216662.24755_33CF52FC-F282-491A-875E-F8EC1EB01F4C)&amp;lt;/msg&amp;gt;
        &amp;lt;msg type="DEBUG"&amp;gt;Invalid eval expression for 'EVAL-url_length' in stanza [pan:threat]: The expression is malformed. Expected LIKE.&amp;lt;/msg&amp;gt;
        &amp;lt;msg type="DEBUG"&amp;gt;base lispy: [ AND host::AAAAAAA source::/app/jboss/BBBBBB/log/server.log ]&amp;lt;/msg&amp;gt;
        &amp;lt;msg type="DEBUG"&amp;gt;search context: user="nnnnnnn", app="search", bs-pathname="/var/splunkhot/splunk/etc"&amp;lt;/msg&amp;gt;
    &amp;lt;/messages&amp;gt;
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;The actual search I have in the body of the POST is:&lt;BR /&gt;&lt;BR /&gt;
 &lt;CODE&gt;search=search+host%3DAAAAAAA+source%3D%2Fapp%2Fjboss%2BBBBBB%2Flog%2Fserver.log+%7C+search+ERROR+earliest%3D-4h&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;I've even done just a SIMPLE search:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;search=search+host%3DAAAAAAA
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;and I STILL get an error.&lt;/P&gt;

&lt;P&gt;Any ideas what the issue is??&lt;/P&gt;</description>
      <pubDate>Thu, 25 Apr 2019 18:40:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/REST-API-search-issue-in-Postman/m-p/426941#M74810</guid>
      <dc:creator>gartnerj</dc:creator>
      <dc:date>2019-04-25T18:40:55Z</dc:date>
    </item>
  </channel>
</rss>

