Skip to content

Commit 2becde9

Browse files
authored
Merge branch 'MicrosoftDocs:main' into cosmos-archive-java-spark-v2
2 parents cffba86 + 9292a1a commit 2becde9

File tree

4 files changed

+3
-3
lines changed

4 files changed

+3
-3
lines changed
-786 Bytes
Loading

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -71,7 +71,7 @@ There are several [ways of sending custom metrics from the Application Insights
7171

7272
## Custom metrics dimensions and pre-aggregation
7373

74-
All metrics that you send using [OpenTelemetry](opentelemetry-add-modify.md), [trackMetric](./api-custom-events-metrics.md#trackmetric) or [GetMetric and TrackValue](./api-custom-events-metrics.md#getmetric) API calls are automatically stored in both logs and metrics stores. These metrics can be found in the customMetrics table in Application Insights and in Metrics Explorer under the Custom Metric Namespace called "azure.applicationinsights". Although the log-based version of your custom metric always retains all dimensions, the pre-aggregated version of the metric is stored by default with no dimensions. Retaining dimensions of custom metrics is a Preview feature that can be turned on via the [usage and estimated cost](../cost-usage.md#usage-and-estimated-costs) tab and selecting the **Enable alerting on custom metric dimensions** checkbox.
74+
All metrics that you send using [OpenTelemetry](opentelemetry-add-modify.md), [trackMetric](./api-custom-events-metrics.md#trackmetric) or [GetMetric and TrackValue](./api-custom-events-metrics.md#getmetric) API calls are automatically stored in both logs and metrics stores. These metrics can be found in the customMetrics table in Application Insights and in Metrics Explorer under the Custom Metric Namespace called "azure.applicationinsights". Although the log-based version of your custom metric always retains all dimensions, the pre-aggregated version of the metric is stored by default with no dimensions. Retaining dimensions of custom metrics is a Preview feature that can be turned on from the [Usage and estimated cost](../cost-usage.md#usage-and-estimated-costs) tab by selecting **With dimensions** under **Send custom metrics to Azure Metric Store**.
7575

7676
:::image type="content" source="./media/pre-aggregated-metrics-log-metrics/001-cost.png" lightbox="./media/pre-aggregated-metrics-log-metrics/001-cost.png" alt-text="Screenshot that shows usage and estimated costs.":::
7777

articles/load-balancer/cross-region-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.custom: template-concept, references_regions
1414

1515
# Cross-region (Global) Load Balancer
1616

17-
Azure Standard Load Balancer supports cross-region load balancing enabling geo-redundant High Availability scenarios such as:
17+
Azure Standard Load Balancer supports cross-region load balancing enabling geo-redundant high availability scenarios such as:
1818

1919
* Incoming traffic originating from multiple regions.
2020
* [Instant global failover](#regional-redundancy) to the next optimal regional deployment.

articles/managed-grafana/how-to-data-source-plugins-managed-identity.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.date: 12/08/2023
1010

1111
# How to manage data sources in Azure Managed Grafana
1212

13-
In this guide, you learn about data sources supported in each Azure Managed Grana plan and learn how to add, manage and remove these data sources.
13+
In this guide, you learn about data sources supported in each Azure Managed Grafana plan and learn how to add, manage and remove these data sources.
1414

1515
## Prerequisites
1616

0 commit comments

Comments
 (0)