The more that I understand and rely only the tooling that I can create in Splunk:
- saved searches
- Field knowledge Objects
- Lookup table definitions
The more that I realize that I will ultimately need some notion of source code management for the objects that I create. I want to protect myself from me or my teammates accidentally changing the tooling that we are coming to count on.
Are there any Source Control Management tools that work (and better yet, integrate) well with Splunk? Does anyone have any experience that they could share?
I am currently on a path to just paste a copy of the things that my team counts on into Accurev (the tool our AD team uses), but it would be better to have integration to
The most common one is git, in particular Atlassian's Bit Bucket Server (formerly Stash). Here's a link to one discussion, but there are at least 4-5 threads on various issues and questions.
@DalJeanis: which of the following was your intent: