<?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: Issue with parsing Json data in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Issue-with-parsing-Json-data/m-p/531443#M89401</link>
    <description>&lt;P&gt;I would rather use index-time parsing. Honestly speaking I'm not very familiar with "spath" command. Could it help with parsing, even though line _breaker isn't correct?&lt;/P&gt;</description>
    <pubDate>Tue, 01 Dec 2020 07:12:49 GMT</pubDate>
    <dc:creator>slipinski</dc:creator>
    <dc:date>2020-12-01T07:12:49Z</dc:date>
    <item>
      <title>Issue with parsing Json data</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Issue-with-parsing-Json-data/m-p/531409#M89396</link>
      <description>&lt;P&gt;Hello Splunkers,&lt;/P&gt;&lt;P&gt;I'm facing problem with correct parsing json data. Splunk correctly recognizes data as json sourced, but with default settings, it cannot parse data correctly. It creates fields like: 3b629fbf-be6c-4806-8ceb-1e2b196b6277.currentUtilisation or device31.1.127.out::device54.1.87.in.currentUtilisation. As the main field is irregular I don't know how to set line_breaker which is the most likely main cause of the problem. Can I count on your help?&lt;BR /&gt;A chunk of the input file is below.&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; {
 	"device31.1.127.out::device54.1.87.in": {
 		"currentUtilisation": 0.0,
 		"enabled": true,
 		"from": "device31.1.127.out",
 		"hasBookings": false,
 		"id": "device31.1.127.out::device54.1.87.in",
 		"isActive": false,
 		"name": "Adam",
 		"props": {
 			"bandwidth": 90000.0,
 			"conflictPri": 1,
 			"description": ""
 		},
 		"to": "device54.1.87.in",
 		"usage": {
 			"bookings": [],
 			"id": "device31.1.127.out::device54.1.87.in"
 		}
 	},
 	"device49.1.117.out::device34.1.69.in": {
 		"currentUtilisation": 0.0,
 		"enabled": true,
 		"from": "device49.1.117.out",
 		"hasBookings": false,
 		"id": "device49.1.117.out::device34.1.69.in",
 		"isActive": false,
 		"name": "Barek",
 		"props": {
 			"bandwidth": 90000.0,
 			"conflictPri": 1,
 			"description": ""
 		},
 		"to": "device34.1.69.in",
 		"usage": {
 			"bookings": [],
 			"id": "device49.1.117.out::device34.1.69.in"
 		}
 	},
 	"3b629fbf-be6c-4806-8ceb-1e2b196b6277": {
 		"currentUtilisation": 0.0,
 		"enabled": true,
 		"from": "device38.1.93.out",
 		"hasBookings": false,
 		"id": "3b629fbf-be6c-4806-8ceb-1e2b196b6277",
 		"isActive": false,
 		"name": "Cezary",
 		"props": {
 			"bandwidth": 90000.0,
 			"conflictPri": 1,
 			"description": ""
 		},
 		"to": "device441.1.89.in",
 		"usage": {
 			"bookings": [],
 			"id": "3b629fbf-be6c-4806-8ceb-1e2b196b6277"
 		}
 	},
 	"87725874-f760-4e37-9421-168506a05573": {
 		"currentUtilisation": 0.0,
 		"enabled": true,
 		"from": "device21.1.75.out",
 		"hasBookings": false,
 		"id": "87725874-f760-4e37-9421-168506a05573",
 		"isActive": false,
 		"name": "Darek",
 		"props": {
 			"bandwidth": 90000.0,
 			"conflictPri": 1,
 			"description": ""
 		},
 		"to": "device61.1.97.in",
 		"usage": {
 			"bookings": [],
 			"id": "87725874-f760-4e37-9421-168506a05573"
 		}
 	}
 }&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 30 Nov 2020 21:46:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Issue-with-parsing-Json-data/m-p/531409#M89396</guid>
      <dc:creator>slipinski</dc:creator>
      <dc:date>2020-11-30T21:46:00Z</dc:date>
    </item>
    <item>
      <title>Re: Issue with parsing Json data</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Issue-with-parsing-Json-data/m-p/531415#M89397</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/124273"&gt;@slipinski&lt;/a&gt;&amp;nbsp;would you like index-time or search-time parsing? may i know if you are aware of the command "spath", please suggest, thanks.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Best Regards,&lt;/P&gt;&lt;P&gt;Sekar&lt;/P&gt;</description>
      <pubDate>Mon, 30 Nov 2020 23:54:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Issue-with-parsing-Json-data/m-p/531415#M89397</guid>
      <dc:creator>inventsekar</dc:creator>
      <dc:date>2020-11-30T23:54:33Z</dc:date>
    </item>
    <item>
      <title>Re: Issue with parsing Json data</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Issue-with-parsing-Json-data/m-p/531443#M89401</link>
      <description>&lt;P&gt;I would rather use index-time parsing. Honestly speaking I'm not very familiar with "spath" command. Could it help with parsing, even though line _breaker isn't correct?&lt;/P&gt;</description>
      <pubDate>Tue, 01 Dec 2020 07:12:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Issue-with-parsing-Json-data/m-p/531443#M89401</guid>
      <dc:creator>slipinski</dc:creator>
      <dc:date>2020-12-01T07:12:49Z</dc:date>
    </item>
  </channel>
</rss>

