Getting Data In

Why does excludeFromUpdate not work in serverclass.conf?

schose
Builder

Hi all,

I'm managing my apps deployed through forwarder management using git. When running a scheduled "git pull" the file, .git/FETCH_HEAD is always newly created.
When running a splunk reload deploy-server, the app is always sent out to the clients and Splunk will be restarted.

To avoid this, I'm trying to use the excludeFromUpdate introduced in Splunk v6.2 but neither

[serverClass:splunkdebug:app:myapp]
restartSplunkd = 1
stateOnClient = enabled
excludeFromUpdate=myapp/.git

nor

[default]
excludeFromUpdate=$app_root$/.git

seems to work.

Any hints?

Cheers,

Andreas

1 Solution

hexx
Splunk Employee
Splunk Employee

What version are your deployment clients running? This particular setting requires both the deployment server and its deployment clients to be running Splunk Enterprise 6.2 or higher.

View solution in original post

hexx
Splunk Employee
Splunk Employee

What version are your deployment clients running? This particular setting requires both the deployment server and its deployment clients to be running Splunk Enterprise 6.2 or higher.

schose
Builder

You're right. 🙂

0 Karma

hexx
Splunk Employee
Splunk Employee

Oh good, let me convert my comment to an answer then.

0 Karma

schose
Builder

As hexx answered correctly you also need a v6.2 or higer client.

Workaround for everyone having the same issue with the older clients using git: it's save enough to delete the .git//FETCH_HEAD everytime after git pull.

Regards,

Andreas

Get Updates on the Splunk Community!

App Platform's 2025 Year in Review: A Year of Innovation, Growth, and Community

As we step into 2026, it’s the perfect moment to reflect on what an extraordinary year 2025 was for the Splunk ...

Operationalizing Entity Risk Score with Enterprise Security 8.3+

Overview Enterprise Security 8.3 introduces a powerful new feature called “Entity Risk Scoring” (ERS) for ...

Unlock Database Monitoring with Splunk Observability Cloud

  In today’s fast-paced digital landscape, even minor database slowdowns can disrupt user experiences and ...