Source Control Management

[MonkeyK]

The more that I understand and rely only the tooling that I can create in Splunk:
- saved searches
- alerts
- reports
- dashboards
- 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

1. automatically populate the SCM tool
2. Deploy those things to Splunk as a shared object, ideally such that they run under some system type ID (rather than my ID, as the creator)

[gabriel_vasseur]

You might like https://splunkbase.splunk.com/app/6895 to track changes to your knowledge objects. It's no effort, doesn't require git or anything else, and works equally well on-prem and in cloud.

[LukeMurphey]

@DalJeanis: which of the following was your intent:

1. create the changes within a live instance of Splunk and then log those changes in source control
2. making the changes directly in a source-code repository and then deploy the changes out to your Splunk installs

[DalJeanis · Accepted solution]

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.

https://answers.splunk.com/answers/312571/best-way-to-use-git-for-source-version-control-wit.html

[MonkeyK]

Sorry, my initial search must have been way off. Thanks for pointing me in the right direction.

[gjanders]

You may also be interested in https://answers.splunk.com/answers/484716/is-anyone-using-cicd-to-deploy-splunk-apps.html