Hi all, I am currently planning and preparing the monitoring of a platform with Docker Swarm Clusters running on underlying Linux and Windows hosts. Collecting the docker logs seems straightforward, either with the Splunk logging driver sending it to the HEC or monitoring the logs with an UF on the host. (Please correct me if I'm wrong) For the docker metrics, I can use some help on the approach to collect this. I found the Splunk app for Infrastructure supports Docker monitoring but only for standalone Linux hosts or for Kubernetes or Openshift, but not for Docker Swarm. Does anyone know why this is not supporting Docker Swarm? Will this be added in a future release? I found the following solutions to get the Splunk metrics in to Splunk: This Splunk conference topic that looks interesting, but seems never fully productized (Why not?) https://conf.splunk.com/files/2017/slides/monitoring-docker-containers-with-splunk.pdf The only fully working solution looks like this third-party solution: https://splunkbase.splunk.com/app/3723/ Then there is also the simple variant that is not advised for Docker Swarm clusters: https://splunkbase.splunk.com/app/4468/ Any advice on which path I should go for collecting the docker stats with Splunk? Thanks for you help!
... View more
Hi all, Because we have Splunk running in multiple security environments, we have two separate indexer clusters. For some data we need to send data to either both or only one of the indexer clusters. We do this on the HF by setting the _TCP_ROUTING key with props.conf & transforms.conf as described in https://docs.splunk.com/Documentation/Splunk/8.0.6/Forwarding/Routeandfilterdatad. Or by directly setting the _TCP_ROUTING with inputs.conf on the UF. In outputs.conf we configure the two different destinations as in the example below. We see that in all Splunkdoc examples that different ports are used for different destinations. Is this required for Splunk to function as intended? Or is this only best practice? When do you need to use a different port then 9997 in outputs.conf and when not? This is not clear from the documentation... Please advice, thanks! [tcpout]
... View more