I am currently in use of ELK cluster based on version 7.3.1 under Kubernetes environment. I also use Jolokia module inside metricbeat in order to gather many metrics. I wander does anyone can help me regarding Jolokia auto-discovery problem I have in recent versions.
Description: In past I used Kubernetes autodiscovery together with Jolokia module in order to detect changes in Kubernetes cluster (new services, removal of old services... in order to get required jmx metrics from them). This combination worked perfectly until version 7.3.1 Now there are often missing references inside metricbeat when Jolokia looses reference on deleted services. Data are still incoming but lost reference accumulate over time. New services are detected without problems by Jolokia. Problem persist only when service is deleted from Kubernetes cluster.
I am aware that Jolokia module has it own auto-discovery now. Can someone give me a clue how to configure Jolokia auto discovery parameters (name - interface name, grace period, probe timeout) but in case metricbeat runs inside Kubernetes cluster with services that exposes metrics via Jolokia. Thanks in advance