Hi @jsoriano, thank you for your answer ( and the greetings ) .
I try to give some context:
We automate the installation of filebeat, using rpm and deb packages, while deploying our software.
Some of this servers have filebeat already installed (also different major version) sending data to another elastic server and we do not want to interfere with it.
In order to prevent any issues we would like "our" filebeat to use the same deploy strategy we already have but change the binary name from
/usr/share/filebeat/ to something like
/usr/share/filebeat-our-product-name and do the same with the service name (same for registry and conf file).
In this way we would have 2 different filebeat binary working in parallel on the same machine. The already installed filebeat MUST not change or be even stopped, while we have full control of "our" filebeat.
I have tried to use the
mage package command but it seems not to create the service when installed (Did I do somenthing wrong?).
I have no problem to change the source code (I tried to change the env var
BEAN_NAME but it seems to be used for paths tto and it do not work).
I can evaluate any option but having the "custom rpm and deb packages means we do not need to make any change to our source code. It will save us a lot of time!!