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!

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...

Request for Professional Development: Attending .conf26

Winning Over the Boss: Your Pass to .conf26 conf26 is going to be here before you know it. If don't already ...