Hi all,
I'm doing some QA checking on an application, and I notice that the Admin section of the application has two views: Newest Updates and Newest Entries. I assume the former is for edits of existing records, and the latter for new line records in tables.
However, on review, I'm noticing that audit records are missing for edits made to the tables.
In role profiles, I have one user who creates the record, and another user who edits / updates the record. However, I can find no audit record for the editing person, despite being able to see in the table views (edited by / edited date columns I have made) that they did in fact update the records. It could, theoretically, be a user problem at this time, or could be an event logging issue - I haven't narrowed anything down yet.
I've searched the forum and found onoehring's excellent page and follow up, but this all seems to pre-date this function in the tool. ( https://forums.appgini.com/phpbb/viewto ... &start=100 )
I can't find in the change logs for Appgini when auditing was integrated into the tool in order to know when to search from for any reports of a bug or problem.
Has anyone else identified issues with the built in logging in the admin section? I can't see any variables at table or user level which might need to be toggled to enable / disable logging, so this seems like a possible bug?
I'm going to do some more controlled testing to replicate the issue, and report back if I find anything else.
Admin Function - Audit Log Gaps?
Re: Admin Function - Audit Log Gaps?
So I've done a little more testing on this today, and observed the following:
"Newest Entries" view:
- Some table inserts seem to be recorded, but Username and Group are blank in the audit view, and not storing name and role of the person who did it.
- logging is sometimes done, sometimes not. I'm not clear on why.
"Newest Updates" view:
- It doesn't write a new line for each edit. It seems to write one record for an edit, and then update that record with the new details each time
- blank username / group is also prevalent here.
When I'm seeing audits of username and group, it's typically where I've used a hook for after_insert in the table, but the audit on the original table record that triggered the after_insert is not writing username / group for the "trigger" record.
"Newest Entries" view:
- Some table inserts seem to be recorded, but Username and Group are blank in the audit view, and not storing name and role of the person who did it.
- logging is sometimes done, sometimes not. I'm not clear on why.
"Newest Updates" view:
- It doesn't write a new line for each edit. It seems to write one record for an edit, and then update that record with the new details each time
- blank username / group is also prevalent here.
When I'm seeing audits of username and group, it's typically where I've used a hook for after_insert in the table, but the audit on the original table record that triggered the after_insert is not writing username / group for the "trigger" record.
Re: Admin Function - Audit Log Gaps?
Further update: I think I understand what's happening.
The updates ARE being logged, but the usernames shown in the views are always for the CREATING user (and role) of the record, and not the audit of the EDITING person, which may be different.
So if user Alan creates a record, the view will ALWAYS show user Alan in the view. You have to look at the detail (and store the Edited By Username) of the record to see who ACTUALLY made the change.
It's less useful in terms of being able to search and parse activity by userfrom this front end view, but at least it's audited. Hopefully this info helps anyone else who may have been confused, like me.
The updates ARE being logged, but the usernames shown in the views are always for the CREATING user (and role) of the record, and not the audit of the EDITING person, which may be different.
So if user Alan creates a record, the view will ALWAYS show user Alan in the view. You have to look at the detail (and store the Edited By Username) of the record to see who ACTUALLY made the change.
It's less useful in terms of being able to search and parse activity by userfrom this front end view, but at least it's audited. Hopefully this info helps anyone else who may have been confused, like me.