All Apps and Add-ons

log is going to _internal index

shashidharh
Explorer

Hi,

Logs are going to _internal index instead of customized index.

host = xxxx
index = _internal
source = C:\Program Files\SplunkUniversalForwarder\var\log\splunk\splunkd.log
sourcetype = splunkd

inputs.conf and props.conf are set properly in deployment server.Also verified in the SplunkForwarder "Windows"  server.  Still getting above one , not going to customized index.

What could be the reason ?

Labels (3)
0 Karma

richgalloway
SplunkTrust
SplunkTrust

The reason is simple: that is where Splunk is told to put the data.  It's also the default setting so no real surprise.  To find out which config file is specifying the settings, run btool on the forwarder.

\Program Files\Splunk\bin\splunk.exe btool --debug inputs list 

Then you'll know which file to modify to have the data go to the desired index.

Be aware that sending data to a custom index rather than _internal may have license implications and may break some dashboards.

---
If this reply helps you, Karma would be appreciated.
0 Karma
Get Updates on the Splunk Community!

Monitoring Postgres with OpenTelemetry

Behind every business-critical application, you’ll find databases. These behind-the-scenes stores power ...

Mastering Synthetic Browser Testing: Pro Tips to Keep Your Web App Running Smoothly

To start, if you're new to synthetic monitoring, I recommend exploring this synthetic monitoring overview. In ...

Splunk Edge Processor | Popular Use Cases to Get Started with Edge Processor

Splunk Edge Processor offers more efficient, flexible data transformation – helping you reduce noise, control ...