Deployment Architecture

Deployment clients logging

Starlette
Contributor

Is the component in _internal dropped for the deployment clients connects ( component DeploymenServer) ?

I believe that to get the client you could use :

index=_internal source=splunkd.log component="DeploymentServer" | dedup hostname | table hostname

Tags (1)
0 Karma

sowings
Splunk Employee
Splunk Employee

The clients themselves will log events as DeploymentClient (typically when the server has issued splunk reload deploy-server to update the class definitions. It will also log DeployedApplication when the client has downloaded and installed a new app.

The server will log PackageDownloadRestHandler messages in splunkd.log (including the IP of the client) when a client downloads an application. The server also logs client connections (even when no apps are being deployed) in splunkd_access.log, with the 'phonehome' keyword. Information about the client is logged here, such as its IP, server name (as defined in server.conf), etc.

Starlette
Contributor

yeah, or is ariving at the deploymentbox, i can control them now but was focus on the component deploymentserver which is gone in splunk.d log

0 Karma

sowings
Splunk Employee
Splunk Employee

Components are gone? Perhaps I misunderstood the nature of your question? What exactly are you trying to figure out? Whether an individual client has connected?

0 Karma

Starlette
Contributor

cool, indeed it looks like the components are gone,,,,guess time for a deployment config monitor?

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!

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 ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Note: This post outlines a proposed architecture and serves as an interest check. If we secure commitments ...