Right now filebeat monitoring only publishes to Elasticsearch. There is no data path via Logstash. For isolation/proxy purposes one can also setup nginx.
Thanks Steffens. Let me make sure I understand what you're suggesting. Are you saying that a workaround is to use nginx or some form of a proxy on the logstash instance(s) to forward the requests to the ES cluster?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.