Hi,
we have a pretty old ELK-stack (5.5) and since a few weeks our Logstash CPU usage is through the roof. Is there a way to check which pipeline or grok pattern is causing that?
I think 5.5 had monitoring, but you're right, it's old. If monitoring was configured to send the stats to Elastic (or a monitoring stack) before problems occur, then you have "before" history. If not, this might help Node Stats API | Logstash Reference [5.5] | Elastic
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.