This post will address the Web Sites DASHBOARD management page. In one of my earlier posts I discussed the QuickStart management page.
The DASHBOARD management page is one of the most important pages. We'll discuss all the options on this page one by one. Before we proceed further, here is a snapshot of the DASHBOARD page:
There are several sections which depicts different data and provides the users with certain information and options.
As soon as the user lands on this page, he will see the graphical representation of certain CPU metrics which provides some insight into the overall usage of the site. I will not discuss this entirely here as this is a replica of the same information which is available on the MONITOR management page. The only change is that here the users have the ability to select only these metrics:
Below is a snapshot of the chart when the endpoint monitoring is enabled:
We will discuss this in more detail when I would post about MONITOR Management Page later.
At the bottom of the page is the Command Bar that provides basic manage functionalities to stop, start and browse a website. Below is a snapshot:
As seen above it includes the following options:
Currently this feature is in PREVIEW
(or BETA) and is available only if the website is running in STANDARD mode. This provides for monitoring functionality for the Web Site's HTTP or HTTPS endpoints from up to 3 geographically distributed locations. Below is a snapshot before the web endpoint is configured for monitoring:
This section corresponds to the monitoring section under the CONFIGURE Management Page.
The users can configure a maximum of 2 endpoints each of which can be monitored from up to 3 geographic locations. Rephrasing again, "one endpoint can be monitored from up to 3 geographical locations". There are 8 geographical locations to choose from, they are:
To set this up the user needs to browse to the Configure management page. After the user has created the endpoint, the Dashboard management page takes some time to update the changes. It may take approximately 10-15 minutes for the portal to reflect the changes. Until the changes are reflected the user will see this:
Once the portal has finished updating, the user will see something similar to this:
As shown above, the user will get an option to view the result of the tests. UI will display the endpoints that were tested (from the chosen geo-locations) along with the timestamp. The time stamp seen in the above image reflects the user's local time-zone. The user has to click on the endpoint's name to view the results. I setup 2 endpoints called Kaushal and test as seen above. Below is the output when I click on one of the endpoints.
This section displays the data corresponding to the AUTOSCALE option under SCALE Management page. Currently this feature is in PREVIEW
(or BETA) and is available only if the website is running in STANDARD mode. Below is a snapshot of the section before autoscale has been configured:
Once the website has been scaled to STANDARD and autoscale has been set to CPU, the portal would update the section and this is what it would display:
This section displays the usage quotas for Data Out, CPU Time, File System Storage,
Memory Usage, SQL Server Database Size etc.
This section displays different set of data depending on which mode the website might be running in. Typically this section depicts the quota restriction enforced by Windows Azure on the utilization of system resources.
NOTE: The database info is related to SQL Server and not MySQL. There are no metrics available for MySQL on WAWS currently. To view this please logon to ClearDB's site.
As I mentioned earlier, WAWS prevents over usage of the resources through quota restrictions on the website. It takes subsequent actions when a website overuses the resources, this is done to prevent any subscriber from exhausting resources to the detriment of other subscribers.
What happens when a resource usage quota is exceeded?
Windows Azure takes the following actions if a subscription's resource usage quotas are exceeded in a quota interval:
This will display all the resources and dependencies of the user's web sites. The user can link new or existing Windows Azure SQL Database instances, MySQL instances, or Storage accounts to the web site.
If there are no linked resources then the DASHBOARD page reflects something as shown in the image below:
The MANAGE LINKED RESOURCES (a hyperlink) points to the LINKED RESOURCES management page.
Towards the right side of the page is the quick glance section which provides the user with few important options and information.
As seen in the above snapshot, it provides the following information:
View connection strings – This link when clicked displays the connection string to the user, provided the application connects to either a SQL or a MySQL database.
NOTE: The difference between Reset deployment profile credentials & Reset publish profile credentials has been discussed in more detail in this blog post: Click Here
NOTE: Once the source control is configured the option changes to reflect a new value. For example if the user configures GitHub as a source control, the quick glance section would contain an option called Disconnect from GitHub. See below snapshot:
There are other sections below quick glance (right side of the page) which provide additional information regarding the website.
So this is the summary of the DASHBOARD Management Page. I will update this post to keep in sync with the new features that either get added or removed.