Inconsistent package installation docs between Kibana and Elasticsearch

[tbragin]

I’ve been installing the Elastic Stack a bunch of times lately from various packages, and I noticed that the Kibana RPM install docs are somewhat incomplete compared to Elasticsearch. For instance Elasticsearch has this neat table detailing where files end up on the file system after install — very convenient… Kibana RPM install docs seem to have nothing like that.

Situation is not helped by the fact that Kibana seems to put stuff in different folders compared to ES. For me, for 5.0-alpha3, ES binaries ended up in /usr/share/elasticsearch/bin and kibana binaries in /opt/kibana/bin, configs are in different folder structures too. I'm sure there is a good reason for it, but it is all the more reason for being explicit in the docs where files end up on the file system. It appears there is a PR outstanding to address it, but listing locations will still help.

There are other inconsistencies too, for instance, ES provides more information about how to start the services depending on the distribution that the Kibana docs. I'll leave the detailed comparison to the reader.

[LeeDr]

We fixed most, if not all, of those inconsistencies in the install directories in 5.0.0 alpha4 Kibana.
The Kibana directories are now in line with Elasticsearch directories.

The config file is /etc/kibana/kibana.yml just like /etc/elasticsearch/elasticsearch.yml

Binaries are in /usr/share/kibana just like /usr/share/elasticsearch

There's nothing installed in /opt/kibana now.

But I'm sure the docs could still be improved.

[epixa]

#8821 fixed this for 5.0+