Troubleshooting Tip: How is the Automation Stitch 'Configuration Change' triggered (2024)

Description
This article provides some details about which event log is triggering the 'Configuration Change' event found in automation stitch.

Useful links:

Fortinet Documentation
Automation stitches: https://docs.fortinet.com/document/fortigate/6.0.6/handbook/712138/automation-stitches

Solution

The stitch is triggered by the event that is created when an admin made configuration changes to the FortiGate and logs out of the device.

The log id that triggers this stitch is 0100032102.


Events with this ID can be found by applying a filter with Log ID 0100032102 under Events in Log & Reports section of the FortiGate.
Testing the stitch will trigger an event with the same logid.


Message:
'Configuration is changed in the admin session'

'Automation Stitch Test: Configuration is changed in the admin session'

Troubleshooting Tip: How is the Automation Stitch 'Configuration Change' triggered (1)

Troubleshooting Tip: How is the Automation Stitch 'Configuration Change' triggered (2024)
Top Articles
Latest Posts
Article information

Author: Rubie Ullrich

Last Updated:

Views: 6323

Rating: 4.1 / 5 (52 voted)

Reviews: 83% of readers found this page helpful

Author information

Name: Rubie Ullrich

Birthday: 1998-02-02

Address: 743 Stoltenberg Center, Genovevaville, NJ 59925-3119

Phone: +2202978377583

Job: Administration Engineer

Hobby: Surfing, Sailing, Listening to music, Web surfing, Kitesurfing, Geocaching, Backpacking

Introduction: My name is Rubie Ullrich, I am a enthusiastic, perfect, tender, vivacious, talented, famous, delightful person who loves writing and wants to share my knowledge and understanding with you.