This forum is for all security enthusiasts to discuss Fortinet's latest & evolving technologies and to connect & network with peers in the cybersecurity hemisphere. Share and learn on a broad range of topics like best practices, use cases, integrations and more. For support specific questions/resources, please visit the Support Forum or the Knowledge Base.
I've a problem with creating a custom parser.
I've added the Device, created a Custom Event, added a simple parser (with Recognizer etc) and a test log message.
The XML validates ok, but when I use the Test button, I get an "Errors" message (but no other details).
My parser is listed under the 'Parser Used' column.
I cloned some other existing parsers (such as CiscoSEParser) and tried the test function there.
They also fails with "Errors"
Why do clones of 'production' parsers fail the Test ?
thanks,
Solved! Go to Solution.
Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
If is based on another parser you must disable it before clone it, in the error message sometimes you will see that the error is because another parser is handling the test message. I'm attaching a quick document that you can use as a reference, however, keep in mind that the parser used in that example is already fixed on 4.10.
In Reply to Morgan Doyle:
I've a problem with creating a custom parser.
I've added the Device, created a Custom Event, added a simple parser (with Recognizer etc) and a test log message.
The XML validates ok, but when I use the Test button, I get an "Errors" message (but no other details).
My parser is listed under the 'Parser Used' column.
I cloned some other existing parsers (such as CiscoSEParser) and tried the test function there.
They also fails with "Errors"
Why do clones of 'production' parsers fail the Test ?
thanks,
-
Rolando Antón
Hello,
to pass the test, you also need an appropriate syslog message to test the custom parser against.
Sincerely
Harald
If is based on another parser you must disable it before clone it, in the error message sometimes you will see that the error is because another parser is handling the test message. I'm attaching a quick document that you can use as a reference, however, keep in mind that the parser used in that example is already fixed on 4.10.
In Reply to Morgan Doyle:
I've a problem with creating a custom parser.
I've added the Device, created a Custom Event, added a simple parser (with Recognizer etc) and a test log message.
The XML validates ok, but when I use the Test button, I get an "Errors" message (but no other details).
My parser is listed under the 'Parser Used' column.
I cloned some other existing parsers (such as CiscoSEParser) and tried the test function there.
They also fails with "Errors"
Why do clones of 'production' parsers fail the Test ?
thanks,
-
Rolando Antón
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.