The configuration in this example makes use of the System module, available for both Filebeat and Metricbeat. Logstash makes the most sense for proxying when there are many Beats. This setup is not suitable in simple scenarios when there is only one or a couple of Beats in use. Rather than configure each Beat to send its data directly to Elasticsearch Service, you can use Logstash to proxy this traffic through one firewall exception or rule. It’s common to have many Beats dispersed across a network, each installed close to the data that it monitors, and each Beat individually communicating with an Elasticsearch Service deployment. This proxying reduces the firewall exceptions or rules necessary for Beats to communicate with Elasticsearch Service. Logstash then acts as a proxy through your firewall to send the Beats data to Elasticsearch Service, as shown in the following diagram: You can send multiple instances of Beats data through your local network’s demilitarized zone (DMZ) to Logstash.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |