How to debug filebeat module, it doesn't seem to be getting syslog data

I'm trying to use the panw module receiving data via a syslog port. I've enabled the module and can see that filebeat is listening on the proper udp port. I can see traffic arrive in tcpdump and the events look valid.

I enabled debug logging in filebeat and I don't see anything that looks like an event arriving, so I don't know what else to check. Shouldn't a debug log show something when the input is received?


Hi @rugenl
Please Share Config and Logs
Do you see filebeat reporting that is is listening on UDP port?
You can also set the output to console to just eliminate variables.

  pretty: true

The filebeat log shows it starts the udp listen:

"Starting Syslog input","":"filebeat","protocol":"udp"

It would be nice if it included a port number but netstat shows that the correct port is in use by filebeat.

This filebeat is using other modules, so I can't redirect the output to console, but I switched to a simple -type: syslog, without the panw module and it will index the "raw" syslog events.

The debug log doesn't show anything about the event until it publishes it. Is there a way to turn on debugging in the module? The doc shows how to enable logging in the publisher section, but doesn't seem to list any other sections. I'm just setting logging.level: debug in filebeat.yml.


Interesting... Thoughts..

But I don't know a way to test just a module you could try logging.level: trace

If this is a unix system you could down load another filebeat.tar.gz to a temp directory and set it up and run to console / isolate.

Also you can run manually filebeat with the -d "*" to look at the output messages or -d "publisher"

so you are not seeing and failed to index event messages? (pehaps failing at the ingest pipeline) did you change anything about the pipelines?

Did you run setup after you enabled the panw modules?

Yes, I did the setup and verified the ingest pipelines are loaded. I think that is all setup does, the datastreams are setup as verified by the -type: syslog test. I'm about 90% sure filebeat isn't trying to send the events to Elastic.

They are supposedly on PANOS 10.1, I can't find any comments in the module about version support.

I'll get to more testing when I get time. Thanks

1 Like

From the panw modules doc


This module has been tested with logs generated by devices running PAN-OS versions 7.1 to 9.0 but limited compatibility is expected for earlier versions.

The ingest-geoip Elasticsearch plugin is required to run this module.

I'm hoping that is just an outdated doc reference :slight_smile: PAN-OS 9.0 went out of support March 1, 2022. I'm willing to work on "fixing" the module for the new data format if that is needed, I just can't get to a point where I can see what is failing.

I'm just the syslog catcher on this, I don't know anything about PAN-OS that I haven't Googled today :slight_smile:

Our prior ingest was done in logstash and was setup before modules and ingest pipelines were available. It was doing a csv split on the data, sending it to Elasticsearch, but was failing because some field that was mapped as an IP address was now text. The index failure was a clear message in the logstash log.

Thanks. stay tuned, I'm hoping to get back to this after chumming the daily sharks....

1 Like

Swim Safe!

Yeah we just need the error... Yes if the ingest pipeline or actuall write is failing / typically you should be able to see that in the filebeat logs.

Once we get that we should be able to figure out.

I enabled the module and set -d "*" and then just netcatted a message to the port and saw it send through to elastic I just sent "Hello World" and the pipeline did not fail etc...

Some reason thinking filebeat is not reading from the UDP or there is some other disconnect.

Well, this is embarrassing.... I'm amazed that I can read this:

The interface to listen to UDP based syslog traffic. Defaults to localhost. Set to to bind to all available interfaces.

As "Defaults to '"... I was only listening on localhost, it's working now. It looks like some "types" are still failing, I know I'm not seeing "Threat" events, probably the same mapping error.

1 Like

Cool! and Doh! right :slight_smile:

Let us know if you need help fixing the ingest pipeline but yeah probably a parsing / mapping error

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.