splunk-monitoring-console-setup

Automate Splunk Monitoring Console configuration by rendering local app.conf and distsearch.conf assets, running preflight checks, and applying validated changes. This workflow supports distributed deployments with guided peer onboarding and status validation.

Render Splunk Monitoring Console assets like local app.conf and distsearch.conf first, then run preflight checks to validate inputs. This safe apply workflow provides reviewable, auditable outputs and avoids secret leakage before you commit changes.

Yes, you can onboard search peers for Forwarder monitoring using guided prompts like add-search-peers.sh. The workflow integrates peer onboarding into the apply step to ensure platform alerts and monitoring are configured correctly.

Yes, the Splunk Monitoring Console setup workflow supports both standalone and distributed deployments. It renders necessary configurations and runs status checks to validate configuration integrity across either deployment mode.

Check Splunk Monitoring Console configuration integrity by running status.sh against the rendered artifacts. This validation step confirms that your platform alerts and Forwarder monitoring configurations were applied successfully.