forked from Azure/AppService
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #2 from Azure/master
Sync with upstream
- Loading branch information
Showing
8 changed files
with
95 additions
and
0 deletions.
There are no files selected for viewing
56 changes: 56 additions & 0 deletions
56
_posts/2020-03-23-A-New-Look-for-App-Service-Diagnostics.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,56 @@ | ||
--- | ||
title: "A New Look for App Service Diagnostics" | ||
author_name: "Yun Jung Choi" | ||
toc: true | ||
toc_sticky: true | ||
excerpt: "We are launching a new experience in App Service Diagnostics to help you more easily and quickly diagnose and solve problems of your application." | ||
tags: | ||
- diagnostics | ||
- troubleshooting | ||
- self-help | ||
--- | ||
|
||
> Currently available for select Windows web apps. | ||
App Service Diagnostics is an intelligent and interactive experience to help you troubleshoot your app with no configuration required. When you run into issues with your app, App Service Diagnostics points out what's wrong to guide you to the right information to more easily troubleshoot and resolve issues. | ||
|
||
To make it easier for you to discover your application's issues and helpful insights, we are launching a new experience in App Service Diagnostics. | ||
|
||
## Discover Issues Faster | ||
|
||
The new experience allows you quickly discover issues that your application might be encountering by running health checks for each problem category upfront. Upon clicking on each problem category in the homepage, a series of checks are run, and the results are presented in the overview page. | ||
|
||
![Landing Page]({{site.baseurl}}/media/2020/03/landing-page.png) | ||
|
||
![Overview Page]({{site.baseurl}}/media/2020/03/overview-page.png) | ||
|
||
The cards at the top of the overview page show the status of your app by performing pre-selected checks on your application's backend telemetry. You can click on these cards to further investigate the issue. | ||
|
||
If you already know the problem you want to drill down to, choose a relevant item in the left navigation where you will find more comprehensive checks on different topics. | ||
|
||
![Web App Down]({{site.baseurl}}/media/2020/03/web-app-down.png) | ||
|
||
## Interactive Interface: Genie | ||
|
||
When you are not sure where to begin, or you cannot find the information you are looking for, App Service Diagnostics' interactive interface, Genie, can help guide you through diagnosing and solving problems of your app. | ||
|
||
Click the **Ask Genie** button at the top of the page to start a chat with our interactive interface, Genie. Type in the issue you are experiencing, and Genie will automatically fetch relevant diagnostics available in App Service Diagnostics and return the results along with relevant documentation found on the web. Genie will share its observation on the issue and list out checks that have succeeded. You can click on **More Info** to see additional information for each check. | ||
|
||
![Genie]({{site.baseurl}}/media/2020/03/genie.png) | ||
|
||
## Command Bar | ||
|
||
The new experience introduces a command bar control at the top where you will find buttons and controls you often interact with. Below controls are now available in every page with diagnostics. | ||
|
||
![Command Bar]({{site.baseurl}}/media/2020/03/command-bar.png) | ||
|
||
- **Search**: Search is now available in every page for you to quickly find and navigate to different diagnostics of your choice. | ||
- **Ask Genie**: Ask Genie button is available in every page for you to get analysis and documentation results tailored to your issue. | ||
- **Feedback**: Feedback button is available in every page for you to share feedback with the App Service Diagnostics Product team. | ||
- **Time Filter**: The new time filter now gives options to choose from predefined time range and custom time range using date picker and time picker to more easily filter the diagnostics to your desired time range. The time you select will be honored when you switch to another page. (Current limitation: The time will reset to 24-hour range once you go back to the homepage.) | ||
|
||
## What's Next | ||
|
||
For more information on App Service Diagnostics, please visit [Azure App Service diagnostics overview](https://docs.microsoft.com/azure/app-service/overview-diagnostics). | ||
|
||
Feel free to share your feedback or questions about **App Service Diagnostics** by emailing [[email protected]](mailto:[email protected]) or posting on [UserVoice](https://feedback.azure.com/forums/169385-web-apps) with "[Diag]" in the title. |
39 changes: 39 additions & 0 deletions
39
_posts/2020-03-23-PremiumV2 support for older deployments.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,39 @@ | ||
--- | ||
title: "PremiumV2 tier for older App Service deployments" | ||
tags: | ||
- app service plan | ||
author_name: "Christina Compy" | ||
--- | ||
|
||
The PremiumV2 hardware tier is now available for older deployments of App Service where it was not previously available. A few years ago Azure App Service began to offer the PremiumV2 App Service plan. The benefits of this new tier were tied to the new hardware that was used for it. The same hardware is used for Free to Standard App Service plans. The new hardware required some changes to the system architecture and was not compatible with our older deployments. This unfortunately left many customers unable to upgrade their plans to PremiumV2. To solve this problem we developed a different way to attach the new PremiumV2 compute just for our older App Service deployments. This solution is now slowly rolling out and is adding the PremiumV2 option where it was previously unavailable. | ||
|
||
## Changing IP Addresses | ||
|
||
When you scale to PremiumV2 while in a newer App Service deployment, your outbound addresses will change. To help customers that are sensitive to that, the app property called **Additional Outbound IP Addresses** contains all of the outbound addresses that your app can have. This field holds the outbound addresses your app can have while in Free through Standard as well as the addresses it would have while in PremiumV2. | ||
|
||
With the new ability to offer PremiumV2 to older deployments of the Azure App Service, both your inbound and outbound IP addresses will change when you scale from Standard or lower to PremiumV2 and back. This means that if you have A records for your app, you will need to update them after you scale. Your app will still be accessible for at least five days from the original address as we relay the inbound traffic to the new address. When you go to scale your app from Standard or lower to PremiumV2, you will be told the new addresses for your app. The same will be true if you scale from PremiumV2 to a lower tier. | ||
|
||
In order to select the PremiumV2, you need to acknowledge that your inbound and outbound addresses will change as you scale up your App Service plan. | ||
|
||
## Features gained and lost | ||
|
||
There is a feature lost and another gained when you scale to PremiumV2 in these older App Service deployments. | ||
|
||
- **Remote debugging**: When you scale your app to PremiumV2, you will no longer be able to use remote debugging for your apps. If you scale your App Service plan to a lower tier, you will be able to use remote debug again. | ||
- **Regional VNet Integration**: When your app is in a PremiumV2 App Service plan, you will be able to use regional VNet Integration. When you scale back down to Standard tier or lower, you will lose the ability to use the feature. This is different from the newer App Service deployments where you can use regional VNet Integration from Standard and PremiumV2. | ||
|
||
## How to scale to PremiumV2 | ||
|
||
To scale up to PremiumV2, or just to see if you can scale up to PremiumV2, navigate to the **Scale up (App Service plan)** page in your app portal. If you can select any of the PremiumV2 options, you are able to scale to PremiumV2. The user experience will show you your new addresses and request your acknowledgement. If you opt out at this point and come back later, the addresses you would see would be the same for the same app. | ||
|
||
![PremiumV2 tier selection experience]({{ site.baseurl }}/media/2020/03/premiumv2-old-scale-units.png) | ||
|
||
## Benefits of PremiumV2 | ||
|
||
It is important to highlight some of the other benefits of using a PremiumV2 App Service plan. Those benefits include: | ||
|
||
* Cores are over twice as powerful | ||
* Twice the memory per core as Standard or lower | ||
* Can scale up to 30 instances | ||
* Will be able to use Private Endpoints | ||
* Can use regional VNet Integration |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.