Moving to the Google Cloud Platform Console

The migration from the App Engine Admin Console to the Cloud Platform Console is underway and almost complete. You will find details in this doc to help with the transition.

Features that will be available

Rest assured that all of the following items will be live and available in the Cloud Platform Console before the Admin Console is turned down:

  • Version stop and start control (now live!)
  • Option to permanently prohibit code downloads (now live!)
  • Blob viewer (now live!)
  • Usage history (now live!)
  • Migrate traffic (now live!)
  • Billed instances estimate (now live!)


You can still see all the charts that were in the Admin Console dashboard, in the same units you’d expect. In addition, the new dashboard has much more!

Usage History

Your daily usage history data is now available as an additional tab in the Quota component.


The logging user interface has moved to the Logs Viewer in the Cloud Platform Console. The new user interface is improved to better support the way you use your logs. While the basic idea of browsing and viewing logs remains the same, the new Logs Viewer provides the following enhancements:

  • New capabilities unavailable in the old Admin Console:

    • Logs-based Metrics: Create metrics and alerts on log data. Integrated with Stackdriver Monitoring.
    • Logs to Trace and Logs to Debugger: Creates paths to and from the Diagnostic tools.
    • Advanced Filtering: Provides a powerful new filter syntax for slicing and dicing log data.
    • Structured Logs: Structures all App Engine log data as hierarchical key value pairs for better filtering.
    • Logs Export: Exports log data to BigQuery, Google Cloud Storage, or a custom endpoint via Cloud Pub/Sub.
  • New and more flexible workflow support.

These enhancements result is a more useful logs viewer that has more powerful features. Below are some FAQs / documented changes, and how to adapt your workflow to the new Logs Viewer.

Why does the Logs Viewer seem slower than the old console?

There are two types of latencies that impact your experience.

  • First-load latency: The new logs viewer is built to support more functionality, and Cloud Console as a whole is built to optimize for faster transitions within the console rather than from “cold starts” from outside. We heard from you that this “cold start” latency was too high, and we have already made changes that cut this latency by more than 50%. This is still slightly higher than the old console due to the differences in architecture, but you will not see this if you are already using Cloud Console (the common case). There’s still some room for improvement, and we will continue to work to reduce cold start latency further in the future, but we have reduced it enough for the moment that we are currently prioritizing other, more impactful improvements for you.
  • Query latency: The logs viewer had a different time-out and progress reporting model than the old console, which give a perception of slowness. In the past, it did not communicate that no logs have been found fast enough and when looking for sparse data over an unscoped search, sometimes seems unresponsive (when in reality it is still searching). We have worked to implement a better progress reporting and a more interactive logs viewer to improve the experience. In addition, we will continue to work on the backend to actually return results faster.

How do I turn off scrolling in the new logs viewer?

As mentioned, we thought about the logs viewer differently from the admin console. The logs viewer supports infinite scroll, whereas the old console was built for pagination. Infinite scrolling helps users with viewing live streaming logs, as well as viewing logs around an event without artificial cutoffs between adjacent events requiring paging back and forth.

Does the new Logs Viewer remember my time zone settings like the old console did?

Yes, we will keep a record of the time zone you selected in the logs viewer last time and will default to that. There was an issue where the Logs Viewer defaulted to the system time and this has been fixed.

How can I see logs for the same request_id? How is this different from the old console?

  • You can view logs for a request id by either manually filtering for the request id, or using the “three dot” menu on the right side of any existing entry and selecting show entries from same request.
  • Due to differences in the architectures of the logging systems, the new logs system doesn’t automatically collapse together multiple log entries from AE from long-running requests where AE sends intermediate log checkpoints over time. Based on your feedback, we will soon update the viewer to show only the beginning and ending log entry by default, to reduce the amount of noise in the overall request view. When viewing entries from a specific request, however (as described above), all entries from the request will be shown.

I am used to drop-downs for project, AE version, AE module, and time zone. How does this change in the new logs viewer?

The new logs viewer has slightly different drop downs: there is a service dropdown that allows you to select an App Engine service, module, and version in the cascading menu. If you are used to it, you will find it faster and more flexible. There is also a drop down for ‘severity’ as well as a time picker that allows you to jump to a particular time in a timezone.

Where can I learn more about the new Logs Viewer?

See the Cloud Logging documentation.

I just need to look at my logs. How can I go to the new logs viewer directly?

Bookmark this URL:

Application Settings

Logs Retention

The Admin Console provides 90 days of logs retention by default, with the ability to configure this value up to 1 full year. Cloud Logging in the Cloud Console instead has a default retention policy of 30 days. In order to retain logs for longer, follow the instructions here to export logs to Cloud Storage, BigQuery, or Cloud Pub/Sub.

Disable Datastore Writes

You can find this option on the Datastore Admin page.


The Cloud Console uses Datastore GQL in the ‘Query by GQL’ tab, whereas it previously used Python GQL. You can read more details on query language differences in our documentation.

As Datastore GQL does not support URL-safe keys, if you need to find entities using URL-safe keys you can use the ‘Query by Kind’ tab and select ‘Filter Entities instead. More details.


You can now start and stop versions in the Cloud Console. The versions table provides details such as the instance class and the number of idle instances.

We are aware that the versions page does not auto-refresh to show instances as they are deployed. We are actively working on a solution to this issue.


A delete button is in the works for all instances, regardless of environment type.

Dispatch & Blacklist

Today the Admin Console allows you to view the contents of the dispatch and DoS configuration files. These pages will not be available in the Cloud Platform Console. We are aware this is inconvenient and we are working towards providing a comprehensive view of your application’s configuration in the Cloud Platform Console, which will be available in several months. For the current state of your configuration, please reference the uploaded configuration files.

The functionality of the DoS Protection Service will not change, your application will still follow the rules that you have in place.

Domain Accounts

App Engine Premier Accounts were introduced in October 2011, and were the first paid support offering for App Engine. Everything provided by Premier Accounts has been folded into Google Cloud Platform's current support offerings, with the exception of a feature called Domain Accounts.

Domain Accounts enabled App Engine administrators to view all the App Engine projects on their Google Apps domain. Today, this feature has limited value and low usage because it only applies to App Engine, and the majority of our customers use multiple Google Cloud Platform (GCP) services. These Domain Accounts are being deprecated, and access will no longer be available to these pages in the Admin Console. No action is required, as all applications will continue to be billed as they are today, and serving will not be interupted.

Once the Domain Account functionality is deprecated, the workflow to enable billing becomes consistent with how project billing is handled for all GCP projects. The main difference is that billing can only be enabled by someone who is both a billing admin on the target billing account and a project owner. Full documentation on managing billing accounts, billing administrators, and project billing is available.

Google is developing a new GCP resource called Organizations. Organization resources provide an administrator with the ability to define IAM policies that are applied to GCP projects created on the domain. You can then stipulate that all GCP projects created on the domain include, for example, a group of administrators as owners. If you are interested in getting an invitation, please fill out the form on the Cloud Resource Manager page.

Custom Pages

Custom pages will not be available in the Cloud Console. As an alternative, administrator authentication can be configured within the app.yaml file or within your application. Here is a python example.

Send feedback about...

App Engine Documentation