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!

New in Observability Cloud - Explicit Bucket Histograms

Splunk introduces native support for histograms as a metric data type within Observability Cloud with Explicit ...

Updated Team Landing Page in Splunk Observability

We’re making some changes to the team landing page in Splunk Observability, based on your feedback. The ...

New! Splunk Observability Search Enhancements for Splunk APM Services/Traces and ...

Regardless of where you are in Splunk Observability, you can search for relevant APM targets including service ...