Deployment Architecture

Internal Logs from Forwarders not stopped

amulay26
Path Finder

I am trying to stop the splunkd.log and metrics.log from Windows Universal Forwarders.

Since it is a distributed environment, I deployed a small base app config to make this happen. My inputs.conf stanza looks like as follows:

[monitor://$SPLUNK_HOME\var\log\splunk\splunkd.log]
index = _internal
disabled = true

[monitor://$SPLUNK_HOME\var\log\splunk\metrics.log]
index = _internal
disabled = true

Any suggestions?

Thanks in advance.

  • Akshay
Tags (1)
0 Karma

HiroshiSatoh
Champion

There is a possibility that settings are duplicated. How about excluding it as a black list?

[monitor://$SPLUNK_HOME\var\log\splunk]
index = _internal

※ Restart is okay?

0 Karma

amulay26
Path Finder

Do you mean excluding at as a blacklist in outputs.conf?

I have enabled restart splunkd option while deploying it from deployment server.

0 Karma

HiroshiSatoh
Champion

Set blacklist in inputs.conf. See blacklist setting in the default inputs.conf.

[blacklist:$SPLUNK_HOME\etc\auth]
Please add the setting in the same way.

0 Karma
Get Updates on the Splunk Community!

More Ways To Control Your Costs With Archived Metrics | Register for Tech Talk

Tuesday, May 14, 2024  |  11AM PT / 2PM ET Register to Attend Join us in this Tech Talk and learn how to ...

.conf24 | Personalize your .conf experience with Learning Paths!

Personalize your .conf24 Experience Learning paths allow you to level up your skill sets and dive deeper ...

Threat Hunting Unlocked: How to Uplevel Your Threat Hunting With the PEAK Framework ...

WATCH NOWAs AI starts tackling low level alerts, it's more critical than ever to uplevel your threat hunting ...