Getting Data In

Why did Deployment client stop phoning home?

Alixfire
Loves-to-Learn

Hello,

 

We have a huge setup and UFs are managed through Deployment server, All the UFs are at far places and managed and installed by their respective asset owners. lately some random clients stops phoning home to their client. Though they are disconnected they are sending logs which explains they are not stopped or any configuration changes happened. kindly help me out understanding what is the issue and how it can be handled.

 

Thank you.

Labels (1)
0 Karma

richgalloway
SplunkTrust
SplunkTrust

That the UFs continue to send their logs is a good thing, but it doesn't mean there haven't been any configuration changes.  A change to deploymentclient.conf could stop a UF from phoning home while having no effect on logging.  Also, certain network changes might prevent some UFs from connecting to the DS while allowing connections to indexers.

---
If this reply helps you, Karma would be appreciated.
0 Karma
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!

Data Outage Monitoring and Reporting

We’ve all been there, right? Living our best life, working on our Splunk environment, when out of nowhere a ...

Manage Datasets and Connections in Catalog on Splunk Cloud Platform

Set Up Data Where You Use It Catalog already helps teams find and understand data across Splunk indexes, ...

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...