<?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: JSON Parsing issues in Splunk Cloud Platform</title>
    <link>https://community.splunk.com/t5/Splunk-Cloud-Platform/JSON-Parsing-issues/m-p/520489#M217</link>
    <description>&lt;P&gt;there could be issue with event format.&lt;/P&gt;</description>
    <pubDate>Sun, 20 Sep 2020 12:14:12 GMT</pubDate>
    <dc:creator>thambisetty</dc:creator>
    <dc:date>2020-09-20T12:14:12Z</dc:date>
    <item>
      <title>JSON Parsing issues</title>
      <link>https://community.splunk.com/t5/Splunk-Cloud-Platform/JSON-Parsing-issues/m-p/508453#M93</link>
      <description>&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;P&gt;Im sending a large payload of JSON data to splunk (1000 events) over HEC but when it reaches splunk it does not split the event and thinks its just 1 large event. The JSON is valid but its to do with the first part of the JSON thats the issue. It shows as per the below:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;{
"expand": "schema,names",
"startAt": 0,
"maxResults": 50,
"total": 1253,
"issues": [&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If i remove this manually and then the correlating bottom brackets and send manually, all the events are parsed individually.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The second problem i have is that we are on managed splunk cloud so i dont have access to props.conf to amend the line breaker. Can anyone suggest any other way round this?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Im using spyder python as the middle man to send the load and also testing with postman?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 10 Jul 2020 07:37:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Cloud-Platform/JSON-Parsing-issues/m-p/508453#M93</guid>
      <dc:creator>samneo</dc:creator>
      <dc:date>2020-07-10T07:37:16Z</dc:date>
    </item>
    <item>
      <title>Re: JSON Parsing issues</title>
      <link>https://community.splunk.com/t5/Splunk-Cloud-Platform/JSON-Parsing-issues/m-p/520489#M217</link>
      <description>&lt;P&gt;there could be issue with event format.&lt;/P&gt;</description>
      <pubDate>Sun, 20 Sep 2020 12:14:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Cloud-Platform/JSON-Parsing-issues/m-p/520489#M217</guid>
      <dc:creator>thambisetty</dc:creator>
      <dc:date>2020-09-20T12:14:12Z</dc:date>
    </item>
    <item>
      <title>Re: JSON Parsing issues</title>
      <link>https://community.splunk.com/t5/Splunk-Cloud-Platform/JSON-Parsing-issues/m-p/520491#M218</link>
      <description>&lt;P&gt;Can you modify the payload with your middleman? If not, can you use spath to extract the issues array into a multi value field and then mvexpand to separate them into different events?&lt;/P&gt;</description>
      <pubDate>Sun, 20 Sep 2020 12:24:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Cloud-Platform/JSON-Parsing-issues/m-p/520491#M218</guid>
      <dc:creator>ITWhisperer</dc:creator>
      <dc:date>2020-09-20T12:24:49Z</dc:date>
    </item>
  </channel>
</rss>

