Skip to content

Commit 762ac39

Browse files
committed
edits
1 parent e996a19 commit 762ac39

8 files changed

+13
-13
lines changed

articles/azure-monitor/alerts/alerts-create-log-alert-rule.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -201,7 +201,7 @@ Limitations for log search alert rule queries:
201201
|Field |Description |
202202
|---------|---------|
203203
|Enable upon creation| Select for the alert rule to start running as soon as you're done creating it.|
204-
|Automatically resolve alerts (preview) |Select to make the alert stateful. When an alert is stateful, the alert is resolved when the condition is no longer met for a specific time range. The time range differs based on the frequency of the alert:<br>**1 minute**: The alert condition isn't met for 10 minutes.<br>**5-15 minutes**: The alert condition isn't met for three frequency periods.<br>**15 minutes - 11 hours**: The alert condition isn't met for two frequency periods.<br>**11 to 12 hours**: The alert condition isn't met for one frequency period. <br><br>Note that stateful log search alerts have these [limitations](azure/azure-monitor/service-limits#alerts).|
204+
|Automatically resolve alerts (preview) |Select to make the alert stateful. When an alert is stateful, the alert is resolved when the condition is no longer met for a specific time range. The time range differs based on the frequency of the alert:<br>**1 minute**: The alert condition isn't met for 10 minutes.<br>**5-15 minutes**: The alert condition isn't met for three frequency periods.<br>**15 minutes - 11 hours**: The alert condition isn't met for two frequency periods.<br>**11 to 12 hours**: The alert condition isn't met for one frequency period. <br><br>Note that stateful log search alerts have these [limitations](/azure/azure-monitor/service-limits#alerts).|
205205
|Mute actions |Select to set a period of time to wait before alert actions are triggered again. If you select this checkbox, the **Mute actions for** field appears to select the amount of time to wait after an alert is fired before triggering actions again.|
206206
|Check workspace linked storage|Select if logs workspace linked storage for alerts is configured. If no linked storage is configured, the rule isn't created.|
207207

articles/azure-monitor/app/api-custom-events-metrics.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -679,7 +679,7 @@ The function is asynchronous for the [server telemetry channel](https://www.nuge
679679

680680
> [!NOTE]
681681
> - The Java and JavaScript SDKs automatically flush on application shutdown.
682-
> - **Review Autoflush configuration**: [Enabling autoflush](dotnet/api/system.diagnostics.trace.autoflush) in your `web.config` file can lead to performance degradation in .NET applications instrumented with Application Insights. With autoflush enabled, every invocation of `System.Diagnostics.Trace.Trace*` methods results in individual telemetry items being sent as separate distinct web requests to the ingestion service. This can potentially cause network and storage exhaustion on your web servers. For enhanced performance, it’s recommended to disable autoflush and also, utilize the [ServerTelemetryChannel](azure/azure-monitor/app/telemetry-channels#built-in-telemetry-channels), designed for a more effective telemetry data transmission.
682+
> - **Review Autoflush configuration**: [Enabling autoflush](/dotnet/api/system.diagnostics.trace.autoflush) in your `web.config` file can lead to performance degradation in .NET applications instrumented with Application Insights. With autoflush enabled, every invocation of `System.Diagnostics.Trace.Trace*` methods results in individual telemetry items being sent as separate distinct web requests to the ingestion service. This can potentially cause network and storage exhaustion on your web servers. For enhanced performance, it’s recommended to disable autoflush and also, utilize the [ServerTelemetryChannel](/azure/azure-monitor/app/telemetry-channels#built-in-telemetry-channels), designed for a more effective telemetry data transmission.
683683
684684
## Authenticated users
685685

articles/azure-vmware/license-sql-windows-in-avs.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -79,17 +79,17 @@ You can enable Azure Hybrid Benefit for SQL Server and achieve unlimited virtual
7979

8080
##### License a virtual machine
8181
You can register SQL Server licenses and apply them to VMs running SQL Server in Azure VMware Solution by registering through Azure Arc:
82-
1. Azure VMware Solution must be Azure Arc-enabled. For more information, see [Deploy Azure Arc-enabled VMware vSphere for Azure VMware Solution](azure/azure-vmware/deploy-arc-for-azure-vmware-solution?tabs=windows). You can Azure Arc-enable the VMs and install extensions to that VM by following the steps provided in the section titled "Enable guest management and extension installation."
82+
1. Azure VMware Solution must be Azure Arc-enabled. For more information, see [Deploy Azure Arc-enabled VMware vSphere for Azure VMware Solution](/azure/azure-vmware/deploy-arc-for-azure-vmware-solution). You can Azure Arc-enable the VMs and install extensions to that VM by following the steps provided in the section titled "Enable guest management and extension installation."
8383
1. When **Guest Management** is configured, the Azure Extension for SQL Server should be installed on that VM. The extension installation enables you to configure the license type for the SQL Server instance running in the VM.
8484
1. Now you can configure the license type and other SQL Server configuration settings by using the Azure portal, PowerShell, or the Azure CLI for a specific Azure Arc-enabled server. To configure from the Azure portal with VMware vSphere in the Azure VMware Solution experience, follow these steps:
8585

8686
1. In the Azure VMware Solution portal, go to **vCenter Server Inventory** and **Virtual Machines** by clicking through one of the Azure Arc-enabled VMs. The **Machine-Azure Arc (AVS)** page appears.
8787
1. On the left pane, under **Operations**, select **SQL Server Configuration**.
8888
1. You can now apply and save your license type for the VM along with other server configurations.
8989

90-
You can also configure these settings within the Azure Arc portal experience and by using PowerShell or the Azure CLI. To access the Azure Arc portal experience and code to update the configuration values, see [Configure SQL Server enabled by Azure Arc](/sql/sql-server/azure-arc/manage-configuration?view=sql-server-ver16&tabs=azure).
90+
You can also configure these settings within the Azure Arc portal experience and by using PowerShell or the Azure CLI. To access the Azure Arc portal experience and code to update the configuration values, see [Configure SQL Server enabled by Azure Arc](/sql/sql-server/azure-arc/manage-configuration).
9191

92-
For available license types, see [License types](/sql/sql-server/azure-arc/manage-license-billing?view=sql-server-ver16#license-types).
92+
For available license types, see [License types](/sql/sql-server/azure-arc/manage-license-billing).
9393

9494
> [!NOTE]
9595
> At this time, Azure VMware Solution doesn't have support for the new `SQLServerLicense` resource type.

articles/private-5g-core/ran-insights-create-resource.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ Each RAN insights resource is associated with one physical site resource and is
2020
- Check if the network is ready by verifying that a device / user equipment (UE) connected to the network through the RAN can transmit and receive data. If this doesn't work, fix any problems before trying to activate the RAN insights feature.
2121
- Deploy a compatible version of the RAN EMS from your RAN partner. You'll need to verify with your RAN partner that your RAN EMS contains a Microsoft-compatible External Metrics Agent (EMA) to send metrics to Azure. If not, your partner will need to install a metrics agent on the EMS you're using. Information on how and where to establish the connection between Azure and the EMS is specific to the RAN vendor, so contact them for details.
2222
- Access to RAN insights for your Azure Subscription. Contact your Microsoft representative and ask them to register your Azure subscription for access to RAN insights.
23-
- Ensure you're registered with resource providers listed. Follow [Resource providers and resource types](azure/azure-resource-manager/management/resource-providers-and-types) for steps on how to register.
23+
- Ensure you're registered with resource providers listed. Follow [Resource providers and resource types](/azure/azure-resource-manager/management/resource-providers-and-types) for steps on how to register.
2424
- Microsoft.insights 
2525
- Microsoft.NetworkAnalytics 
2626
- Microsoft.KeyVault 
@@ -64,7 +64,7 @@ This tab holds important details, such as:
6464
- Eventhub name – name of the event hub
6565
- Keyvault – URL for key vault containing connection string
6666

67-
If you're unable to access the information in the MIE key vault URL then you may not have the correct credentials. If so, you need to take the necessary steps to grant access for the required role. Refer to [Azure RBAC documentation | Microsoft Learn](azure/role-based-access-control/) for steps on how to do this.
67+
If you're unable to access the information in the MIE key vault URL then you may not have the correct credentials. If so, you need to take the necessary steps to grant access for the required role. Refer to [Azure RBAC documentation | Microsoft Learn](/azure/role-based-access-control/) for steps on how to do this.
6868
:::image type="content" source="media/ran-insights/ran-insights-key-vault-not-working.png" alt-text="Screenshot of the Azure portal showing operation not allowed for key vault.":::
6969

7070

articles/private-5g-core/ran-insights-monitor-with-correlated-metrics-concepts.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ Correlated metrics are available for monitoring and retrieval for up to 30 days.
2424

2525

2626
## Correlated metrics descriptions and interpretations
27-
Correlated metrics are collected per site resource and aggregated across all connected access points. See [Supported metrics with Azure Monitor](azure/azure-monitor/reference/supported-metrics/metrics-index) for the corelated metrics available for retrieval included under *microsoft.mobilenetwork/sites*.
27+
Correlated metrics are collected per site resource and aggregated across all connected access points. See [Supported metrics with Azure Monitor](/azure/azure-monitor/reference/supported-metrics/metrics-index) for the corelated metrics available for retrieval included under *microsoft.mobilenetwork/sites*.
2828

2929
| Metric Name | Definition | Interpretation |
3030
|-------------|----------------|---------|

articles/private-5g-core/ran-insights-monitor-with-ran-metrics-concepts.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ These are a subset of metrics chosen from the RAN vendor’s EMS based on custom
1818

1919

2020
## Visualize RAN metrics using the Azure portal
21-
RAN metrics are collected per site resource and aggregated across all access points connected. See [Supported metrics with Azure Monitor](azure/azure-monitor/reference/supported-metrics/metrics-index) for the RAN metrics available for retrieval included under *microsoft.mobilenetwork/radioAccessNetworks*.
21+
RAN metrics are collected per site resource and aggregated across all access points connected. See [Supported metrics with Azure Monitor](/azure/azure-monitor/reference/supported-metrics/metrics-index) for the RAN metrics available for retrieval included under *microsoft.mobilenetwork/radioAccessNetworks*.
2222

2323
You can use the Azure portal to monitor your access points performance, reliability, and connection status. The RAN insights resource's **Overview** page under the **Monitoring** tab provides a prebuilt dashboard containing RAN metrics received.
2424
:::image type="content" source="media/ran-insights/ran-insights-monitoring-tab.png" alt-text="Screenshot of the Azure portal showing RAN insight resource monitoring tab.":::
@@ -29,7 +29,7 @@ To view more metrics on and create custom charts, select the **Metrics** tab und
2929

3030
Using the buttons just above the charts, you can edit the timespan from which the data shown in the charts and the granularity of how that data is plotted.
3131

32-
Timespan options range from showing the previous hour of data to the previous 7 days of data and granularity options range from plotting every minute to plotting every 12 hours. For detailed information on interacting with the Azure Monitor graphics, see [Get started with metrics explorer](azure/azure-monitor/essentials/analyze-metrics)
32+
Timespan options range from showing the previous hour of data to the previous 7 days of data and granularity options range from plotting every minute to plotting every 12 hours. For detailed information on interacting with the Azure Monitor graphics, see [Get started with metrics explorer](/azure/azure-monitor/essentials/analyze-metrics)
3333

3434
Note that the EMS might provide metrics at intervals up to 15 minutes apart. For an optimal experience, adjust the plotting rate to match the value recommended by the EMS provider. For instance, if your RAN provider emits metrics every 5 minutes, it's advisable to set the **Time granularity** to 5 minutes accordingly.
3535

articles/stream-analytics/stream-analytics-autoscale.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -96,7 +96,7 @@ The following procedure shows you how to add a condition to automatically increa
9696
:::image type="content" source="./media/stream-analytics-autoscale/save-scale-rule-streaming-units-limits.png" alt-text="Screenshot showing the Save option for a rule." lightbox="./media/stream-analytics-autoscale/save-scale-rule-streaming-units-limits.png" :::
9797

9898
> [!NOTE]
99-
> Flapping refers to a loop condition that causes a series of opposing scale events. Flapping happens when a scale event triggers the opposite scale event. Refer to [this](azure/azure-monitor/autoscale/autoscale-flapping) article which describes flapping in autoscale and how to avoid it.
99+
> Flapping refers to a loop condition that causes a series of opposing scale events. Flapping happens when a scale event triggers the opposite scale event. Refer to [this](/azure/azure-monitor/autoscale/autoscale-flapping) article which describes flapping in autoscale and how to avoid it.
100100
101101
### Scale to specific number of streaming units
102102

articles/trusted-signing/how-to-change-sku.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -68,12 +68,12 @@ az trustedsigning update -n MyAccount -g MyResourceGroup --sku Premium
6868
View and estimate the cost of your Trusted Signing resource usage.
6969
1. In the Azure portal, search **Subscriptions**.
7070
2. Select the **Subscription**, where you have created Trusted Signing resources.
71-
3. Select Cost Management from the menu on the left. Learn more about using [Cost Management](azure/cost-management-billing/costs/).
71+
3. Select Cost Management from the menu on the left. Learn more about using [Cost Management](/azure/cost-management-billing/costs/).
7272
4. For Trusted Signing, you can see costs associated to your Trusted Signing account.
7373

7474
**Billing**
7575

7676
View Invoice for Trusted Signing service.
7777
1. In the Azure portal, search **Subscriptions**.
7878
2. Select the **Subscription**, where you have created Trusted Signing resources.
79-
3. Select Billing from the menu on the left. Learn more about [Billing](azure/cost-management-billing/manage/).
79+
3. Select Billing from the menu on the left. Learn more about [Billing](/azure/cost-management-billing/manage/).

0 commit comments

Comments
 (0)