You can help by commenting or suggesting your edit directly into the transcript. We'll review any changes before posting them. All comments are completely anonymous. For any comments that need a reply, consider emailing firstname.lastname@example.org.
We are experiencing playback issues from our video hosting provider. Please check back shortly.
1:28Creating an Audit Profile
2:19View Audit Information
1:12Alarm Notification Auditing
Take topic challenge
Learn how an Audit Profile can record configuration changes and user actions made at the Gateway level.
Video recorded using: Ignition 8.0
Transcript(open in window)
[00:00] In a previous video, we showed how an audit profile can be configured to log events for specific projects. An ignition gateway can also be pointed to an audit profile to keep an audit trail of gateway specific events. An audit profile auditing a gateway will track things like database connection creation, device connection creation, module restarts, just to name a few. To configure a gateway to be audited, we must first go to the Gateway Web Interface like we have here. We then go to the Configure tab. Then we go over to System, Gateway Settings. Once we're on the Gateway Settings window, we scroll down to the Gateway Audit Profile Setting. Here, we must specify the name of the audit profile that gateway-scoped actions will log to. We have a single audit profile configured on this gateway named Audit One, so I will type Audit One, then scroll down to the bottom and save my changes. Now that my gateway is being audited, let's call some events to be logged so we can see how it works.
[01:08] First, I will delete a device connection by going to Device Connections from the gateway's Configure page and simply deleting the device. Once the connection is deleted, let's view our Audit Profile Data from the gateway. We go to Security, Auditing, we click More for our Audit One profile, then View Log to bring up our Audit Profiles data. Here, we can see the logged event for my device deletion. Restarting an ignition module will also cause an event to be logged. We can verify this by going to Modules, then restarting any module. Going back to our Audit Profiles View Log, we can see the module restart was logged by the audit profile as expected.