Getting Data In

Deployment Server - Automated Client Deletion?

muebel
SplunkTrust
SplunkTrust

Our system provisioning process installs the Splunk UniversalForwarder while the system is on a provisioning network, and then moves the system to it's actual final network.

This results in two client records in the Forwarder Management web interface.

Is there a way to script out Client Deletion? I'd like to remove these duplicate client records in an automated way.

0 Karma

lguinn2
Legend

Splunk writes the info about the deployment client in serverclass.conf

It wouldn't be trivial, but you could certainly write a script that edits serverclass.conf; it is a text file.

More info here: serverclass.conf.spec and at Create Server Classes

After editing serverclass.conf, your script should issue the command

./splunk reload deploy-server

to have Splunk re-read the serverclass.conf file

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!

Accelerate Splunk App Development with AI

  Learn how to automate the repetitive parts of your build cycle.   Watch On-Demand   Replay the Accelerate ...

Splunk Agent Observability: Measuring AI Value with Splunk Tokenomics on AWS

The AI landscape is moving faster than ever, and our latest 2026 State of Observability report provides the ...

Enterprise Security Watch Party: What’s New in 8.8 - Recap

Splunk Community HQ hosted a Splunk Enterprise Security Watch Party: What’s New In ES 8.8 last Thursday. I had ...