<?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 how to configure log4net with nested JSON? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/how-to-configure-log4net-with-nested-JSON/m-p/570653#M101130</link>
    <description>&lt;P class="lia-align-left"&gt;This is really a log4net question but I'm hoping the folks here can help; I have been unsuccessful at searching online for a solution.&lt;/P&gt;&lt;P class="lia-align-left"&gt;-----------------&lt;/P&gt;&lt;P class="lia-align-left"&gt;We have a custom application which generates local logs in JSON format via the log4net module. We then have a Splunk UF installed to collect said logs. In general that all works fine. The problem is that some log messages include a nested JSON '&lt;FONT color="#FF0000"&gt;message&lt;FONT color="#000000"&gt;' field -- but log4net is misformatting it as a string and so Splunk doesn't parse the nested part.&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P class="lia-align-left"&gt;You can see the issue (below) where log4net is unnecessarily adding quote-marks around the nested part:&lt;/P&gt;&lt;P&gt;CURRENT/INVALID&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;"message":"{"command":"Transform271ToBenefitResponse","ms":1}"&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;PROPER&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;"message":{"command":"Transform271ToBenefitResponse","ms":1}&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;--------------------------&lt;/P&gt;&lt;P class="lia-align-left"&gt;I'm not entirely sure of the log4net configuration but here's what I was told by one of our developers:&lt;/P&gt;&lt;P class="lia-align-left"&gt;ORIGINAL LOG4NET CONFIG&lt;/P&gt;&lt;PRE&gt;&amp;lt;conversionPattern value="%utcdate [%property{CorrelationId}] [%property{companyId}] [%property{userId}] [%thread] [%level] %logger - %message%newline" /&amp;gt;&lt;/PRE&gt;&lt;P class="lia-align-left"&gt;UPDATED CONFIG; STILL FAILS&lt;/P&gt;&lt;PRE&gt;&amp;lt;conversionPattern value="{&amp;amp;quot;date&amp;amp;quot;:&amp;amp;quot;%date{ISO8601}&amp;amp;quot;, &amp;amp;quot;correlationId&amp;amp;quot;:&amp;amp;quot;%property{CorrelationId}&amp;amp;quot;, &amp;amp;quot;companyId&amp;amp;quot;:&amp;amp;quot;%property{companyId}&amp;amp;quot;, &amp;amp;quot;userId&amp;amp;quot;:&amp;amp;quot;%property{userId}&amp;amp;quot;, &amp;amp;quot;thread&amp;amp;quot;:&amp;amp;quot;%thread&amp;amp;quot;, &amp;amp;quot;level&amp;amp;quot;:&amp;amp;quot;%level&amp;amp;quot;, &amp;amp;quot;logger&amp;amp;quot;:&amp;amp;quot;%logger&amp;amp;quot;, &amp;amp;quot;message&amp;amp;quot;:&amp;amp;quot;%message&amp;amp;quot;}%newline" /&amp;gt;&lt;/PRE&gt;&lt;P class="lia-align-left"&gt;&amp;nbsp;&lt;/P&gt;&lt;P class="lia-align-left"&gt;&amp;nbsp;&lt;/P&gt;&lt;P class="lia-align-left"&gt;&amp;nbsp;&lt;/P&gt;&lt;P class="lia-align-left"&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;&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 12 Oct 2021 16:43:40 GMT</pubDate>
    <dc:creator>ttovarzoll</dc:creator>
    <dc:date>2021-10-12T16:43:40Z</dc:date>
    <item>
      <title>how to configure log4net with nested JSON?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/how-to-configure-log4net-with-nested-JSON/m-p/570653#M101130</link>
      <description>&lt;P class="lia-align-left"&gt;This is really a log4net question but I'm hoping the folks here can help; I have been unsuccessful at searching online for a solution.&lt;/P&gt;&lt;P class="lia-align-left"&gt;-----------------&lt;/P&gt;&lt;P class="lia-align-left"&gt;We have a custom application which generates local logs in JSON format via the log4net module. We then have a Splunk UF installed to collect said logs. In general that all works fine. The problem is that some log messages include a nested JSON '&lt;FONT color="#FF0000"&gt;message&lt;FONT color="#000000"&gt;' field -- but log4net is misformatting it as a string and so Splunk doesn't parse the nested part.&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P class="lia-align-left"&gt;You can see the issue (below) where log4net is unnecessarily adding quote-marks around the nested part:&lt;/P&gt;&lt;P&gt;CURRENT/INVALID&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;"message":"{"command":"Transform271ToBenefitResponse","ms":1}"&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;PROPER&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;"message":{"command":"Transform271ToBenefitResponse","ms":1}&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;--------------------------&lt;/P&gt;&lt;P class="lia-align-left"&gt;I'm not entirely sure of the log4net configuration but here's what I was told by one of our developers:&lt;/P&gt;&lt;P class="lia-align-left"&gt;ORIGINAL LOG4NET CONFIG&lt;/P&gt;&lt;PRE&gt;&amp;lt;conversionPattern value="%utcdate [%property{CorrelationId}] [%property{companyId}] [%property{userId}] [%thread] [%level] %logger - %message%newline" /&amp;gt;&lt;/PRE&gt;&lt;P class="lia-align-left"&gt;UPDATED CONFIG; STILL FAILS&lt;/P&gt;&lt;PRE&gt;&amp;lt;conversionPattern value="{&amp;amp;quot;date&amp;amp;quot;:&amp;amp;quot;%date{ISO8601}&amp;amp;quot;, &amp;amp;quot;correlationId&amp;amp;quot;:&amp;amp;quot;%property{CorrelationId}&amp;amp;quot;, &amp;amp;quot;companyId&amp;amp;quot;:&amp;amp;quot;%property{companyId}&amp;amp;quot;, &amp;amp;quot;userId&amp;amp;quot;:&amp;amp;quot;%property{userId}&amp;amp;quot;, &amp;amp;quot;thread&amp;amp;quot;:&amp;amp;quot;%thread&amp;amp;quot;, &amp;amp;quot;level&amp;amp;quot;:&amp;amp;quot;%level&amp;amp;quot;, &amp;amp;quot;logger&amp;amp;quot;:&amp;amp;quot;%logger&amp;amp;quot;, &amp;amp;quot;message&amp;amp;quot;:&amp;amp;quot;%message&amp;amp;quot;}%newline" /&amp;gt;&lt;/PRE&gt;&lt;P class="lia-align-left"&gt;&amp;nbsp;&lt;/P&gt;&lt;P class="lia-align-left"&gt;&amp;nbsp;&lt;/P&gt;&lt;P class="lia-align-left"&gt;&amp;nbsp;&lt;/P&gt;&lt;P class="lia-align-left"&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;&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Oct 2021 16:43:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/how-to-configure-log4net-with-nested-JSON/m-p/570653#M101130</guid>
      <dc:creator>ttovarzoll</dc:creator>
      <dc:date>2021-10-12T16:43:40Z</dc:date>
    </item>
  </channel>
</rss>

