Managing Datastore from the Console

This page describes how to view and manage the entities, indexes, and statistics for the data your application stores in your database. It also shows how to enable or disable Cloud Datastore Admin access, and how to enable or disable Cloud Datastore writes. You can do these activities on the Cloud Datastore page in the Google Cloud Platform Console.

Viewing Cloud Datastore statistics

Go to the Cloud Datastore Dashboard to view data for the entities in your application, as well as statistics for the built-in and composite indexes.

Go to the Cloud Datastore Dashboard page

The dashboard should look like:

Datastore Dashboard

For more information about the statistics on this page, see Viewing Statistics in the Console.

Viewing indexes

Go to the Indexes page to view a table of your application's indexes.

Go to the Indexes page

For each index, you should see its status, such as whether it is ready to serve your application. You should also see the amount of storage space used by the index and the number of entries in each index.

Viewing entities

Go to the Entities page to view the entities that your application stored in your database.

Go to the Entities page

You should see:

Datastore Entities page

You can also create, update, delete, and query entities on this page. Learn how in the Quickstart.

Enabling or disabling Cloud Datastore Admin access

If you want to use bulk copy, bulk delete, backups, or restores, you need Cloud Datastore Admin access.

To enable or disable Cloud Datastore Admin access:

  1. Go to the Admin page.
    Go to the Admin page

  2. Click Enable Datastore Admin to enable access, or Disable Datastore Admin to disable access. The button text varies, depending on the state of your project.

Caveats on using Cloud Datastore Admin features

  • For copy, delete, and backups, recent updates might not be considered.
  • All Cloud Datastore Admin operations occur within your application, and thus count against your quota.
  • You are strongly recommended to disable writes during a backup or restore.
  • Existing entities with the same keys will be overwritten during a copy/restore operation. Duplicates are not created if copy/restore operations are performed multiple times. Copy/restore operations do not delete extra data.
  • If you use a non-default queue for backup/restore, you can only specify the target ah-builtin-python-bundle in queue.yaml. You cannot use any other targets.

Deleting entities

Go to the Admin page to delete all entities of a kind, or all entities of all kinds, in all namespaces.

  1. If you haven't already done so, enable Cloud Datastore access for your project.
  2. Go to the Admin page.
    Go to the Admin page
  3. Click Open Datastore Admin.
  4. Select one or more entity kinds.
  5. Click Delete Entities.

Datastore Entities page

Enabling or disabling database writes

It's normally a good idea to disable writes prior to a restore. This helps avoid conflicts between the restore and any new data written to your database. You can still use the Admin page to restore data and to perform bulk deletes when writes are disabled.

Disabling writes prevents entities from being changed by

  • the Cloud Datastore Viewer.
  • applications that use the Cloud Datastore API.

To enable or disable writes:

  1. Go to the Admin page.

    Go to the Admin page

  2. Click Enable writes to enable writes, or Disable writes to disable writes. The button text varies, depending on the state of your project.

Backing up or restoring data

Use the Admin page to backup or restore your data.

Go to the Admin page

Learn how to perform backups and restores in Backing Up and Restoring.

Viewing resource usage

When you run a Cloud Datastore Admin job, you are actually running an underlying MapReduce job. MapReduce jobs cause frontend instance hours to increase on top of Storage operations and Storage usage.

To view your resource usage:

  1. Visit the GCP Console App Engine page.

    Go to the App Engine page

  2. Use the pulldown menus at the top of the page to select the default service and the ah-builtin-python-bundle version.

What's next?



App Engine standard environment for Python 2