FortiGate
FortiGate Next Generation Firewall utilizes purpose-built security processors and threat intelligence security services from FortiGuard labs to deliver top-rated protection and high performance, including encrypted traffic.
gpap_FTNT
Staff
Staff
Article Id 213521
Description The article describes how to test an automation stitch configured for event log.
Scope

FortiGate.

Solution

When an automation-stich is configured for event log, in GUI the test is grey and not able to be used.

 

event-log.PNG

For example for a stich that check the interface status, there is:

 

# config system automation-trigger
    edit "interface"
    set event-type event-log
    set logid 20099 <----- Log ID for interface status.

 

In order to test this stich we use the CLI command:

 

# diagnose automation test[stich] 

 

After the automation trigger name CLI prompts for:

 

"arg please input args"

 

There, it is necessary to add the log. In this case the test should be done as:

 

# diagnose automation test interface "date=2022-05-24 time=12:29:26 eventtime=1653388166478984429 tz="+0200" logid=\"0100020099\" type=\"event\" subtype=\"system\" level=\"warning\" vd=\"root\" logdesc=\"Interface status changed\" action=\"interface-stat-change\" status=\"UP\" msg=\"Link monitor: Interface dmz was turned up\"

 

Results:

 

automation test is done. stitch:interface

Contributors