Depending on your Google Workspace edition, you might have access to the security investigation tool, which has more advanced features. For example, super admins can identify, triage, and take action on security and privacy issues. Learn more
Creating an extracted data source also creates a data source export event for the data source being extracted.
For other services and activities, such as Google Drive and user activity, see the list of log events.
Note: The Looker Studio log events data source provides data for the previous 6 months. If you want to retain it for longer, you can export the log data.
Run a search for log events
Your ability to run a search depends on your Google edition, your administrative privileges, and the data source. You can run a search on all users, regardless of their Google Workspace edition.
Attribute descriptions
For this data source, you can use the following attributes when searching log event data:
Attribute | Description |
---|---|
Actor | Email address of the user who performed the action |
Actor group name |
The group name of the actor. For more information, go to Filtering results by Google Group. To add a group to your filtering groups allowlist:
|
Actor organizational unit | Organizational unit of the actor |
Asset ID | ID of the asset where the logged action happened |
Asset name | The name of the asset that was viewed or changed |
Asset type | The type of asset where the logged action happened |
Connector type | The type of connector used to fetch data for a data source asset |
Current value |
If settings are changed, this field shows the current value of the settings—for example, Can edit, Can view, Private, Public on the web, or Current team workspace ID. Note: This attribute will replace New value. |
Data export type | The type or format of the data export in Looker Studio. Enter one of the following values:
|
Date | Date and time of the event (displayed in your browser's default time zone) |
Distribution content ID | The ID of the schedule or alert |
Distribution content name | The name of the schedule or alert |
Distribution content owner email | The email address for the owner of the schedule or alert. The schedule owner is its most recent editor. The alert owner is the alert creator. |
Distribution content type | The type of content being distributed like schedule or alert |
Embedded in report ID | ID of the report where the data source is embedded |
Event | The logged event action, such as Create, Data Export, or Restore |
IP address | Internet Protocol (IP) address associated with the logged action. Usually reflects the user's physical location, but could be a proxy server or a virtual private network (VPN) address. |
New value | If settings are changed, this field shows the new value of the settings—for example, Can edit, Can view, Private, or Public on the web. |
Old value | If settings are changed, this field shows is the old value of the settings—for example, Can edit, Can view, Private, or Public on the web. |
Owner | The owner of the asset |
Parent Workspace ID | The team workspace for the asset. |
Previous Value |
If settings are changed, this field shows the previous value of the settings—for example, Can edit, Can view, Private, Public on the web, or Current team workspace ID. Note: This attribute will replace Old value. |
Prior visibility | Visibility of the Looker Studio asset before the activity |
Project ID | The Google Cloud project ID that is associated with the Gemini in Looker enablement. |
Setting name | The name of the Gemini in Looker setting. Select one of the following values:
|
Target | When changing user access, this field captures the target users or groups that this access change applies to |
Target domain | If link visibility is changed, this field captures the domains that have access to the link. For example, enter the domain for your organization if the link is shared within your domain, or enter all if the link has public access. |
Visibility | Visibility of the Looker Studio asset associated with the activity |
Note: If you gave a user a new name, you will not see query results with the user's old name. For example, if you rename OldName@example.com to NewName@example.com, you will not see results for events related to OldName@example.com.
Export Looker Studio log event data to BigQuery
If allowed, you can export Looker Studio log events data to Google BigQuery. To export, you'll need to:
Learn more about reporting logs and BigQuery.
Set up email alerts
You can easily track specific Looker Studio activities by setting up alerts. For example, get an alert whenever someone creates or deletes a report.
- Open the log events as described above in Open Looker Studio log event data.
- Click Add a filter.
- Enter or select the criteria for your filter and click Create Alert.
- Enter a name for the alert.
- (Optional) To send the alert to all super administrators, under Recipients, click Turn on.
- Enter the email addresses of alert recipients.
- Click Create.
To edit your custom alerts, go to Administrator email alerts.
Manage log event data
Take action based on search results
Manage your investigations
Supported editions for this feature: Frontline Standard and Frontline Plus; Enterprise Standard and Enterprise Plus; Education Standard and Education Plus; Enterprise Essentials Plus; Cloud Identity Premium. Compare your edition