Did someone come up with a python/bash script to find the slowest/longest extractor in your Graylog instance? I’m dealing with stuck threads and my best bet is a badly-written extractor but searching trough all of them would be a real pain.
It is not quite what you asked for, but this could help regardless.
We have a new feature in 3.2 (if you already upgraded) where you can dump the content of your process buffer (reacable from a node):
With that you see the message a processor is working on right now. From the message it should be hopfully easy to see which extractor is beeing used.
Wow, this looks great ! I will wait a bit before upgrading to 3.2 in production but features like that are awesome.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.