Open elasticmachine opened 7 years ago
Original comment by @jsvd:
I think the main cause for this is that we aligned the modules settings with beats' modules, and the x-pack settings with x-pack settings on other products.
Original comment by @robbavey:
cc @acchen97 @andrewvc
Original comment by @andrewvc:
Hmmm, this is the sort of thing that's really hard to align. Your thoughts @acchen97 ?
I'm not sure what matters more, internal consistency, or consistency between families of products.
Original comment by @ycombinator:
Related question on discuss: https://discuss.elastic.co/t/configuring-both-x-pack-monitoring-and-x-pack-management-with-tls-for-logstash/126045
My PEM certificate does not contain the hostname. Is there a way for Logstash/X-Pack not to do full hostname verification for Monitoring and Centralized Pipeline Management? It is weird that Elasticsearch and Kibana are able to do that, but not Logstash.
Something to add here is that as an example var.elasticsearch.ssl.certificate_authority
has strict
/disable
values, while xpack.monitoring.elasticsearch.ssl.verification_mode
has none, certificate, and full
and from https://www.elastic.co/guide/en/logstash/current/plugins-outputs-elasticsearch.html#plugins-outputs-elasticsearch-ssl_certificate_verification it is a boolean type.
Might be a good idea to unify the criteria for this.
Original comment by @robbavey:
The settings for elasticsearch properties for modules and metrics/configuration management is inconsistent, particularly with regard to how security is handled: