Troubleshoot the Google Workspace Beat

This guide provides solutions for common issues with the Google Workspace Beat.

Data Missing Issue

If the system is experiencing a data loss issue for the Google Workspace Beat, try the following:

Run the following command:

CODE

./lrctl gsbeat config export --outfile gsbeatconfig.yml

Run the following command to open the Google Workspace configuration file:

CODE

vim gsbeatconfig.yml

Increase the "delayedTimeMin:" value and save the updated configuration file.
Run the following commands:

CODE

cat gsbeatconfig.yml
./lrctl gsbeat config import

Run the following command to complete importing the updated configuration file:

CODE

rm gsbeatconfig.yml

Restart the Google Workspace Beat:

CODE

./lrctl gsbeat restart

Check the logs to see if the issue has been resolved:

CODE

./lrctl gsbeat logs

In cases where the system experiences data loss or delays in receiving login, admin, or token logs, the PubSub Beat can be used to collect and parse Google Workspace login, admin, and token logs efficiently.

Data Missing Issue

Login, Admin, and Token Logs Delayed or Missing