Skip to content

Commit 2547c9c

Browse files
author
Jill Grant
authored
Merge pull request #265084 from KennedyDenMSFT/US85911
Removed /monitor-reference.md, updated redirects
2 parents 7844b87 + 80036de commit 2547c9c

12 files changed

+20
-112
lines changed

.openpublishing.redirection.azure-monitor.json

Lines changed: 8 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2287,17 +2287,17 @@
22872287
},
22882288
{
22892289
"source_path_from_root": "/articles/azure-monitor/insights/solutions-inventory.md",
2290-
"redirect_url": "/azure/azure-monitor/monitor-reference",
2290+
"redirect_url": "/azure/azure-monitor/overview",
22912291
"redirect_document_id": false
22922292
},
22932293
{
22942294
"source_path_from_root": "/articles/monitoring/monitoring-solutions-inventory.md",
2295-
"redirect_url": "/azure/azure-monitor/monitor-reference",
2295+
"redirect_url": "/azure/azure-monitor/overview",
22962296
"redirect_document_id": false
22972297
},
22982298
{
22992299
"source_path_from_root": "/articles/azure-monitor/platform/data-locations.md",
2300-
"redirect_url": "/azure/azure-monitor/monitor-reference/",
2300+
"redirect_url": "/azure/azure-monitor/overview/",
23012301
"redirect_document_id": false
23022302
},
23032303
{
@@ -6598,6 +6598,11 @@
65986598
"source_path_from_root": "/articles/azure-monitor/app/java-standalone-arguments.md",
65996599
"redirect_url": "/azure/azure-monitor/app/java-get-started-supplemental",
66006600
"redirect_document_id": true
6601+
},
6602+
{
6603+
"source_path_from_root": "/articles/azure-monitor/monitor-reference.md",
6604+
"redirect_url": "/azure/azure-monitor/overview",
6605+
"redirect_document_id": false
66016606
}
66026607
]
66036608
}

articles/azure-monitor/agents/agent-data-sources.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,7 @@ Data source configurations are delivered to agents that are directly connected t
4848

4949
For System Center Operations Manager agents in a connected management group, data source configurations are translated into management packs and delivered to the management group every 5 minutes by default. The agent downloads the management pack like any other and collects the specified data. Depending on the data source, the data will either be sent to a management server, which forwards the data to the Azure Monitor, or the agent will send the data to Azure Monitor without going through the management server.
5050

51-
For more information, see [Data collection details for monitoring solutions in Azure](../monitor-reference.md). You can read about details of connecting Operations Manager and Azure Monitor and modifying the frequency that configuration is delivered at [Configure integration with System Center Operations Manager](./om-agents.md).
51+
For more information, see [Data collection in Azure Monitor](../essentials/data-collection.md). You can read about details of connecting Operations Manager and Azure Monitor and modifying the frequency that configuration is delivered at [Configure integration with System Center Operations Manager](./om-agents.md).
5252

5353
If the agent is unable to connect to Azure Monitor or Operations Manager, it will continue to collect data that it will deliver when it establishes a connection. Data can be lost if the amount of data reaches the maximum cache size for the client, or if the agent can't establish a connection within 24 hours.
5454

articles/azure-monitor/agents/log-analytics-agent.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -75,7 +75,7 @@ This section explains how to install the Log Analytics agent on different types
7575

7676
## Data collected
7777

78-
The following table lists the types of data you can configure a Log Analytics workspace to collect from all connected agents. For a list of insights and solutions that use the Log Analytics agent to collect other kinds of data, see [What is monitored by Azure Monitor?](../monitor-reference.md).
78+
The following table lists the types of data you can configure a Log Analytics workspace to collect from all connected agents.
7979

8080
| Data Source | Description |
8181
| --- | --- |

articles/azure-monitor/best-practices-data-collection.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,7 @@ Insights provide a specialized monitoring experience for a particular service. T
6666

6767
There's no cost for insights, but you might be charged for any data they collect.
6868

69-
See [What is monitored by Azure Monitor?](monitor-reference.md) for a list of available insights and solutions in Azure Monitor. See the documentation for each for any unique configuration or pricing information.
69+
See [Azure Monitor Insights overview](insights/insights-overview.md) for a list of available insights and solutions in Azure Monitor. See the documentation for each for any unique configuration or pricing information.
7070

7171
> [!IMPORTANT]
7272
> The following insights are much more complex than others and have more guidance for their configuration:

articles/azure-monitor/data-sources.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ Some of these data sources use the [new data ingestion pipeline](essentials/data
2929
3030
## Application tiers
3131

32-
Sources of monitoring data from Azure applications can be organized into tiers, the highest tiers being your application itself and the lower tiers being components of Azure platform. The method of accessing data from each tier varies. The application tiers are summarized in the table below, and the sources of monitoring data in each tier are presented in the following sections. See [Monitoring data locations in Azure](monitor-reference.md) for a description of each data location and how you can access its data.
32+
Sources of monitoring data from Azure applications can be organized into tiers, the highest tiers being your application itself and the lower tiers being components of Azure platform. The method of accessing data from each tier varies. The application tiers are summarized in the table below, and the sources of monitoring data in each tier are presented in the following sections.
3333

3434
:::image type="content" source="media/overview/overview-simple-20230707-opt.svg" alt-text="Diagram that shows an overview of Azure Monitor with data sources on the left sending data to a central data platform and features of Azure Monitor on the right that use the collected data." border="false" lightbox="media/overview/overview-blowout-20230707-opt.svg":::
3535

@@ -193,7 +193,7 @@ When you enable Application Insights for an application by installing an instrum
193193
| | Debug snapshot data that is captured for a subset of exceptions is stored in Azure Storage. Use Application Insights in the Azure portal to download for local analysis. | [How snapshots work](app/snapshot-debugger.md#how-snapshots-work) |
194194

195195
## Insights
196-
[Insights](monitor-reference.md) collect data to provide additional insights into the operation of a particular service or application. They may address resources in different application tiers and even multiple tiers.
196+
[Insights](insights/insights-overview.md) collect data to provide additional insights into the operation of a particular service or application. They may address resources in different application tiers and even multiple tiers.
197197

198198

199199
### Container insights
@@ -234,4 +234,3 @@ Other services in Azure write data to the Azure Monitor data platform. This allo
234234
## Next steps
235235

236236
- Learn more about the [types of monitoring data collected by Azure Monitor](data-platform.md) and how to view and analyze this data.
237-
- List the [different locations where Azure resources store data](monitor-reference.md) and how you can access it.

articles/azure-monitor/essentials/data-platform-metrics.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.author: bwren
1212

1313
# Azure Monitor Metrics overview
1414

15-
Azure Monitor Metrics is a feature of Azure Monitor that collects numeric data from [monitored resources](../monitor-reference.md) into a time-series database. Metrics are numerical values that are collected at regular intervals and describe some aspect of a system at a particular time.
15+
Azure Monitor Metrics is a feature of Azure Monitor that collects numeric data from monitored resources into a time-series database. Metrics are numerical values that are collected at regular intervals and describe some aspect of a system at a particular time.
1616

1717
> [!NOTE]
1818
> Azure Monitor Metrics is one half of the data platform that supports Azure Monitor. The other half is [Azure Monitor Logs](../logs/data-platform-logs.md), which collects and organizes log and performance data. You can analyze that data by using a rich query language.
@@ -54,9 +54,8 @@ Azure Monitor collects metrics from the following sources. After these metrics a
5454
- **Custom metrics**: You can define metrics in addition to the standard metrics that are automatically available. You can [define custom metrics in your application](../app/api-custom-events-metrics.md) that's monitored by Application Insights. You can also create custom metrics for an Azure service by using the [custom metrics API](./metrics-store-custom-rest-api.md).
5555
- **Kubernetes clusters**: Kubernetes clusters typically send metric data to a local Prometheus server that you must maintain. [Azure Monitor managed service for Prometheus ](prometheus-metrics-overview.md) provides a managed service that collects metrics from Kubernetes clusters and store them in Azure Monitor Metrics.
5656

57-
For a complete list of data sources that can send data to Azure Monitor Metrics, see [What is monitored by Azure Monitor?](../monitor-reference.md).
57+
## REST API
5858

59-
## REST API
6059
Azure Monitor provides REST APIs that allow you to get data in and out of Azure Monitor Metrics.
6160
- **Custom metrics API** - [Custom metrics](./metrics-custom-overview.md) allow you to load your own metrics into the Azure Monitor Metrics database. Those metrics can then be used by the same analysis tools that process Azure Monitor platform metrics.
6261
- **Azure Monitor Metrics REST API** - Allows you to access Azure Monitor platform metrics definitions and values. For more information, see [Azure Monitor REST API](/rest/api/monitor/metrics/list). For information on how to use the API, see the [Azure monitoring REST API walkthrough](./rest-api-walkthrough.md).

articles/azure-monitor/essentials/monitor-azure-resource.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -93,7 +93,7 @@ To learn how to create a diagnostic setting, see [Collect and analyze resource l
9393

9494
## Insights
9595

96-
The **Insights** menu item opens the insight for the resource if the Azure service has one. [Insights](../monitor-reference.md) provide a customized monitoring experience built on the Azure Monitor data platform and standard features.
96+
The **Insights** menu item opens the insight for the resource if the Azure service has one. [Insights](../insights/insights-overview.md) provide a customized monitoring experience built on the Azure Monitor data platform and standard features.
9797

9898
For a list of insights that are available and links to their documentation, see [Insights](../insights/insights-overview.md) and [core solutions](/previous-versions/azure/azure-monitor/insights/solutions).
9999
<!-- convertborder later -->

articles/azure-monitor/getting-started.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ This section provides answers to common questions.
4040

4141
### How do I enable Azure Monitor?
4242

43-
Azure Monitor is enabled the moment that you create a new Azure subscription, and [activity log](./essentials/platform-logs-overview.md) and platform [metrics](essentials/data-platform-metrics.md) are automatically collected. Create [diagnostic settings](essentials/diagnostic-settings.md) to collect more detailed information about the operation of your Azure resources, and add [monitoring solutions](/previous-versions/azure/azure-monitor/insights/solutions) and [insights](./monitor-reference.md) to provide extra analysis on collected data for particular services.
43+
Azure Monitor is enabled the moment that you create a new Azure subscription, and [activity log](./essentials/platform-logs-overview.md) and platform [metrics](essentials/data-platform-metrics.md) are automatically collected. Create [diagnostic settings](essentials/diagnostic-settings.md) to collect more detailed information about the operation of your Azure resources, and add monitoring solutions to provide extra analysis on collected data for particular services.
4444

4545
### How do I access Azure Monitor?
4646

articles/azure-monitor/insights/insights-overview.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -62,4 +62,3 @@ The following table lists the available curated visualizations and information a
6262
## Next steps
6363

6464
- Reference some of the insights listed above to review their functionality
65-
- Understand [what Azure Monitor can monitor](../monitor-reference.md)

articles/azure-monitor/logs/data-platform-logs.md

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,13 @@
11
---
22
title: Azure Monitor Logs
3-
description: Learn the basics of Azure Monitor Logs, which is used for advanced analysis of monitoring data.
3+
description: Learn the basics of Azure Monitor Logs, which are used for advanced analysis of monitoring data.
44
ms.topic: conceptual
55
ms.date: 09/14/2023
66
ms.author: bwren
77
---
88

99
# Azure Monitor Logs overview
10-
Azure Monitor Logs is a feature of Azure Monitor that collects and organizes log and performance data from [monitored resources](../monitor-reference.md). Several features of Azure Monitor store their data in Logs and present this data in various ways to assist you in monitoring the performance and availability of your cloud and hybrid applications and their supporting components.
10+
Azure Monitor Logs is a feature of Azure Monitor that collects and organizes log and performance data from monitored resources. Several features of Azure Monitor store their data in Logs and present this data in various ways to assist you in monitoring the performance and availability of your cloud and hybrid applications and their supporting components.
1111

1212
Along with using existing Azure Monitor features, you can analyze Logs data by using a sophisticated query language that's capable of quickly analyzing millions of records. You might perform a simple query that retrieves a specific set of records or perform sophisticated data analysis to identify critical patterns in your monitoring data. Work with log queries and their results interactively by using Log Analytics, use them in alert rules to be proactively notified of issues, or visualize their results in a workbook or dashboard.
1313

@@ -44,8 +44,6 @@ This configuration will be different depending on the data source. For example:
4444
> [!IMPORTANT]
4545
> Most data collection in Logs will incur ingestion and retention costs. See [Azure Monitor pricing](https://azure.microsoft.com/pricing/details/monitor/) before you enable any data collection.
4646
47-
For a complete list of data sources that you can configure to send data to Azure Monitor Logs, see [What is monitored by Azure Monitor?](../monitor-reference.md).
48-
4947
## Log Analytics workspaces
5048
Azure Monitor Logs stores the data that it collects in one or more [Log Analytics workspaces](./workspace-design.md). You must create at least one workspace to use Azure Monitor Logs. For a description of Log Analytics workspaces, see [Log Analytics workspace overview](log-analytics-workspace-overview.md).
5149

@@ -78,7 +76,7 @@ The experience of using Log Analytics to work with Azure Monitor queries in the
7876

7977
[Security monitoring](../best-practices-plan.md#security-monitoring) in Azure is performed by [Microsoft Sentinel](../../sentinel/overview.md) and [Microsoft Defender for Cloud](../../defender-for-cloud/defender-for-cloud-introduction.md).
8078

81-
These services store their data in Azure Monitor Logs so that it can be analyzed with other log data collected by Azure Monitor. For more information, see [Product integrations](../monitor-reference.md#product-integrations) and [Other services](../data-sources.md#other-services).
79+
These services store their data in Azure Monitor Logs so that it can be analyzed with other log data collected by Azure Monitor.
8280

8381
### Learn more
8482

0 commit comments

Comments
 (0)