Getting Data In

Deployment Monitor - scheduled searches necessary?

sc0tt
Builder

I've seen other questions regarding the number of scheduled searches by Deployment Monitor to cause the maximum number of historical searches warning. Currently, there are about 25 searches that are scheduled to run every 30min/1hr. Can I just unschedule these? Are any of these scheduled searches actually necessary for the app or is it better to offset them at different times?

jakesony
Explorer

I would also appreciate a better understanding of these scheduled searches and how many are really necessary. These are always among the most frequently running and expensive searches in my installation.

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

Catalog Is Now Generally Available on Splunk Cloud Platform

A Unified View of Your Data  Security logs, application events, business data, and historical telemetry often ...

Your Path to AgenticOps: AI Experiences for Every Splunk Practitioner

Your Path to AgenticOps: AI Experiences for Every Splunk Practitioner   Watch on demand us for a demo-driven ...