LogstashKafkaConsumerLag alert was firing since ~6h this EU morning, upon investigation from https://grafana.wikimedia.org/d/000000561/logstash I noticed logstash1032 wasn't consuming messages; turns out apache2 process was stuck on CPU (on futexes) and there was no CPU left for logstash/elasticsearch. I wanted to capture a backtrace with symbols, unfortunately installing apache2-bin-dbgsym also restarted apache2, so the problem went away.
Filing a task for tracking purposes, however I don't think we run into this bug very often (i.e. will be hard to reproduce)