I configured a multi-layer Deployment Server (DS) setup with the following architecture:
Main DS Management: The main DS manages its local Universal Forwarders (UFs) and acts as the parent controller for branch Intermediate Forwarders (IFs), which register as clients to the main DS.
Branch DS Configuration & Target Repository: The branch Intermediate Forwarders act as local Deployment Servers for their respective branch UFs. To manage branch UF configurations from the main DS, I configured custom targetRepositoryLocation settings on the IFs so that deployment apps pushed from the main DS land directly in the intermediate deployment apps directory (/opt/splunk/etc/deployment-apps).
Dynamic Server Class Mapping: To ensure deployed apps map to the correct server classes and target agents, I pushed an app from the main DS to the intermediate DS to handle the mapping logic.
Current Issue: Although the configuration works correctly on the backend, the main DS GUI displays an error and provides error status information.
Main deployment server issues bellow :
The branches intermediate forwarder are ok :
and verification from search head the branch universal forwarder conf work well
@gcusello The solution is to set stateOnClient = noop either under the server class related to branches or under apps. For more details about this solution, visit the threads below:"
Why is my Deployment Server showing an error pushi... - Splunk Community
the output as
For guide to how implement this design from scratch visit the link bellow:
@gcusello The solution is to set stateOnClient = noop either under the server class related to branches or under apps. For more details about this solution, visit the threads below:"
Why is my Deployment Server showing an error pushi... - Splunk Community
the output as
For guide to how implement this design from scratch visit the link bellow:
