There were changes introduced in the way Deployment Server communicates to its own clients and indexers:
clients_<DS_instance_guid>.log
phonehomes_<DS_instance_guid>.log
appevents_<DS_instance_guid>.log
As a representation of a simplistic Splunk Environment in which this scenario might happen:
LM works simultaneously as an Indexer.
DS is configured to forward its logs to LM/indexer and doesn’t index them on its own.
Deployment Server has been configured to forward all its logs to the License Manager/Indexer instance, without indexing them on its own.
Upon migration from pre 9.2.0 to pos-9.2.0 these indexes weren't located in the DS itself:
clients_<DS_instance_guid>.log
phonehomes_<DS_instance_guid>.log
appevents_<DS_instance_guid>.log
In that situation DC phones home to DS okay and apps and the whole communication in the backend works okay and as it should.
The issue it's only visible in the GUI in both, Forwarder Management on the DS and LicenseManager/Indexer (LM)
Because all data about communication with the DC has been forwarded to the indexer that is the reason why the Deployment Clients appeared on a not-DS instance.
To fix:
[indexAndForward]
index = true
selectiveIndexing = true[tcpout]
forwardedindex.filter.disable = false
forwardedindex.2.whitelist = (_audit|_internal|_introspection|_telemetry|_metrics|_metrics_rollup|_configtracker)
Little temporarily behaviour as a side note:
| Revision | Publish Date | Comments |
|---|---|---|
1.0 |
29-Sep-2026
|
Initial Release |