...
The following table shows the DNS configuration and the role each machine plays in the cluster.
| IP | | Role |
|---|
| wifimon-node1.example.org |
10.0.0.1 | | master-eligible / data node |
| wifimon-node2.example.org |
10.0.0.2 | master-eligible / data node |
| wifimon-node3.example.org |
10.0.0.3 | master-eligible / data node |
| wifimon-kibana.example.org |
10.0.0.4 | coordinating node |
| wifimon-logstash.example.org |
10.0.0.5 | Cluster node is considered to be the one that joins the cluster. In this setup, cluster nodes are the master-eligible/data nodes and the coordinating node. The pipeline node is not, it doesn’t join the cluster.
...
| Code Block |
|---|
|
instances:
- name: node1
dns: wifimon-node1.example.org
ip: 10.0.0.1
- name: node2
dns: wifimon-node2.example.org
ip: 10.0.0.2
- name: node3
dns: wifimon-node3.example.org
ip: 10.0.0.3
- name: kibana
dns: wifimon-kibana.example.org
ip: 10.0.0.4
- name: logstash
dns: wifimon-logstash.example.org
- name: filebeat |
...
| Note |
|---|
|
If you get in the Logstash logs the following warning: [2020-07-22T13:09:07,993][WARN ][logstash.outputs.elasticsearchmonitoring][.monitoring-logstash] ** WARNING ** Detected UNSAFE options in elasticsearch output configuration!
** WARNING ** You have enabled encryption but DISABLED certificate verification.
** WARNING ** To make sure your data is secure change :ssl_certificate_verification to true [2020-07-22T13:09:07,993][WARN ][logstash.outputs.elasticsearchmonitoring][.monitoring-logstash] ** WARNING ** Detected UNSAFE options in elasticsearch output configuration!
** WARNING ** You have enabled encryption but DISABLED certificate verification.
** WARNING ** To make sure your data is secure change :ssl_certificate_verification to true
just ignore it. According to https://github.com/elastic/logstash/issues/10352 it's about a false warning. |
...
