Splunk Search

Is there a way not to restart entire splunk instance after making changes in .conf files?

krishnakanthgup
New Member

In general after we make changes in .conf files splunk instance should restart. If we deploy splunk in production environment and after making changes in .conf files a restart of entire splunk might be problem. so, is there any way we can resolve this problem?

Tags (1)
0 Karma
1 Solution

nickstone
Path Finder

If its just a change to a search time transforms.conf, you could use the following SPL:
| extract reload=t

View solution in original post

0 Karma

nickstone
Path Finder

If its just a change to a search time transforms.conf, you could use the following SPL:
| extract reload=t

0 Karma

krishnakanthgup
New Member

Thanks Nickstone. but what if it was a props.conf file?

0 Karma

gjanders
SplunkTrust
SplunkTrust

As per the props.conf documentation:
# You can enable configurations changes made to props.conf by typing the
# following search string in Splunk Web:
#
# | extract reload=T

So yes that will work for props and transforms.conf

0 Karma
Get Updates on the Splunk Community!

Extending Observability Content to Splunk Cloud

Watch Now!   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to leverage ...

More Control Over Your Monitoring Costs with Archived Metrics!

What if there was a way you could keep all the metrics data you need while saving on storage costs?This is now ...

New in Observability Cloud - Explicit Bucket Histograms

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