<?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 HEC - Why is HTTP Event Collector not Ingesting json logs? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/HEC-Why-is-HTTP-Event-Collector-not-Ingesting-json-logs/m-p/590431#M103439</link>
    <description>&lt;P&gt;We have an on-prem Splunk Enterprise instance using a Deployment server, indexers, search head, etc.&amp;nbsp; The environment sits on Windows 2019 and Splunk is version 8.2.3.&lt;/P&gt;
&lt;P&gt;We have recently setup a HTTP Event Collector token for HEC Collection.&amp;nbsp; It is working correctly from Curl both in Health check and absorbing the manual calls from curl and postman, such as:&lt;/P&gt;
&lt;P&gt;curl -k &lt;A href="http://deploymentserver.local:8088/services/collector/raw" target="_blank" rel="noopener"&gt;http://deploymentserver.local:8088/services/collector/raw&lt;/A&gt; -H "Authorization:Splunk 1920123a-f2b1-4c46-b848-6fba456789fe7" -d '{"Sourcetype":"log4j","event":"test"}'&lt;/P&gt;
&lt;P&gt;These particular calls are ingested and searchable within Splunk.&amp;nbsp; We have opened a ticket with Splunk, but has been less than helpful as the are just directing us to the token setup which as noted above is working.&lt;/P&gt;
&lt;P&gt;The issue, it is not ingesting any of our actual application logs.&amp;nbsp; There are no errors, it has the correct token, it's like it's not getting there or rejected.&amp;nbsp; &amp;nbsp; We've made changes to the sourcetype so there is no criteria as well as set for json, no difference either way.&amp;nbsp; So we suspect the formatting of our json is incorrect.&amp;nbsp; Are there any good samples out there?&lt;/P&gt;
&lt;P&gt;This is what the json looks like:&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;&amp;lt;?xml version="1.0" encoding="utf-8"?&amp;gt;
&amp;lt;Configuration status="INFO" name="cloudhub"
packages="com.appforsplunk.ch.logging.appender, com.splunk.logging
,org.apache.logging.log4j"&amp;gt;
&amp;lt;Appenders&amp;gt;
&amp;lt;Console name="Console" target="SYSTEM_OUT"&amp;gt;
&amp;lt;PatternLayout pattern="%-5p %d [%t] [event: %X{correlationId}] %c: %m%n" /&amp;gt;
&amp;lt;/Console&amp;gt;
&amp;lt;Console name="ConsoleLogUtil" target="SYSTEM_OUT"&amp;gt;
&amp;lt;PatternLayout pattern="%m%n" /&amp;gt;
&amp;lt;/Console&amp;gt;
&amp;lt;RollingFile name="file" fileName="${sys:splunkapp.home}${sys:file.separator}logs${sys:file.separator}splunkapp-custom-logging-api.log"
filePattern="${sys:splunkapp.home}${sys:file.separator}logs${sys:file.separator}splunkapp-custom-logging-api-%i.log"&amp;gt;
&amp;lt;PatternLayout pattern="%-5p %d [%t] [processor: %X{processorPath}; event: %X{correlationId}] %c: %m%n" /&amp;gt;
&amp;lt;SizeBasedTriggeringPolicy size="10 MB" /&amp;gt;
&amp;lt;DefaultRolloverStrategy max="10"/&amp;gt;
&amp;lt;/RollingFile&amp;gt;
&amp;lt;SplunkHttp name="splunk" url="http://deploymentserver.local:8088/services/collector/raw" token="Splunk 50817720-52e2-4481-a2cf-eb519716354c" disableCertificateValidation="true"&amp;gt;
&amp;lt;PatternLayout pattern="%-5p %d [%t] [event: %X{correlationId}] %c: %m%n"/&amp;gt;
&amp;lt;/SplunkHttp&amp;gt;
&amp;lt;Log4J2CloudhubLogAppender name="CLOUDHUB" addressProvider="com.appforsplunk.ch.logging.DefaultAggregatorAddressProvider"
applicationContext="com.appforsplunk.ch.logging.DefaultApplicationContext"
appendRetryIntervalMs="${sys:logging.appendRetryInterval}"
appendMaxAttempts="${sys:logging.appendMaxAttempts}"
batchSendIntervalMs="${sys:logging.batchSendInterval}"
batchMaxRecords="${sys:logging.batchMaxRecords}" memBufferMaxSize="${sys:logging.memBufferMaxSize}"
journalMaxWriteBatchSize="${sys:logging.journalMaxBatchSize}"
journalMaxFileSize="${sys:logging.journalMaxFileSize}"
clientMaxPacketSize="${sys:logging.clientMaxPacketSize}"
clientConnectTimeoutMs="${sys:logging.clientConnectTimeout}"
clientSocketTimeoutMs="${sys:logging.clientSocketTimeout}"
serverAddressPollIntervalMs="${sys:logging.serverAddressPollInterval}"
serverHeartbeatSendIntervalMs="${sys:logging.serverHeartbeatSendIntervalMs}"
statisticsPrintIntervalMs="${sys:logging.statisticsPrintIntervalMs}"&amp;gt;
&amp;lt;PatternLayout pattern="[%d{MM-dd HH:mm:ss}] %-5p %c{1} [%t]: %m%n" /&amp;gt;
&amp;lt;/Log4J2CloudhubLogAppender&amp;gt;
&amp;lt;/Appenders&amp;gt;
&amp;lt;Loggers&amp;gt;
&amp;lt;AsyncLogger name="org.splunkapp.service.http" level="WARN"/&amp;gt;
&amp;lt;AsyncLogger name="org.splunkapp.extension.http" level="WARN"/&amp;gt;
&amp;lt;!-- splunkapp logger --&amp;gt;
&amp;lt;AsyncLogger name="org.splunkapp.runtime.core.internal.processor.LoggerMessageProcessor" level="INFO"/&amp;gt;
&amp;lt;AsyncRoot level="INFO"&amp;gt;
&amp;lt;AppenderRef ref="splunk" /&amp;gt;
&amp;lt;AppenderRef ref="CLOUDHUB" /&amp;gt;
&amp;lt;AppenderRef ref="Console"/&amp;gt;
&amp;lt;AppenderRef ref="file" /&amp;gt;
&amp;lt;/AsyncRoot&amp;gt;
&amp;lt;/Loggers&amp;gt;
&amp;lt;/Configuration&amp;gt;&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;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks in advance.&lt;/P&gt;</description>
    <pubDate>Wed, 23 Mar 2022 22:32:56 GMT</pubDate>
    <dc:creator>rtengineer</dc:creator>
    <dc:date>2022-03-23T22:32:56Z</dc:date>
    <item>
      <title>HEC - Why is HTTP Event Collector not Ingesting json logs?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/HEC-Why-is-HTTP-Event-Collector-not-Ingesting-json-logs/m-p/590431#M103439</link>
      <description>&lt;P&gt;We have an on-prem Splunk Enterprise instance using a Deployment server, indexers, search head, etc.&amp;nbsp; The environment sits on Windows 2019 and Splunk is version 8.2.3.&lt;/P&gt;
&lt;P&gt;We have recently setup a HTTP Event Collector token for HEC Collection.&amp;nbsp; It is working correctly from Curl both in Health check and absorbing the manual calls from curl and postman, such as:&lt;/P&gt;
&lt;P&gt;curl -k &lt;A href="http://deploymentserver.local:8088/services/collector/raw" target="_blank" rel="noopener"&gt;http://deploymentserver.local:8088/services/collector/raw&lt;/A&gt; -H "Authorization:Splunk 1920123a-f2b1-4c46-b848-6fba456789fe7" -d '{"Sourcetype":"log4j","event":"test"}'&lt;/P&gt;
&lt;P&gt;These particular calls are ingested and searchable within Splunk.&amp;nbsp; We have opened a ticket with Splunk, but has been less than helpful as the are just directing us to the token setup which as noted above is working.&lt;/P&gt;
&lt;P&gt;The issue, it is not ingesting any of our actual application logs.&amp;nbsp; There are no errors, it has the correct token, it's like it's not getting there or rejected.&amp;nbsp; &amp;nbsp; We've made changes to the sourcetype so there is no criteria as well as set for json, no difference either way.&amp;nbsp; So we suspect the formatting of our json is incorrect.&amp;nbsp; Are there any good samples out there?&lt;/P&gt;
&lt;P&gt;This is what the json looks like:&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;&amp;lt;?xml version="1.0" encoding="utf-8"?&amp;gt;
&amp;lt;Configuration status="INFO" name="cloudhub"
packages="com.appforsplunk.ch.logging.appender, com.splunk.logging
,org.apache.logging.log4j"&amp;gt;
&amp;lt;Appenders&amp;gt;
&amp;lt;Console name="Console" target="SYSTEM_OUT"&amp;gt;
&amp;lt;PatternLayout pattern="%-5p %d [%t] [event: %X{correlationId}] %c: %m%n" /&amp;gt;
&amp;lt;/Console&amp;gt;
&amp;lt;Console name="ConsoleLogUtil" target="SYSTEM_OUT"&amp;gt;
&amp;lt;PatternLayout pattern="%m%n" /&amp;gt;
&amp;lt;/Console&amp;gt;
&amp;lt;RollingFile name="file" fileName="${sys:splunkapp.home}${sys:file.separator}logs${sys:file.separator}splunkapp-custom-logging-api.log"
filePattern="${sys:splunkapp.home}${sys:file.separator}logs${sys:file.separator}splunkapp-custom-logging-api-%i.log"&amp;gt;
&amp;lt;PatternLayout pattern="%-5p %d [%t] [processor: %X{processorPath}; event: %X{correlationId}] %c: %m%n" /&amp;gt;
&amp;lt;SizeBasedTriggeringPolicy size="10 MB" /&amp;gt;
&amp;lt;DefaultRolloverStrategy max="10"/&amp;gt;
&amp;lt;/RollingFile&amp;gt;
&amp;lt;SplunkHttp name="splunk" url="http://deploymentserver.local:8088/services/collector/raw" token="Splunk 50817720-52e2-4481-a2cf-eb519716354c" disableCertificateValidation="true"&amp;gt;
&amp;lt;PatternLayout pattern="%-5p %d [%t] [event: %X{correlationId}] %c: %m%n"/&amp;gt;
&amp;lt;/SplunkHttp&amp;gt;
&amp;lt;Log4J2CloudhubLogAppender name="CLOUDHUB" addressProvider="com.appforsplunk.ch.logging.DefaultAggregatorAddressProvider"
applicationContext="com.appforsplunk.ch.logging.DefaultApplicationContext"
appendRetryIntervalMs="${sys:logging.appendRetryInterval}"
appendMaxAttempts="${sys:logging.appendMaxAttempts}"
batchSendIntervalMs="${sys:logging.batchSendInterval}"
batchMaxRecords="${sys:logging.batchMaxRecords}" memBufferMaxSize="${sys:logging.memBufferMaxSize}"
journalMaxWriteBatchSize="${sys:logging.journalMaxBatchSize}"
journalMaxFileSize="${sys:logging.journalMaxFileSize}"
clientMaxPacketSize="${sys:logging.clientMaxPacketSize}"
clientConnectTimeoutMs="${sys:logging.clientConnectTimeout}"
clientSocketTimeoutMs="${sys:logging.clientSocketTimeout}"
serverAddressPollIntervalMs="${sys:logging.serverAddressPollInterval}"
serverHeartbeatSendIntervalMs="${sys:logging.serverHeartbeatSendIntervalMs}"
statisticsPrintIntervalMs="${sys:logging.statisticsPrintIntervalMs}"&amp;gt;
&amp;lt;PatternLayout pattern="[%d{MM-dd HH:mm:ss}] %-5p %c{1} [%t]: %m%n" /&amp;gt;
&amp;lt;/Log4J2CloudhubLogAppender&amp;gt;
&amp;lt;/Appenders&amp;gt;
&amp;lt;Loggers&amp;gt;
&amp;lt;AsyncLogger name="org.splunkapp.service.http" level="WARN"/&amp;gt;
&amp;lt;AsyncLogger name="org.splunkapp.extension.http" level="WARN"/&amp;gt;
&amp;lt;!-- splunkapp logger --&amp;gt;
&amp;lt;AsyncLogger name="org.splunkapp.runtime.core.internal.processor.LoggerMessageProcessor" level="INFO"/&amp;gt;
&amp;lt;AsyncRoot level="INFO"&amp;gt;
&amp;lt;AppenderRef ref="splunk" /&amp;gt;
&amp;lt;AppenderRef ref="CLOUDHUB" /&amp;gt;
&amp;lt;AppenderRef ref="Console"/&amp;gt;
&amp;lt;AppenderRef ref="file" /&amp;gt;
&amp;lt;/AsyncRoot&amp;gt;
&amp;lt;/Loggers&amp;gt;
&amp;lt;/Configuration&amp;gt;&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;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks in advance.&lt;/P&gt;</description>
      <pubDate>Wed, 23 Mar 2022 22:32:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/HEC-Why-is-HTTP-Event-Collector-not-Ingesting-json-logs/m-p/590431#M103439</guid>
      <dc:creator>rtengineer</dc:creator>
      <dc:date>2022-03-23T22:32:56Z</dc:date>
    </item>
  </channel>
</rss>

