Splunk ITSI

Source Monitoring

kanyewestnewmer
New Member

Splunk developers should have access to native source control that includes versioning, effect analysis, and rollbacks to previously stable versions.

Labels (1)
Tags (1)
0 Karma

eddieddieddie
Path Finder

There are some tools that sort of let you do this - including capturing the Splunk configuration changes (all the conf files) into GIT. Here is an old, but still insightful, video from a Splunk Conference some years ago: https://www.youtube.com/watch?v=-NIME9XRqlo

0 Karma

ITWhisperer
SplunkTrust
SplunkTrust

What is the question here? If you are proposing a new idea, please submit it to the Ideas section https://ideas.splunk.com/

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Automating Threat Operations and Threat Hunting with Recorded Future

    Automating Threat Operations and Threat Hunting with Recorded Future June 29, 2026 | Register   Is your ...

Keep the Learning Going with the New Best of .conf Hub

Hello Splunkers, With .conf26 getting closer, there’s already a lot of excitement building around this year’s ...

Splunk Community Badges!

  Hey everyone! Ready to earn some serious bragging rights in the community? Along with our existing badges ...