Deployment Architecture

Deployment Monitor best practices

mundus
Path Finder

I'm getting some weird behavior with the Deployment monitor app. I've got two servers in our DMZ that act receive data from forwarders at another data center.

When I look at the "All Forwarders" tab, it shows one of the DMZ hosts twice, but not the other one. When I do a check from the command line from a host in the remote data center, it shows that forwarding is working properly.

So, my question is, why is one host showing up twice and not the other? I've confirmed that they have different hostnames defined in inputs.conf and server.conf. The other question is, do I need to run the Deployment Monitor on all forwarders? If not, then why can I only see the two forwarders that are forwarding directly to the central server and not any of the 3rd tier servers?

Thx.

Craig

0 Karma

araitz
Splunk Employee
Splunk Employee

This is pretty strange behavior, and I don't think I can diagnose it without taking a look at your enviroment. Can you please open a support case?

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

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...