Technical Tip: Setup Automation stitch to monitor an IP address and trigger email alerts

[achu]

Description	This article describes creating an automation stitch to send an email alert to the admin if FortiGate is unable to reach an IP address that is being checked by link monitoring.
Scope	FortiOS.
Solution	Configure the link monitor to check the reachability of the endpoint/server: config system link-monitor     edit "server_10.50.5.19"         set server "10.50.5.19"  <--- Private/public IP address to monitor.         set interval 1000         set protocol ping         set update-static-route disable         set update-policy-route disable     next end Create an Automation trigger. Go to Security Fabric -> Automation -> Trigger -> Create New -> Configure the following parameters: Event: Link monitor status warning. Field filter 1: msg. Value 1: Link Monitor changed state from alive to dead, protocol: ping. Field filter 2: name. Value 2: server_10.50.5.19. Create an Automation Stitch to bind the trigger and action. Go to Security Fabric -> Automation -> Stitch -> Create New. If the destination IP address is not reachable, the automation stitch trigger count increases. If the automation stitch is triggered, it can be viewed in the Log and report -> System events. To verify the link monitor status when the destination is not reachable, the status is set to dead: diagnose sys link-monitor status Link Monitor: server_10.50.5.19, Status: dead, Server num(1), cfg_version=0 HA state: local(dead), shared(dead) Flags=0x1 init, Create time: Tue Nov 11 19:21:19 2025 VRF: 0 Interval: 1000 ms Service-detect: disable Diffservcode: 000000 Class-ID: 0 Transport-Group: 0 Class-ID: 0   Peer: 10.50.5.19(10.50.5.19)         protocol: ping, state: dead                 Packet lost: 100.000%                 MOS: 4.350                 Number of out-of-sequence packets: 0                 Recovery times(0/5) Fail Times(1/5)                 Packet sent: 1299, received: 467, Sequence(sent/rcvd/exp):1300/749/750