Join Joseph Lowery for an in-depth discussion in this video Using the project console, part of Up and Running with Google Cloud Platform.
- In this lesson we'll take a tour of the App Engine's robust project console. If you're following along, make sure you've completed the steps in the previous lesson before you proceed. So here I am at the Google Cloud platform home page focusing on the App Engine. Now to get to your project console from any of those entry points just click Go to my console, if you're already signed in, otherwise you'll see a Sign in link right next to it. The next screen shows you all your available projects.
We have two, the one that we originally set up when we were getting underway. And then the one that we developed in the previous chapter. Let's explore the one that we just created, Hello App Engine 1. So I'll click that link and we'll start off in the project console. And here we are in the overview where up top there's a chart with a Summary of Activity. Now I did this yesterday, so I'm going to click the 1 day tab here and it will redraw and show us our little spike of activity, that's basically when we set it up.
And you may need to choose a different time option to see your results. There are a great many other chart views to select from, but you have to drill down into the console a bit. So over on the left-hand side navigation select Compute, and then App Engine, and then Dashboard. Now in addition to our Summary chart, again let me switch it to a 1 day perspective, we have a select list with a good number of other options.
Let's look at Traffic, for example. Here we can not only track the Bytes Sent, oh I'm sorry, Bytes Sent is actually the green down below here, but also those Received. And of course, the more activity that you have the more the chart will reflect that. Now the rest of the Dashboard that we see here, I'll scroll down, shows the Instances used, now we just have the 1 so far, and our Billing status right below that.
Now it's still free, we haven't really invoked any charges yet, we won't for some time probably. The rest of the Dashboard shows the Current load, any Server Errors that you see, or any Client Errors. So far we're pretty much Error-free. More details about instant usage are really just a click away. Including displaying the latency, requests, errors, memory, and so forth. In fact if we go up a little bit, back up, and drill down to Instances, so we'll get a better perspective of that.
We'll see all of that information, as well as a option for taking it offline. Now to see a little bit more of what was going on you can follow the activity by clicking the View link under Logs. Now, of course, you won't see a whole lot of activity, we just did a very simple hello world app, but you can expand the log to get a little bit more information and it will show you precisely that This request caused a new process to be started for your application and so your application code might be loaded for the first time, it might take longer, more CPU.
So that explains the spike that we saw there. Now over on the left navigation, let's go down to Quota details. Now we certainly haven't reached the quota on anything at this point, but you definitely want to keep an eye on this panel when testing to get a sense of how much bandwidth and storage your app is taking up. Just to give you an idea of the kind of information that you'll be able to access, I'll click the link here to Show resources not in use.
And now you can see all of the various resources that will be tracked, and there are quite a few of them. There's Storage, Mobile Storage, Search, Mail, UriFetch, Sockets, Image Manipulation, and so on. Very robust. Now the last stop on this brief tour is to Settings. Again I'll go to my left-hand navigation, click Settings.
Now there are a number of basic application settings you can change here. Like how long your Login Cookie will stay active, 1 day, 1 week, 2 weeks. And also, for example, the type of Authentication protocol that you want to use. Choices are using Google Accounts, or Google Apps domain. And finally, how long you want to retain your Logs. Which can either be a duration, a number of days, or until it reaches a certain size.
But more interesting, at least to me, is the Custom Domain tab that I wanted to point out to you. This is where you want to go when you're ready to begin marketing your app and want to use your own domain, rather than an app spot sub-domain. So let me just click Add a custom domain so you can see what's required. Basically you're going to have to verify that you own the domain, using Google's Web Master tools. And then once you have that verification all set up, modify the DNS resource records to point your App Engine hosted app according to the information provided here in step 3.
There is of course no reason to create a custom domain for our example app, so let's just go back to the Dashboard to dismiss the screen. Obviously there's a great more to the project console, but this lesson is intended to pinpoint some of the more crucial elements.
Learn the basics of hosting a mobile app with App Engine and see how to analyze massive datasets in seconds with BigQuery. Then explore the benefits of Cloud Storage, including unlimited file storage and fast data retrieval, and learn how to establish a cloud-based private network with Compute Engine. Finally, the course explores how to set up and manage cloud-based databases with Cloud Datastore and Cloud SQL.
- Why Google Cloud Platform?
- Deploying an app with Google App Engine
- Activating and working with Google Cloud Storage
- Loading, querying, and exporting data with BigQuery
- Working with Cloud Storage buckets
- Managing cloud-based private networks
- Importing and exporting data
- Scheduling backups
- Working with Google Datastore
- Filtering data with Cloud SQL