Getting Data In

Why does data ingestion from Spring boot application to Splunk stops intermittently?

life1style1
New Member

I have a Spring boot application where I have configured log4j to use Http event collector.

The data ingestion is successfully done but the ingestion stops intermittently and again resumes, there is no definite pattern for resuming the ingesion

There is no failure logs in the tomcat as well.

Below are the configuration in log4j2-spring.xml :

 

<SplunkHttp
name="splunkhttp"
host="dummy"
source="source1"
url="https://http-yyy-xxxx.splunkcloud.com"
token="xxxxxxxxxxxxxxxx"
index="ssssssss"
sourcetype="log4j"
disableCertificateValidation="true" >
<PatternLayout
pattern="%m" />
</SplunkHttp>


<Loggers>

</Logger>
<Logger name="com.some.service" level="debug" additivity="false">
<appender-ref ref="splunkhttp" />
</Logger>

</Loggers>

 

The following are the dependency in pom.xml :

 

<repositories>
<repository>
<id>splunk-artifactory</id>
<name>Splunk Releases</name>
<url>https://splunk.jfrog.io/splunk/ext-releases-local</url>
</repository>
</repositories>

 

<repositories>
<repository>
<id>splunk-artifactory</id>
<name>Splunk Releases</name>
<url>https://splunk.jfrog.io/splunk/ext-releases-local</url>
</repository>
</repositories>

 

Any pointer please.

 

Labels (1)
0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...

Casting Call: Compete in Cyber Games

Lights, Camera, SecOps: Apply to Compete in Cyber Games     Think you have what it takes to beat the clock? ...

How Edge Processor's Durable Queue Works

Edge Processor sits in one of the most consequential places in any Splunk pipeline: between your data sources ...