zez3

I was reading this https://www.elastic.co/blog/using-parallel-logstash-pipelines-to-improve-persistent-queue-performance I see that there is an issue(“To put this another way, a single pipeline can only drive the disk with a single thread. This is...

I would also add one more issue. After filling up the PQ file LS should check if the ES cluster is in read-only state and stop outputting to that cluster....

3 years without any advance, wow If somebody finds some time to do this I can help with the InsightVM/Nexpose on our prod env

btw. the R7 InsideVM API provides json formatted exports.

Hi there, now would be a good time to merge those PS's

btw. it's also valid for clusters with no authentication. @TomRitserveldt

I'm on 7.15 and still see this

This sounds very familiar to the issue that I had in https://github.com/elastic/elastic-agent/issues/127 Which hopefully will be fixed in V2 https://github.com/elastic/elastic-agent/issues/189

Running 8.4.2 now and the issue still persists ps aux | grep 'Z' USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 445286 0.0 0.0 0 0...

All of my linux hosts where my Agents are running present the same behavior