Skip to content

Commit 6c1ab04

Browse files
authored
Merge pull request #222301 from MicrosoftDocs/main
Publish to live, Friday 4 AM PST 12/23
2 parents 184a762 + 44ac12a commit 6c1ab04

File tree

40 files changed

+459
-517
lines changed

40 files changed

+459
-517
lines changed

articles/azure-arc/vmware-vsphere/quick-start-connect-vcenter-to-arc-using-script.md

Lines changed: 26 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -79,7 +79,7 @@ You need a Windows or Linux machine that can access both your vCenter Server ins
7979

8080
8. Under **Region**, select an Azure location where the resource metadata will be stored. Currently, supported regions are **East US**, **West Europe**, **Australia East** and **Canada Central**.
8181

82-
9. Provide a name for **Custom location**. This is the name that you'll see when you deploy VMs. Name it for the datacenter or the physical location of your datacenter. For example: **contoso-nyc-dc**.
82+
9. Provide a name for **Custom location**. You'll see this name when you deploy VMs. Name it for the datacenter or the physical location of your datacenter. For example: **contoso-nyc-dc**.
8383

8484
10. Leave **Use the same subscription and resource group as your resource bridge** selected.
8585

@@ -145,11 +145,35 @@ A typical onboarding that uses the script takes 30 to 60 minutes. During the pro
145145
| **Data store** | Select the name of the datastore to be used for the Azure Arc resource bridge VM. |
146146
| **Folder** | Select the name of the vSphere VM and the template folder where the Azure Arc resource bridge's VM will be deployed. |
147147
| **VM template Name** | Provide a name for the VM template that will be created in your vCenter Server instance based on the downloaded OVA file. For example: **arc-appliance-template**. |
148-
| **Control Plane IP** address | Provide a static IP address that's outside the DHCP range but still available on the network. Ensure that this IP address isn't assigned to any other machine on the network. Azure Arc resource bridge (preview) runs a Kubernetes cluster, and its control plane requires a static IP address. Control Plane IP must have internet access. |
148+
| **Control Plane IP address** | Provide a static IP address that is outside the DHCP scope for virtual machines but in the same subnet. Ensure that this IP address isn't assigned to any other machine on the network. Azure Arc resource bridge (preview) runs a Kubernetes cluster, and its control plane requires a static IP address. Control Plane IP must have internet access. |
149149
| **Appliance proxy settings** | Enter **y** if there's a proxy in your appliance network. Otherwise, enter **n**. </br> You need to populate the following boxes when you have a proxy set up: </br> 1. **Http**: Address of the HTTP proxy server. </br> 2. **Https**: Address of the HTTPS proxy server. </br> 3. **NoProxy**: Addresses to be excluded from the proxy. </br> 4. **CertificateFilePath**: For SSL-based proxies, the path to the certificate to be used.
150150
151151
After the command finishes running, your setup is complete. You can now use the capabilities of Azure Arc-enabled VMware vSphere.
152152
153+
> [!IMPORTANT]
154+
> After the successful installation of Azure Arc resource bridge, it is recommended to retain a copy of the resource bridge config .yaml files and the kubeconfig file safe and secure in a place that facilitates easy retrieval. These files may be needed later to run a few commands to perform management operations on the resource bridge.
155+
156+
## Recovering from failed deployments
157+
158+
If the Azure Arc resource bridge deployment fails, consult the [Azure Arc resource bridge troubleshooting document](../resource-bridge/troubleshoot-resource-bridge.md). While there can be many reasons why the Azure Arc resource bridge deployment fails, one of them is KVA timeout error. For more information about the KVA timeout error and how to troubleshoot it, see [KVA timeout error](../resource-bridge/troubleshoot-resource-bridge.md#kva-timeout-error).
159+
160+
To clean up the installation and retry the deployment, use the following commands.
161+
162+
### Retry command - Windows
163+
164+
Run the command with ```-Force``` to clean up the installation and onboard again.
165+
166+
```powershell-interactive
167+
./resource-bridge-onboarding-script.ps1 -Force
168+
```
169+
170+
### Retry command - Linux
171+
172+
Run the command with ```--force``` to clean up the installation and onboard again.
173+
```bash
174+
bash resource-bridge-onboarding-script.sh --force
175+
```
176+
153177
## Next steps
154178

155179
- [Browse and enable VMware vCenter resources in Azure](browse-and-enable-vcenter-resources-in-azure.md)

articles/azure-monitor/app/azure-web-apps-net.md

Lines changed: 74 additions & 79 deletions
Large diffs are not rendered by default.

articles/azure-monitor/app/pre-aggregated-metrics-log-metrics.md

Lines changed: 37 additions & 37 deletions
Large diffs are not rendered by default.
Lines changed: 28 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -1,70 +1,73 @@
11
---
2-
title: Downtime, SLA, and outage workbook - Application Insights
3-
description: Calculate and report SLA for Web Test through a single pane of glass across your Application Insights resources and Azure subscriptions.
2+
title: Downtime, SLA, and outages workbook - Application Insights
3+
description: Calculate and report SLA for web test through a single pane of glass across your Application Insights resources and Azure subscriptions.
44
ms.topic: conceptual
55
ms.date: 05/4/2021
66
ms.reviwer: casocha
77
---
88

99
# Downtime, SLA, and outages workbook
1010

11-
Introducing a simple way to calculate and report SLA (service-level agreement) for Web Tests through a single pane of glass across your Application Insights resources and Azure subscriptions. The Downtime and Outage report provides powerful pre-built queries and data visualizations to enhance your understanding of your customer's connectivity, typical application response time, and experienced down time.
11+
This article introduces a simple way to calculate and report service-level agreement (SLA) for web tests through a single pane of glass across your Application Insights resources and Azure subscriptions. The downtime and outage report provides powerful prebuilt queries and data visualizations to enhance your understanding of your customer's connectivity, typical application response time, and experienced downtime.
1212

13-
The SLA workbook template is accessible through the workbook gallery in your Application Insights resource or through the availability tab by selecting **SLA Reports** at the top.
14-
:::image type="content" source="./media/sla-report/availability.png" alt-text="Screenshot of availability tab with SLA Reports highlighted." lightbox="./media/sla-report/availability.png":::
13+
The SLA workbook template is accessible through the workbook gallery in your Application Insights resource. Or, in the left pane, select **Availability** and then select **SLA Report** at the top of the screen.
14+
:::image type="content" source="./media/sla-report/availability.png" alt-text="Screenshot that shows the Availability tab with SLA Report highlighted." lightbox="./media/sla-report/availability.png":::
1515

16-
:::image type="content" source="./media/sla-report/workbook-gallery.png" alt-text="Screenshot of the workbook gallery with downtime and outages workbook highlighted." lightbox ="./media/sla-report/workbook-gallery.png":::
16+
:::image type="content" source="./media/sla-report/workbook-gallery.png" alt-text="Screenshot of the workbook gallery with the Downtime & Outages workbook highlighted." lightbox ="./media/sla-report/workbook-gallery.png":::
1717

1818
## Parameter flexibility
1919

2020
The parameters set in the workbook influence the rest of your report.
2121

22-
:::image type="content" source="./media/sla-report/parameters.png" alt-text=" Screenshot of parameters." lightbox= "./media/sla-report/parameters.png":::
22+
:::image type="content" source="./media/sla-report/parameters.png" alt-text=" Screenshot that shows parameters." lightbox= "./media/sla-report/parameters.png":::
2323

24-
`Subscriptions`, `App Insights Resources`, and `Web Test` parameters determine your high-level resource options. These parameters are based on Log Analytics queries and used in every report query.
24+
* `Subscriptions`, `App Insights Resources`, and `Web Test`: These parameters determine your high-level resource options. They're based on Log Analytics queries and are used in every report query.
25+
* `Failure Threshold` and `Outage Window`: You can use these parameters to determine your own criteria for a service outage. An example is the criteria for an App Insights Availability alert based on a failed location counter over a chosen period. The typical threshold is three locations over a five-minute window.
26+
* `Maintenance Period`: You can use this parameter to select your typical maintenance frequency. `Maintenance Window` is a datetime selector for an example maintenance period. All data that occurs during the identified period will be ignored in your results.
27+
* `Availability Target %`: This parameter specifies your target objective and takes custom values.
2528

26-
`Failure Threshold` and `Outage Window` allow you to determine your own criteria for a service outage, for example, the criteria for App Insights Availability alert based upon failed location counter over a chosen period. The typical threshold is three locations over a five-minute window.
27-
28-
`Maintenance Period` enables you to select your typical maintenance frequency and `Maintenance Window` is a datetime selector for an example maintenance period. All data that occurs during the identified period will be ignored in your results.
29+
## Overview page
2930

30-
`Availability Target %` specifies your target objective & takes custom values.
31+
The overview page contains high-level information about your:
3132

32-
## Overview page
33+
- Total SLA (excluding maintenance periods, if defined).
34+
- End-to-end outage instances.
35+
- Application downtime.
3336

34-
The overview page contains high-level information about your total SLA (excluding maintenance periods if defined), end to end outage instances, and application downtime. Outage instances are defined by when a test starts to fail until it is successful based on your outage parameters. If a test starts failing at 8:00 am and succeeds again at 10:00 am, then that entire period of data is considered the same outage.
37+
Outage instances are defined by when a test starts to fail until it's successful, based on your outage parameters. If a test starts failing at 8:00 AM and succeeds again at 10:00 AM, that entire period of data is considered the same outage.
3538

36-
:::image type="content" source="./media/sla-report/overview.gif" alt-text=" GIF of overview page showing the overview table by test." lightbox="./media/sla-report/overview.gif":::
39+
:::image type="content" source="./media/sla-report/overview.gif" alt-text=" Screenshot that shows an overview page showing the Overview Table by Test." lightbox="./media/sla-report/overview.gif":::
3740

38-
You can also investigate your longest outage that occurred over your reporting period.
41+
You can also investigate the longest outage that occurred over your reporting period.
3942

40-
Some tests are linkable back to their Application Insights resource for further investigation but that is only possible in the [Workspace-based Application Insights resource](create-workspace-resource.md).
43+
Some tests are linkable back to their Application Insights resource for further investigation. But that's only possible in the [workspace-based Application Insights resource](create-workspace-resource.md).
4144

4245
## Downtime, outages, and failures
4346

44-
The **Outages and Downtime** tab has information on total outage instances and total down time broken down by test. The **Failures by Location** tab have a geo-map of failed testing locations to help identify potential problem connection areas.
47+
The **Outages & Downtime** tab has information on total outage instances and total downtime broken down by test. The **Failures by Location** tab has a geo-map of failed testing locations to help identify potential problem connection areas.
4548

46-
:::image type="content" source="./media/sla-report/outages-failures.gif" alt-text=" GIF of Outages and Downtime tab and Failure by Location tab in the downtime and outages workbook." lightbox="./media/sla-report/outages-failures.gif":::
49+
:::image type="content" source="./media/sla-report/outages-failures.gif" alt-text=" Screenshot that shows the Outages & Downtime tab and the Failure by Location tab in the downtime and outages workbook." lightbox="./media/sla-report/outages-failures.gif":::
4750

4851
## Edit the report
4952

50-
You can edit the report like any other [Azure Monitor Workbook](../visualize/workbooks-overview.md). You can customize the queries or visualizations based on your team's needs.
53+
You can edit the report like any other [Azure Monitor workbook](../visualize/workbooks-overview.md). You can customize the queries or visualizations based on your team's needs.
5154

52-
:::image type="content" source="./media/sla-report/edit.gif" alt-text=" GIF of selecting the edit button to change the visualization to a pie chart." lightbox="./media/sla-report/edit.gif":::
55+
:::image type="content" source="./media/sla-report/edit.gif" alt-text=" Screenshot that shows selecting the Edit button to change the visualization to a pie chart." lightbox="./media/sla-report/edit.gif":::
5356

5457
### Log Analytics
5558

5659
The queries can all be run in [Log Analytics](../logs/log-analytics-overview.md) and used in other reports or dashboards. Remove the parameter restriction and reuse the core query.
5760

58-
:::image type="content" source="./media/sla-report/logs.gif" alt-text=" GIF of log query." lightbox="./media/sla-report/logs.gif":::
61+
:::image type="content" source="./media/sla-report/logs.gif" alt-text=" Screenshot that shows a log query." lightbox="./media/sla-report/logs.gif":::
5962

6063
## Access and sharing
6164

62-
The report can be shared with your teams, leadership, or pinned to a dashboard for further use. The user needs to have read permission/access to the Applications Insights resource where the actual workbook is stored.
65+
The report can be shared with your teams and leadership or pinned to a dashboard for further use. The user needs to have read permission/access to the Application Insights resource where the actual workbook is stored.
6366

64-
:::image type="content" source="./media/sla-report/share.png" alt-text=" Screenshot of share this template." lightbox= "./media/sla-report/share.png":::
67+
:::image type="content" source="./media/sla-report/share.png" alt-text=" Screenshot that shows the Share Template pane." lightbox= "./media/sla-report/share.png":::
6568

6669
## Next steps
6770

68-
- [Log Analytics query optimization tips](../logs/query-optimization.md).
71+
- Learn some [Log Analytics query optimization tips](../logs/query-optimization.md).
6972
- Learn how to [create a chart in workbooks](../visualize/workbooks-chart-visualizations.md).
7073
- Learn how to monitor your website with [availability tests](monitor-web-app-availability.md).

0 commit comments

Comments
 (0)