Debian Policy compliance

[jlecour]

Hi,

I've been integrating the current ELK packages (ES 2.3, Kibana 4.5 and Logstash 2.3) in a Debian environment (7 and 8).

Contrary to Elasticsearch, the Kibana and Logstash Debian packages provided by Elastic are not very compliant with the Debian packages guidelines.

Both Kibana and Logstash are installed in /opt and not in /var/lib like it should be

Also, the log directory /var/log/kibana/ is not created at install time, but at launch time. I guess it's wise to check for the existence of the specified log directory at launch, in case the config has been modified, but creating the default directory at install time seems important if you want to have a proper/verifiable install without having to launch the service.

Finally, the configuration should go to /etc/kibana instead of /opt/kibana/config.

Let me finish by a big thank you to all the contributors of the ELK products. Your work is really appreciated.
A lot of progress has been done to improve integration with various distributions. I'm pointing this issue to help improving the experience.

[jlecour]

Here are some links to the Debian Policy :

• regarding configuration files : https://www.debian.org/doc/debian-policy/ch-files.html#s10.7
• regarding log files : https://www.debian.org/doc/debian-policy/ch-files.html#s10.8

I'll add specific links when I find them ;)

[jlecour]

In the same issue for Logstash, @suyograo pointed to this layout for Logstash v5 : https://www.elastic.co/guide/en/logstash/5.0/dir-layout.html

Is there a similar effort on the way for Kibana ?

[markwalkom]

Thanks for raising this, we have this issue to track the work you have highlighted #7275