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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...