Logs! We need them, we want them, we must have them. And if you were awestruck by Google Glass during Google I/O this year, then you may not have been paying enough attention and most likely didn’t notice a big change concerning programmatic access Google Apps audit logs. Sure, this may be one of the least sexy things that you have heard come out of Google I/O, but frankly we couldn’t be more excited.
The news… Google has deprecated the Admin Audit Logs API. Specifically, the new Admin SDK includes a component called Reports API which should allow us to achieve the same ends.
We had previously covered how to access Google Apps Admin Audit logs on this blog. If you had read that post you would have noticed a bit of a complexity in retrieving logs, involving a certain “customerId” operation. The new Reports API will not require you to retrieve the customerId. This is only one of the changes, here is a summary of the rest:
- Currently, you can access 2 types of logs from this API: “admin” and “docs”. The “admin” logs correspond to the Admin Audit API logs. The “docs” logs track important events related to Google Docs in your organization, such as when users have viewed or edited a document.
- Export to CSV is not supported as part of this Reports API. This was a supported feature of the Admin Audit API.
- Reports API uses OAuth 2.0.
- The Reports API responses contain the UNIX epoch time in seconds. Meanwhile, the logs retrieved via Admin Audit API contained date/time fields in UTC.
These are some of the changes in how you are supposed to access Google logs. You can read the details here.