Splunk Dev

ModularInput - Input not written in myapp/local/inputs.conf but in /search/local/inputs.conf

rechteklebe
Path Finder

Hi, 

I've recognized that my modularinput configuration for "myapp" has a strange situation.

When I am in Splunk using "myapp" and go to Data Inputs>MyAppInput, the inputs.conf file gets written properly (<myapp>/local/inputs.conf).

But when someone is in another app than "myapp" (e.g. search), and goes to Data Inputs>MyAppInput, the data gets written to /search/local/inputs.conf (not "myapp" app).

It gets written to the application folder from where you click on "Data Inputs".

How can i make sure that from wherever the user clicks on " Data Inputs>MyAppInput", the data gets only written in  (<myapp>/local/inputs.conf)?

Thanks!

Labels (1)
0 Karma

thambisetty
SplunkTrust
SplunkTrust

That’s Splunk Enterprise default behavior.

otherwise splunk doesn’t know where to write custom configurations. 

————————————
If this helps, give a like below.
0 Karma
Get Updates on the Splunk Community!

Unleash the Power of Splunk MCP and AI, Meet Us at .Conf 2025, and Find Even More New ...

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...

Observability Professionals: Build Resilience and Visibility with These .conf25 ...

  If you're focused on performance, availability, and full-stack visibility, the Observability track at ...

See just what you’ve been missing | Observability tracks at Splunk University

Looking to sharpen your observability skills so you can better understand how to collect and analyze data from ...