Description

Audit profiles store information into a database. This video shows how to display that information and what information is stored.

Video recorded using: Ignition 8.0

Transcript

(open in window)

[00:00] With an audit profile configured, audit events can be viewed a various ways. First, audit events can be viewed through the gateway's web interface by going to the configure tab. Then under security, we select auditing to bring up the list of all audit profiles configured on your gateway. To view audit events for any profile, we simply go to more and select view log. What we see here is a list of all the audit events recorded by this audit profile. This interface allows users to filter events by event actor, action, and target. Users can also filter for events in a desired date range using the start and end date filters here. As an example, if I type report in the target field and press search, we see that all events with a report target are returned. Now that we have seen how to view our profile events in the gateway, let's go to our designer. Audit profile data can also be viewed through the designer's database query browser. To do this, simply go to tools and click on database query browser.

[01:09] Once the database query browser is open, we can see that there's an audit events database table present. This database table is where all audit events are stored. As any regular database table, it can be queried as such, so running this query should return all the events associated with this auto profile. To view auto profile data from a vision window, we simply create a new window and we drag in a power table from our vision component palette. We then bind the power table's data property to a SQL query that returns all the information in the audit event's SQL table. After doing so, we see that our power table now displays all the data in our audit profile. To view audit profile data from a perspective view, we simply create a new view and drag in a table from our prospective component pallet. We then bind the table's data property to a name query that returns all the information in the audit event's SQL table. After doing so, we see that our table now displays all the data in our audit profile.

You are editing this transcript.

Make any corrections to improve this transcript. We'll review any changes before posting them.

close

Share this video