I will open the New Feature ticket no problem. They changed the x-pack on friday without changing the version number and no notification whatsoever. My testing env changed the kibana a little bit adding the Machine Learning tab. if you testing ROR/KBN with the monitoring on the older version of x-pack pre 9th of June, it is working perfectly as we checked that on our old env (we are migrating from 3 nodes to 15 nodes env).
The problem is that they added ML to x-pack in alpha stage and monitoring has nothing to do with the hung env. I did the stacktrace and found the problem and reported it the ES people. The problem only exist in env with systemd. I am testing their workaround at the moment.
We had a talk in the team regarding if we want to rely on x-pack for monitoring and if there was an alternative the answer is “definitely NO”.
Anyway, thnks again
PS: ROR 1.16.5-pre1 has this error:
[CLUSTERWIDE SETTINGS] index settings not found, have you installed ReadonlyREST Kibana plugin? Will keep on using elasticearch.yml. Learn more at https://readonlyrest.com
I got back to ROR 1.16.4 with KBN 0.1.5 and it is working perfectly with the x-pack