I already tried to configure an INPUT of the CEF UDP type, but the logs do not appear!!
When I configure the input with SYSLOG UDP they appear but without the parser.
Do you have any idea why CEF UDP doesn’t work?
Not sure how you configure that input BUT you should have seen something on CEF UDP since the logs that are shipped are in CEF. Curious when you had CEF UDP input configured and did not see logs appear, by chance did you try a tcpdump on Graylog? This should have shown more info on what was happing.
Not sure, we would nee to see more info on what your seeing. Right now Im take a guess.
Check if ports are correct on INPUT ( Input port config match the senders port)
If a firewall is in enabled insure the CEF UDP port is opened.
Check configuration on CEF UDP are correct.
Use a different CEF input.
I’m just guessing at this point. Don’t have any clue how you configured your setup.
Firewall rules are ok! The logs are arriving on UDP port 5555 and I see the requests in tcpdump!
I configured the entry for RAW/PlainText UDP on port 5555 and the logs are being seen in the graylog, but without parser.
You could try a extractor on the input but I’m not sure that would help. I can modify and create but as far as removing parts of the logs being sent and modify before the INPUT , I have not done that. I have had to adjust how logs were sent to correspond to the input used.
Maybe if @tmacgbay is around he may have an idea using a pipeline.
What doesn’t seam right is that why CEF Input is there because the type of log message is being sent. I looked in GitHub and seen other issues with CEF input. But that was for older versions of GL.
I am using a Syslog-TCP-Input with this pipeline-rule:
rule "Sentinelone Process CEF"
contains(to_string($message.message), "CEF:0", true)
let result = regex(("(CEF:.*)$"),to_string($message.message));