Deployment Architecture

Any Ideas--Ensure metadata, tstats, lookups, and deployment server are in sync

nahfam
Path Finder

Hey all,

We have hit-and-miss identification of servers that fall off of Splunk monitoring. There needs to be a critical alert if a non-decommissioned server:

1.Stops reporting to Splunk, or
2.Stops phoning home to the deployment server

Is there a weay to query the rest api from the search head to determind Deployment server contact?

Any help is much apprreciated..

Tags (1)
0 Karma

darrenfuller
Contributor

If your deployment server is forwarding its internal logs to your indexing layer, you should be able to use a query like:

index=_internal host="Your_deployment_server_hostname" "/services/broker/phonehome/"
| stats max(_time) AS last_checkin_epoch by clientip
| eval now_epoch=now()
| eval time_since_last_checkin=now_epoch-last_checkin_epoch
| sort - time_since_last_checkin

./DF

Get Updates on the Splunk Community!

Data Management Digest – December 2025

Welcome to the December edition of Data Management Digest! As we continue our journey of data innovation, the ...

Index This | What is broken 80% of the time by February?

December 2025 Edition   Hayyy Splunk Education Enthusiasts and the Eternally Curious!    We’re back with this ...

Unlock Faster Time-to-Value on Edge and Ingest Processor with New SPL2 Pipeline ...

Hello Splunk Community,   We're thrilled to share an exciting update that will help you manage your data more ...