
The only troubleshooting that can be done is for the non-compiled normalisers, as you can check the log messages against the patterns for those. But the compiled normalisers are as the name implies “compiled”, so their signatures are not visible outside of our source code.
I have just checked the Support tickets, and there does seem to be something going on with the Palo Alto logs in version 10.1, apparently the field count doesn’t match what we are expecting for THREAT and TRAFFIC logs. I suspect that Palo Alto threw in a few additional fields without telling anyone :)
I can see in the tickets that we have built some new normaliser versions over the last week or two, so it’s probably best to open a ticket and point out that you have problems with PanOS 10 - Support can decide what new package to share with you, rather than me picking one randomly from the Support ticket I see.
9 comments