Deployment Architecture

Why New Index is disabled by default after creation?

andrewpagans
Path Finder

Hello,
after creation , the index is disabled by default (so to manually enable I need to restart server).
is there any setting that I can change in order to have the index enabled by default after creation?

In my local machine works well (Index enabled by default after creation).
Why in production Env is present this behavior (Index disabled by default after creation).

Thank you

Tags (1)
0 Karma

andrewpagans
Path Finder

I did these tests:

Local Machine:
- New Index created when adding Data--> monitor
- New index creared from Settings--> Indexes
In both cases the index is ready and enabled after creation, no need to restart.

Prod machine:
- New Index created when adding Data--> monitor : new index does not apper in the liste after creation. I need to go under Index setting enable and restart. after these procedures the index is visible in drop down list.
- New index creared from Settings--> Indexes : new index created appear disabled , so I need to enable and restart.

Thanks

0 Karma

valiquet
Contributor

Even on stand alone instance you need to restart. How did you create the index? Does in non prod you might have written to main index instead?

0 Karma
Get Updates on the Splunk Community!

Stay Connected: Your Guide to May Tech Talks, Office Hours, and Webinars!

Take a look below to explore our upcoming Community Office Hours, Tech Talks, and Webinars this month. This ...

They're back! Join the SplunkTrust and MVP at .conf24

With our highly anticipated annual conference, .conf, comes the fez-wearers you can trust! The SplunkTrust, as ...

Enterprise Security Content Update (ESCU) | New Releases

Last month, the Splunk Threat Research Team had two releases of new security content via the Enterprise ...