splunk / splunk/splunk-library-javalogging
Logs are printed in console, but not getting pushed to Splunk Server
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 140
- Forks
- 173
- PR merge metrics
- No merged PRs in 30d
Description
Logs are printed correctly in console, but not getting pushed to Splunk Server.
And not even printing any error.
Below is my log4j2.xml configuration file
<?xml version="1.0" encoding="UTF-8"?>
<Configuration status="info" name="example" packages="org.example">
<Appenders>
<Console name="console" target="SYSTEM_OUT">
<PatternLayout
pattern="%style{%d{ISO8601}} %highlight{%-5level }[%style{%t}{bright,blue}] %style{%C{10}}{bright,yellow}: %msg%n%throwable" />
</Console>
<File name="MyFile" fileName="logs/app.log">
<PatternLayout>
<Pattern>%d %p %c{1.} [%t] %m%n</Pattern>
</PatternLayout>
</File>
<SplunkHttp name="httpconf"
url="http://localhost:8088"
token="b489e167-d96d-46ec-922f-6b25fc83f199"
host="localhost"
index="spring_dev"
source="source name"
sourcetype="log4j"
messageFormat="text"
disableCertificateValidation="true">
<PatternLayout pattern="%m" />
</SplunkHttp>
</Appenders>
<Loggers>
<Root level="info">
<AppenderRef ref="console" />
<AppenderRef ref="MyFile"/>
<AppenderRef ref="httpconf" />
</Root>
</Loggers>
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the supplied log4j2.xml configuration, focusing on the SplunkHttp appender and its relationship to the root logger. Verify the configured Splunk endpoint and appender behavior; done means application logs are received by the Splunk server and failures are reported when delivery does not work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- observability-sre
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100