<?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 Ingesting JSON formatted logs into Splunk in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Ingesting-JSON-formatted-logs-into-Splunk/m-p/416727#M73588</link>
    <description>&lt;P&gt;I'm able to get JSON formatted linux os &amp;amp; modx web logs into a Splunk index, but they are not formatted or parsed. How can I get the logs to be efficiently parsed into the index so that they can be searched and used for reporting &amp;amp; dashboards. If this is impractical, is there a better way to get modx web logs into Splunk? If I am able to get them sent in syslog format will they parse correctly?&lt;/P&gt;</description>
    <pubDate>Wed, 27 Feb 2019 22:17:02 GMT</pubDate>
    <dc:creator>lball</dc:creator>
    <dc:date>2019-02-27T22:17:02Z</dc:date>
    <item>
      <title>Ingesting JSON formatted logs into Splunk</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Ingesting-JSON-formatted-logs-into-Splunk/m-p/416727#M73588</link>
      <description>&lt;P&gt;I'm able to get JSON formatted linux os &amp;amp; modx web logs into a Splunk index, but they are not formatted or parsed. How can I get the logs to be efficiently parsed into the index so that they can be searched and used for reporting &amp;amp; dashboards. If this is impractical, is there a better way to get modx web logs into Splunk? If I am able to get them sent in syslog format will they parse correctly?&lt;/P&gt;</description>
      <pubDate>Wed, 27 Feb 2019 22:17:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Ingesting-JSON-formatted-logs-into-Splunk/m-p/416727#M73588</guid>
      <dc:creator>lball</dc:creator>
      <dc:date>2019-02-27T22:17:02Z</dc:date>
    </item>
    <item>
      <title>Re: Ingesting JSON formatted logs into Splunk</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Ingesting-JSON-formatted-logs-into-Splunk/m-p/416728#M73589</link>
      <description>&lt;P&gt;What are the props.conf settings for that sourcetype?&lt;/P&gt;</description>
      <pubDate>Wed, 27 Feb 2019 22:22:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Ingesting-JSON-formatted-logs-into-Splunk/m-p/416728#M73589</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2019-02-27T22:22:14Z</dc:date>
    </item>
    <item>
      <title>Re: Ingesting JSON formatted logs into Splunk</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Ingesting-JSON-formatted-logs-into-Splunk/m-p/416729#M73590</link>
      <description>&lt;P&gt;If you can grab a copy of the file you are trying to read, then on a dev splunk instance walk through the Add Data function in the web console.&lt;/P&gt;

&lt;P&gt;Just import your file directly and when at the Set Source Type, choose, Structured-&amp;gt;_json&lt;/P&gt;

&lt;P&gt;You can then make sure it looks like it is parsing correctly and do a Save As to a new name/sourcetype name.  Then when you finish getting it all read in, you can go to your drive and look for the inputs/props/transforms conf files it would create.  Then you can use those on the forwarder you are trying to read the file originally from (or pushed out through a deployment server in an app).&lt;/P&gt;</description>
      <pubDate>Wed, 27 Feb 2019 22:31:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Ingesting-JSON-formatted-logs-into-Splunk/m-p/416729#M73590</guid>
      <dc:creator>jeffbat</dc:creator>
      <dc:date>2019-02-27T22:31:59Z</dc:date>
    </item>
    <item>
      <title>Re: Ingesting JSON formatted logs into Splunk</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Ingesting-JSON-formatted-logs-into-Splunk/m-p/416730#M73591</link>
      <description>&lt;P&gt;Like richgalloway mentioned in props.conf, make sure it has set KV_MODE = json. Also make sure that each event is a complete JSON event (for example doesn't have any text written before the JSON)&lt;/P&gt;

&lt;P&gt;You could always copy a JSON line and paste it into a JSON pretty print web site to make sure they can parse it, like &lt;A href="https://jsonformatter.org/json-pretty-print"&gt;https://jsonformatter.org/json-pretty-print&lt;/A&gt;.&lt;/P&gt;</description>
      <pubDate>Thu, 28 Feb 2019 04:19:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Ingesting-JSON-formatted-logs-into-Splunk/m-p/416730#M73591</guid>
      <dc:creator>worshamn</dc:creator>
      <dc:date>2019-02-28T04:19:14Z</dc:date>
    </item>
    <item>
      <title>Re: Ingesting JSON formatted logs into Splunk</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Ingesting-JSON-formatted-logs-into-Splunk/m-p/416731#M73592</link>
      <description>&lt;P&gt;Thanks for the tip!&lt;/P&gt;</description>
      <pubDate>Mon, 02 Sep 2019 13:45:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Ingesting-JSON-formatted-logs-into-Splunk/m-p/416731#M73592</guid>
      <dc:creator>hookupgeek</dc:creator>
      <dc:date>2019-09-02T13:45:36Z</dc:date>
    </item>
  </channel>
</rss>

