<?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 ES Investigation REST API Error in Splunk Enterprise Security</title>
    <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/ES-Investigation-REST-API-Error/m-p/559289#M10058</link>
    <description>&lt;P&gt;Greetings Splunkers,&lt;/P&gt;&lt;P&gt;I have a dashboard that "broke" over the weekend. When I run any of the dashboard searches I see errors of:&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Unexpected status for to fetch REST endpoint uri=&lt;A href="https://127.0.0.1:8089/services/storage/investigation/investigation?count=0&amp;amp;all=true&amp;amp;earliest=-700d&amp;amp;latest=-2d&amp;amp;output_mode=xml" target="_blank" rel="noopener"&gt;https://127.0.0.1:8089/services/storage/investigation/investigation?count=0&amp;amp;all=true&amp;amp;earliest=-700d&amp;amp;latest=-2d&amp;amp;output_mode=xml from server=&lt;/A&gt;&lt;A href="https://127.0.0.1:8089" target="_blank" rel="noopener"&gt;https://127.0.0.1:8089 - Bad Request&lt;/A&gt;&lt;/LI&gt;&lt;LI&gt;Failed to fetch REST endpoint uri=&lt;A href="https://127.0.0.1:8089/services/storage/investigation/investigation?count=0&amp;amp;all=true&amp;amp;earliest=-700d&amp;amp;latest=-2d&amp;amp;output_mode=xml" target="_blank" rel="noopener"&gt;https://127.0.0.1:8089/services/storage/investigation/investigation?count=0&amp;amp;all=true&amp;amp;earliest=-700d&amp;amp;latest=-2d&amp;amp;output_mode=xml from server &lt;/A&gt;&lt;A href="https://127.0.0.1:8089" target="_blank" rel="noopener"&gt;https://127.0.0.1:8089. Check that the URI path provided exists in the REST API. &lt;/A&gt;&lt;A href="https://splunk-es/en-US/help?location=message.rest.reference.uris" target="_blank" rel="noopener"&gt;Learn More&lt;/A&gt;&lt;/LI&gt;&lt;LI&gt;The REST request on the endpoint URI /services/storage/investigation/investigation?count=0&amp;amp;all=true&amp;amp;earliest=-700d&amp;amp;latest=-2d&amp;amp;output_mode=xml returned HTTP 'status not OK': code=400, Bad Request.&lt;P&gt;&amp;nbsp;&lt;/P&gt;Looking up similar questions here leads me to believe that it might be an issue with the REST api path for investigations. Does anyone know if there is a different path for investigations for ES 6.0.2? I am sure I am missing something simple so don't be afraid to "barney" style this.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Other questions:&lt;BR /&gt;&lt;A href="https://community.splunk.com/t5/Splunk-Enterprise-Security/Why-do-we-get-errors-on-the-REST-command-in-the-Investigation/m-p/470951" target="_blank" rel="noopener"&gt;https://community.splunk.com/t5/Splunk-Enterprise-Security/Why-do-we-get-errors-on-the-REST-command-in-the-Investigation/m-p/470951&lt;BR /&gt;&lt;BR /&gt;&lt;/A&gt;&lt;/LI&gt;&lt;/UL&gt;</description>
    <pubDate>Tue, 13 Jul 2021 15:53:46 GMT</pubDate>
    <dc:creator>ctfletcher</dc:creator>
    <dc:date>2021-07-13T15:53:46Z</dc:date>
    <item>
      <title>ES Investigation REST API Error</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/ES-Investigation-REST-API-Error/m-p/559289#M10058</link>
      <description>&lt;P&gt;Greetings Splunkers,&lt;/P&gt;&lt;P&gt;I have a dashboard that "broke" over the weekend. When I run any of the dashboard searches I see errors of:&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Unexpected status for to fetch REST endpoint uri=&lt;A href="https://127.0.0.1:8089/services/storage/investigation/investigation?count=0&amp;amp;all=true&amp;amp;earliest=-700d&amp;amp;latest=-2d&amp;amp;output_mode=xml" target="_blank" rel="noopener"&gt;https://127.0.0.1:8089/services/storage/investigation/investigation?count=0&amp;amp;all=true&amp;amp;earliest=-700d&amp;amp;latest=-2d&amp;amp;output_mode=xml from server=&lt;/A&gt;&lt;A href="https://127.0.0.1:8089" target="_blank" rel="noopener"&gt;https://127.0.0.1:8089 - Bad Request&lt;/A&gt;&lt;/LI&gt;&lt;LI&gt;Failed to fetch REST endpoint uri=&lt;A href="https://127.0.0.1:8089/services/storage/investigation/investigation?count=0&amp;amp;all=true&amp;amp;earliest=-700d&amp;amp;latest=-2d&amp;amp;output_mode=xml" target="_blank" rel="noopener"&gt;https://127.0.0.1:8089/services/storage/investigation/investigation?count=0&amp;amp;all=true&amp;amp;earliest=-700d&amp;amp;latest=-2d&amp;amp;output_mode=xml from server &lt;/A&gt;&lt;A href="https://127.0.0.1:8089" target="_blank" rel="noopener"&gt;https://127.0.0.1:8089. Check that the URI path provided exists in the REST API. &lt;/A&gt;&lt;A href="https://splunk-es/en-US/help?location=message.rest.reference.uris" target="_blank" rel="noopener"&gt;Learn More&lt;/A&gt;&lt;/LI&gt;&lt;LI&gt;The REST request on the endpoint URI /services/storage/investigation/investigation?count=0&amp;amp;all=true&amp;amp;earliest=-700d&amp;amp;latest=-2d&amp;amp;output_mode=xml returned HTTP 'status not OK': code=400, Bad Request.&lt;P&gt;&amp;nbsp;&lt;/P&gt;Looking up similar questions here leads me to believe that it might be an issue with the REST api path for investigations. Does anyone know if there is a different path for investigations for ES 6.0.2? I am sure I am missing something simple so don't be afraid to "barney" style this.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Other questions:&lt;BR /&gt;&lt;A href="https://community.splunk.com/t5/Splunk-Enterprise-Security/Why-do-we-get-errors-on-the-REST-command-in-the-Investigation/m-p/470951" target="_blank" rel="noopener"&gt;https://community.splunk.com/t5/Splunk-Enterprise-Security/Why-do-we-get-errors-on-the-REST-command-in-the-Investigation/m-p/470951&lt;BR /&gt;&lt;BR /&gt;&lt;/A&gt;&lt;/LI&gt;&lt;/UL&gt;</description>
      <pubDate>Tue, 13 Jul 2021 15:53:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/ES-Investigation-REST-API-Error/m-p/559289#M10058</guid>
      <dc:creator>ctfletcher</dc:creator>
      <dc:date>2021-07-13T15:53:46Z</dc:date>
    </item>
  </channel>
</rss>

