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!

Data Outage Monitoring and Reporting

We’ve all been there, right? Living our best life, working on our Splunk environment, when out of nowhere a ...

Manage Datasets and Connections in Catalog on Splunk Cloud Platform

Set Up Data Where You Use It Catalog already helps teams find and understand data across Splunk indexes, ...

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 ...