GCP Cloud Audit Activeboard

Purpose

This Activeboard summarizes information about the most relevant fields contained in GPC Cloud Audit log entries related to GCP Services audited API calls for a selected period of time. It allows you to filter by main log entry fields (Resource Type, Project ID, Service Name, Principal - entity issuing API calls - and Caller IP). The Activeboard is divided into four sections:

Overview
Errors
Data by Main Categories
Data Tables

Open Cloud Audit Activeboard

Once you have installed the application, you can access the Activeboard in the following ways:

Go to Exchange in the navigation pane and look for the Activeboard to open it. Click Open.

Go to Activeboards in the navigation pane and use the filter to open the Activeboard you downloaded.

Know more about Activeboards

Refer to Manage and filter Activeboards article to know how to work with Activeboards.

Exploring the Activeboard

When opening the GCP Cloud Audit Activeboard, the information displays in 4 different sections:

1. Overview

Total number of log entries.
Top 3 locations where resources for which API calls have been issued reside.
Percentage of log entries by type (Admin Activity, Data Access, System Events, Policy Denied).
Percentage of log entries by severity (Default, Debug, Info, Notice, Warning, Error, Critical, Alert, Emergency).
Evolution over time of the number of log entries by a type/severity combination.
A map locating API calls by CallerIP geo position and the total number of API calls registered for each CallerIP.
Top 5 most active public IPv4 CallerIP’s.

2. Errors

Total number of log entries registering unsuccessful API calls.
Percentage of errors vs total number of log entries.
Percentage of errors by GCP Cloud Audit error code (mapping between numeric code and its corresponding description implemented for the sake of error interpretation).
Evolution over time of unsuccessful API calls by error type.

3. Data by Main Categories

A column and a line chart showing Top 5 total number of log entries and their evolution over time, respectively, for the most relevant log entries fields (Resource Type, ProjectID, Service Name, and Method Name).

4. Data Table

A table for log entries grouped by Resource Type, ProjectID, Service Name, Principal, CallerIP, and Error Type.

Load data takes too long

Sometimes some widgets take time to upload the data, it is possible to speed up the process by creating aggregation tasks. Refer to Aggregation tasks article to learn how to do it.