<?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: Splunk logging driver logs not parsed by indexer in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-logging-driver-logs-not-parsed-by-indexer/m-p/527507#M88960</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;when catching up source at props.conf stanza you have to use two colons instead of equal sign. Like&lt;/P&gt;&lt;P&gt;[source::http:docker]&lt;/P&gt;&lt;P&gt;For regex I would use capturing group, for example&lt;/P&gt;&lt;P&gt;REGEX = security_level\":\"([^"]*)&lt;BR /&gt;DEST_KEY = _MetaData:Index&lt;BR /&gt;FORMAT = $1&lt;/P&gt;&lt;P&gt;When event goes to xx -index.&amp;nbsp;Or as hard coded&amp;nbsp;&lt;/P&gt;&lt;P&gt;REGEX = security_level\":\"xx\"&lt;BR /&gt;DEST_KEY = _MetaData:Index&lt;BR /&gt;FORMAT = xx_index&lt;/P&gt;&lt;P&gt;Event ends up to&amp;nbsp;xx_index -index.&lt;/P&gt;</description>
    <pubDate>Mon, 02 Nov 2020 11:48:31 GMT</pubDate>
    <dc:creator>juhatamminen</dc:creator>
    <dc:date>2020-11-02T11:48:31Z</dc:date>
    <item>
      <title>Splunk logging driver logs not parsed by indexer</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-logging-driver-logs-not-parsed-by-indexer/m-p/523847#M88454</link>
      <description>&lt;P&gt;Hi Splunkers,&lt;/P&gt;&lt;P&gt;I have start using Splunk Logging Driver to get my docker logs into Splunk. I am using Splunk Enterprice 8.0.1.&lt;/P&gt;&lt;P&gt;Problem is that indexer does not parse docker logs. I have tried with json and raw formats but either seems not to be noticed by indexer.&lt;/P&gt;&lt;P&gt;Current setup. HEC token used has source type _raw and all indexes allowed.&lt;/P&gt;&lt;P&gt;Docker startup&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;docker run \
&amp;gt; --log-driver=splunk \
&amp;gt; --log-opt splunk-token=xxxx \
&amp;gt; --log-opt splunk-url=http://xxxxx:8088 \
&amp;gt; --log-opt splunk-format=raw \
&amp;gt; --log-opt tag="{{.Name}}/{{.FullID}}" \
&amp;gt; --log-opt labels=location \
&amp;gt; --log-opt env=TEST \
&amp;gt; --env "TEST=false" \
&amp;gt; --label location=xxxxx \
&amp;gt; containerId&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;props.conf&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[source=http:docker]
INDEXED_EXTRACTIONS=JSON
KV_MODE = none
AUTO_KV_JSON= false
TRANSFORMS-class_to_xx_index = route_to_xx_index&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;transforms.conf&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[route_to_xx_index]
REGEX = .*\"xx\":\"xx\".*
DEST_KEY = _MetaData:Index
FORMAT = xx_index&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;All logs are going to default index. I have double checked that regex pattern matches and same pattern is working for universal forwarder, which logs are parsed and indexed correctly.&lt;/P&gt;&lt;P&gt;Input I get to default index is one line&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;containerName/container location=xx TEST=false {"message":"User xxx does xxx","priority":6,"priorityName":"INFO","sessionId":"xxx","action":"auth/login","application":"xx","environment":"development","security_level":"xx","info":"xxx"}&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;which does not get parsed and index.&lt;/P&gt;&lt;P&gt;&amp;nbsp;If I try with with _json token input to Splunk is "line" format and with same content and logs are also not parsed.&lt;/P&gt;&lt;P&gt;Any idea what I am doing wrong here. How to get json formatted logs to be parsed?&lt;/P&gt;</description>
      <pubDate>Fri, 09 Oct 2020 05:38:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-logging-driver-logs-not-parsed-by-indexer/m-p/523847#M88454</guid>
      <dc:creator>ps</dc:creator>
      <dc:date>2020-10-09T05:38:16Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk logging driver logs not parsed by indexer</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-logging-driver-logs-not-parsed-by-indexer/m-p/524327#M88522</link>
      <description>&lt;P&gt;up&lt;/P&gt;</description>
      <pubDate>Tue, 13 Oct 2020 06:45:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-logging-driver-logs-not-parsed-by-indexer/m-p/524327#M88522</guid>
      <dc:creator>ps</dc:creator>
      <dc:date>2020-10-13T06:45:51Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk logging driver logs not parsed by indexer</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-logging-driver-logs-not-parsed-by-indexer/m-p/527507#M88960</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;when catching up source at props.conf stanza you have to use two colons instead of equal sign. Like&lt;/P&gt;&lt;P&gt;[source::http:docker]&lt;/P&gt;&lt;P&gt;For regex I would use capturing group, for example&lt;/P&gt;&lt;P&gt;REGEX = security_level\":\"([^"]*)&lt;BR /&gt;DEST_KEY = _MetaData:Index&lt;BR /&gt;FORMAT = $1&lt;/P&gt;&lt;P&gt;When event goes to xx -index.&amp;nbsp;Or as hard coded&amp;nbsp;&lt;/P&gt;&lt;P&gt;REGEX = security_level\":\"xx\"&lt;BR /&gt;DEST_KEY = _MetaData:Index&lt;BR /&gt;FORMAT = xx_index&lt;/P&gt;&lt;P&gt;Event ends up to&amp;nbsp;xx_index -index.&lt;/P&gt;</description>
      <pubDate>Mon, 02 Nov 2020 11:48:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-logging-driver-logs-not-parsed-by-indexer/m-p/527507#M88960</guid>
      <dc:creator>juhatamminen</dc:creator>
      <dc:date>2020-11-02T11:48:31Z</dc:date>
    </item>
  </channel>
</rss>

