Splunk Search

What is a good convention for config file organisation?

mikeydee
Explorer

Something to ponder while working from home...

I am planning on storing and managing my config files in Git. We recently ran into a few confusions managing our props files where our support teams got confused about the same props file (containing extracts and line breaking) getting deployed on search heads and on indexers.

So I thought I would come up with a convention that aligns to splunks phases. As per below...

<company>_search_<app>  search app for user dashboards and  reports (not to be held in git at present)
<company>_data_<app>     (field extractsion, calculated fields)
<company>_parse_<app>    (props and transforms for line breaking, timestamping etc)
<deployment>_<p|t>_<app>_<sub_component>  (inputs, outputs etc)  very much environment specific

Does anyone else worry about this stuff like I seem to and have a suggestion?

Mike

Tags (1)
0 Karma

mikeydee
Explorer
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 ...