Microsoft Azure Web sites app and Practice series:
"1"--Build your first Microsoft Azure Website
"2"--Remote administration of Microsoft Azure Web Site via local IIS
"3"-online editing of the Microsoft Azure Web site through visual Studio online
"4"--microsoft the "backdoor" of the Azure website
The "backdoor" of the Microsoft Azure Web site
As you can see from our previous blog post, users can control primarily the data and files of their own applications for the Microsoft Azure Web site, while the server system or other lower configuration is like a black box for us. This is a PAAs-based design because it allows us to focus on the application without worrying about the underlying platform. It may be a little curious sometimes: is it completely impossible to learn more about the "server" where Microsoft Azure Web sites are located?
Actually, it's possible. The Microsoft Azure website has an open source tool to open a special "backdoor" for administrators to learn more information or assist in troubleshooting. Let's give you a brief introduction.
Login
Assume that your current Microsoft Azure Web site is named Yoursitename
You can choose from one of the following two options:
Method One:
Entrance: HTTPs://yoursitename. SCM. Azurewebsites.net
Credentials: The same as the user name and password used to log on to the Azure portal management site
Method Two:
Entrance: HTTPs://yoursitename. SCM . Azurewebsites.net/basicauth
Credentials: The same as the FTP user name for the Microsoft Azure Web site (no need to add a site name) and a password.
After logging in, enter the Kudu website as follows:
Main Features Overview View server environment (environment)
In this section we can view system information (such as the operating system, IIS configuration file ApplicationHost.config, etc.), environment variables, connection strings, and so on.
Virtual command line (Debug Console)
Here we can open two windows that resemble the local server's window command line and PowerShell command line, and execute some commands that do not require special permissions.
In addition, you can choose to view and edit the listed folders and their contents directly or by dragging and uploading them. Of course, uploading some tools that do not need to be installed and running here is also permissible and feasible.
Progress Management (Process Explorer)
Here we can view some information about the processes related to our site, such as the W3wp.exe process that IIS corresponds to. You can also generate a dump file for troubleshooting when necessary.
Tool (Tools)
Some of the handy tools for troubleshooting.
Site extension (sites Extensions)
You can add some off-the-shelf extensions from the library to extend the functionality of your site from performance monitoring or optimization or problem diagnosis. For example, Visual Studio Online, Daas, and so on.
In addition, we can also see a button that restarts the site (Restart site) to complete the same task of restarting the site on the Azure Management portal site.
RELATED LINKS
Source code: https://github.com/projectkudu/kudu/
daas:http://azure.microsoft.com/blog/2014/07/08/daas/
Using Kudu to capture hang dumps for Windows Azure Web Sites
Using Kudu to capture first-chance dumps for Windows Azure Web Sites
Microsoft Azure Web Sites app and practice "backdoor" for "4"--microsoft Azure website