Skip to content

Commit ad2fba7

Browse files
Merge pull request #230012 from v-jbasden/v-jbasden-delete-legacy-retired-articles
Deleting legacy and retired articles
2 parents 7f25911 + 299a4f0 commit ad2fba7

File tree

421 files changed

+401
-10794
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

421 files changed

+401
-10794
lines changed

.openpublishing.redirection.azure-monitor.json

Lines changed: 216 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -92,7 +92,7 @@
9292
},
9393
{
9494
"source_path_from_root": "/articles/azure-monitor/app/legacy-pricing.md",
95-
"redirect_url": "/azure/azure-monitor/best-practices-cost",
95+
"redirect_url": "/previous-versions/azure/azure-monitor/app/legacy-pricing",
9696
"redirect_document_id": false
9797
},
9898
{
@@ -608,7 +608,7 @@
608608
},
609609
{
610610
"source_path_from_root": "/articles/azure-monitor/app/cloudservices.md" ,
611-
"redirect_url": "/azure/azure-monitor/app/azure-web-apps-net-core",
611+
"redirect_url": "/previous-versions/azure/azure-monitor/app/cloudservices",
612612
"redirect_document_id": false
613613
},
614614
{
@@ -5786,6 +5786,220 @@
57865786
"source_path_from_root": "/articles/azure-monitor/app/java-in-process-agent.md",
57875787
"redirect_url": "/azure/azure-monitor/app/opentelemetry-enable",
57885788
"redirect_document_id": false
5789+
},
5790+
{
5791+
"source_path_from_root": "/articles/azure-monitor/insights/solutions.md",
5792+
"redirect_url": "/previous-versions/azure/azure-monitor/insights/solutions",
5793+
"redirect_document_id": false
5794+
},
5795+
{
5796+
"source_path_from_root": "/articles/azure-monitor/insights/solution-targeting.md",
5797+
"redirect_url": "/previous-versions/azure/azure-monitor/insights/solution-targeting",
5798+
"redirect_document_id": false
5799+
},
5800+
{
5801+
"source_path_from_root": "/articles/azure-monitor/insights/ad-assessment.md",
5802+
"redirect_url": "/previous-versions/azure/azure-monitor/insights/ad-assessment",
5803+
"redirect_document_id": false
5804+
},
5805+
{
5806+
"source_path_from_root": "/articles/azure-monitor/insights/ad-replication-status.md",
5807+
"redirect_url": "/previous-versions/azure/azure-monitor/insights/ad-replication-status",
5808+
"redirect_document_id": false
5809+
},
5810+
{
5811+
"source_path_from_root": "/articles/azure-monitor/insights/capacity-performance.md",
5812+
"redirect_url": "/previous-versions/azure/azure-monitor/insights/capacity-performance",
5813+
"redirect_document_id": false
5814+
},
5815+
{
5816+
"source_path_from_root": "/articles/azure-monitor/containers/containers.md",
5817+
"redirect_url": "/previous-versions/azure/azure-monitor/containers/containers",
5818+
"redirect_document_id": false
5819+
},
5820+
{
5821+
"source_path_from_root": "/articles/azure-monitor/insights/solution-office-365.md",
5822+
"redirect_url": "/previous-versions/azure/azure-monitor/insights/solution-office-365",
5823+
"redirect_document_id": false
5824+
},
5825+
{
5826+
"source_path_from_root": "/articles/azure-monitor/vm/service-map.md",
5827+
"redirect_url": "/previous-versions/azure/azure-monitor/vm/service-map",
5828+
"redirect_document_id": false
5829+
},
5830+
{
5831+
"source_path_from_root": "/articles/azure-monitor/vm/service-map-scom.md",
5832+
"redirect_url": "/previous-versions/azure/azure-monitor/vm/service-map-scom",
5833+
"redirect_document_id": false
5834+
},
5835+
{
5836+
"source_path_from_root": "/articles/azure-monitor/insights/azure-sql.md",
5837+
"redirect_url": "/previous-versions/azure/azure-monitor/insights/azure-sql",
5838+
"redirect_document_id": false
5839+
},
5840+
{
5841+
"source_path_from_root": "/articles/azure-monitor/insights/sql-assessment.md",
5842+
"redirect_url": "/previous-versions/azure/azure-monitor/insights/sql-assessment",
5843+
"redirect_document_id": false
5844+
},
5845+
{
5846+
"source_path_from_root": "/articles/azure-monitor/insights/surface-hubs.md",
5847+
"redirect_url": "/previous-versions/azure/azure-monitor/insights/surface-hubs",
5848+
"redirect_document_id": false
5849+
},
5850+
{
5851+
"source_path_from_root": "/articles/azure-monitor/insights/vmware.md",
5852+
"redirect_url": "/previous-versions/azure/azure-monitor/insights/vmware",
5853+
"redirect_document_id": false
5854+
},{
5855+
"source_path_from_root": "/articles/azure-monitor/insights/wire-data.md",
5856+
"redirect_url": "/previous-versions/azure/azure-monitor/insights/wire-data",
5857+
"redirect_document_id": false
5858+
},
5859+
{
5860+
"source_path_from_root": "/articles/azure-monitor/insights/alert-management-solution.md",
5861+
"redirect_url": "/previous-versions/azure/azure-monitor/insights/alert-management-solution",
5862+
"redirect_document_id": false
5863+
},
5864+
{
5865+
"source_path_from_root": "/articles/azure-monitor/insights/azure-networking-analytics.md",
5866+
"redirect_url": "/previous-versions/azure/azure-monitor/insights/azure-networking-analytics",
5867+
"redirect_document_id": false
5868+
},
5869+
{
5870+
"source_path_from_root": "/articles/azure-monitor/insights/dns-analytics.md",
5871+
"redirect_url": "/previous-versions/azure/azure-monitor/insights/dns-analytics",
5872+
"redirect_document_id": false
5873+
},
5874+
{
5875+
"source_path_from_root": "/articles/azure-monitor/insights/network-performance-monitor.md",
5876+
"redirect_url": "/previous-versions/azure/azure-monitor/insights/network-performance-monitor",
5877+
"redirect_document_id": false
5878+
},
5879+
{
5880+
"source_path_from_root": "/articles/azure-monitor/insights/network-performance-monitor-performance-monitor.md",
5881+
"redirect_url": "/previous-versions/azure/azure-monitor/insights/network-performance-monitor-performance-monitor",
5882+
"redirect_document_id": false
5883+
},
5884+
{
5885+
"source_path_from_root": "/articles/azure-monitor/insights/network-performance-monitor-service-connectivity.md",
5886+
"redirect_url": "/previous-versions/azure/azure-monitor/insights/network-performance-monitor-service-connectivity",
5887+
"redirect_document_id": false
5888+
},
5889+
{
5890+
"source_path_from_root": "/articles/azure-monitor/insights/network-performance-monitor-expressroute.md",
5891+
"redirect_url": "/previous-versions/azure/azure-monitor/insights/network-performance-monitor-expressroute",
5892+
"redirect_document_id": false
5893+
},
5894+
{
5895+
"source_path_from_root": "/articles/azure-monitor/insights/network-performance-monitor-pricing-faq.yml",
5896+
"redirect_url": "/previous-versions/azure/azure-monitor/insights/network-performance-monitor-pricing-faq",
5897+
"redirect_document_id": false
5898+
},
5899+
{
5900+
"source_path_from_root": "/articles/azure-monitor/insights/network-performance-monitor-faq.yml",
5901+
"redirect_url": "/previous-versions/azure/azure-monitor/insights/network-performance-monitor-faq",
5902+
"redirect_document_id": false
5903+
},
5904+
{
5905+
"source_path_from_root": "/articles/azure-monitor/insights/azure-web-apps-analytics.md",
5906+
"redirect_url": "/previous-versions/azure/azure-monitor/insights/azure-web-apps-analytics",
5907+
"redirect_document_id": false
5908+
},
5909+
{
5910+
"source_path_from_root": "/articles/azure-monitor/logs/app-insights-connector.md",
5911+
"redirect_url": "/previous-versions/azure/azure-monitor/logs/app-insights-connector",
5912+
"redirect_document_id": false
5913+
},
5914+
{
5915+
"source_path_from_root": "/articles/azure-monitor/logs/oms-portal-transition.md",
5916+
"redirect_url": "/previous-versions/azure/azure-monitor/logs/oms-portal-transition",
5917+
"redirect_document_id": false
5918+
},
5919+
{
5920+
"source_path_from_root": "/articles/azure-monitor/insights/azure-key-vault-deprecated.md",
5921+
"redirect_url": "/previous-versions/azure/azure-monitor/insights/azure-key-vault-deprecated",
5922+
"redirect_document_id": false
5923+
},
5924+
{
5925+
"source_path_from_root": "/articles/azure-monitor/app/deprecated-java-2x.md",
5926+
"redirect_url": "/previous-versions/azure/azure-monitor/app/deprecated-java-2x",
5927+
"redirect_document_id": false
5928+
},
5929+
{
5930+
"source_path_from_root": "/articles/azure-monitor/app/create-new-resource.md",
5931+
"redirect_url": "/previous-versions/azure/azure-monitor/app/create-new-resource",
5932+
"redirect_document_id": false
5933+
},
5934+
{
5935+
"source_path_from_root": "/articles/azure-monitor/essentials/classic-api-retirement-metrics-autoscale.md",
5936+
"redirect_url": "/previous-versions/azure/azure-monitor/essentials/classic-api-retirement-metrics-autoscale",
5937+
"redirect_document_id": false
5938+
},
5939+
{
5940+
"source_path_from_root": "/articles/azure-monitor/essentials/metrics-supported-export-diagnostic-settings.md",
5941+
"redirect_url": "/previous-versions/azure/azure-monitor/essentials/metrics-supported-export-diagnostic-settings",
5942+
"redirect_document_id": false
5943+
},
5944+
{
5945+
"source_path_from_root": "/articles/azure-monitor/essentials/portal-disk-metrics-deprecation.md",
5946+
"redirect_url": "/previous-versions/azure/azure-monitor/essentials/portal-disk-metrics-deprecation",
5947+
"redirect_document_id": false
5948+
},
5949+
{
5950+
"source_path_from_root": "/articles/azure-monitor/essentials/resource-logs-blob-format.md",
5951+
"redirect_url": "/previous-versions/azure/azure-monitor/essentials/resource-logs-blob-format",
5952+
"redirect_document_id": false
5953+
},
5954+
{
5955+
"source_path_from_root": "/articles/azure-monitor/alerts/monitoring-classic-retirement.md",
5956+
"redirect_url": "/previous-versions/azure/azure-monitor/alerts/monitoring-classic-retirement",
5957+
"redirect_document_id": false
5958+
},
5959+
{
5960+
"source_path_from_root": "/articles/azure-monitor/alerts/alerts-log-api-switch.md",
5961+
"redirect_url": "/previous-versions/azure/azure-monitor/alerts/alerts-log-api-switch",
5962+
"redirect_document_id": false
5963+
},
5964+
{
5965+
"source_path_from_root": "/articles/azure-monitor/visualize/view-designer.md",
5966+
"redirect_url": "/previous-versions/azure/azure-monitor/visualize/view-designer",
5967+
"redirect_document_id": false
5968+
},
5969+
{
5970+
"source_path_from_root": "/articles/azure-monitor/visualize/view-designer-tiles.md",
5971+
"redirect_url": "/previous-versions/azure/azure-monitor/visualize/view-designer-tiles",
5972+
"redirect_document_id": false
5973+
},
5974+
{
5975+
"source_path_from_root": "/articles/azure-monitor/visualize/view-designer-parts.md",
5976+
"redirect_url": "/previous-versions/azure/azure-monitor/visualize/view-designer-parts",
5977+
"redirect_document_id": false
5978+
},
5979+
{
5980+
"source_path_from_root": "/articles/azure-monitor/visualize/view-designer-filters.md",
5981+
"redirect_url": "/previous-versions/azure/azure-monitor/visualize/view-designer-filters",
5982+
"redirect_document_id": false
5983+
},
5984+
{
5985+
"source_path_from_root": "/articles/azure-monitor/app/export-telemetry.md",
5986+
"redirect_url": "/previous-versions/azure/azure-monitor/app/export-telemetry",
5987+
"redirect_document_id": false
5988+
},
5989+
{
5990+
"source_path_from_root": "/articles/azure-monitor/app/sharepoint.md",
5991+
"redirect_url": "/previous-versions/azure/azure-monitor/app/sharepoint",
5992+
"redirect_document_id": false
5993+
},
5994+
{
5995+
"source_path_from_root": "/articles/azure-monitor/app/monitor-web-app-availability.md",
5996+
"redirect_url": "/previous-versions/azure/azure-monitor/app/monitor-web-app-availability",
5997+
"redirect_document_id": false
5998+
},
5999+
{
6000+
"source_path_from_root": "/articles/azure-monitor/app/availability-multistep.md",
6001+
"redirect_url": "/previous-versions/azure/azure-monitor/app/availability-multistep",
6002+
"redirect_document_id": false
57896003
}
57906004
]
57916005
}

articles/active-directory-b2c/analytics-with-application-insights.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -51,7 +51,7 @@ When you use Application Insights, consider the following:
5151

5252
## Create an Application Insights resource
5353

54-
When you use Application Insights with Azure AD B2C, all you need to do is create a resource and get the instrumentation key. For information, see [Create an Application Insights resource](../azure-monitor/app/create-new-resource.md).
54+
When you use Application Insights with Azure AD B2C, all you need to do is create a resource and get the instrumentation key. For information, see [Create an Application Insights resource](/previous-versions/azure/azure-monitor/app/create-new-resource).
5555

5656
1. Sign in to the [Azure portal](https://portal.azure.com/).
5757
1. Make sure you're using the directory that has your Azure AD subscription, and not your Azure AD B2C directory. Select the **Directories + subscriptions** icon in the portal toolbar.

articles/advisor/advisor-performance-recommendations.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -83,7 +83,7 @@ Migrate your storage account deployment model to Azure Resource Manager to take
8383
Advisor identifies any stand-alone storage accounts that are using the classic deployment model and recommends migrating to the Resource Manager deployment model.
8484

8585
> [!NOTE]
86-
> Classic alerts in Azure Monitor were retired in August 2019. We recommended that you upgrade your classic storage account to use Resource Manager to retain alerting functionality with the new platform. For more information, see [classic alerts retirement](../azure-monitor/alerts/monitoring-classic-retirement.md#retirement-of-classic-monitoring-and-alerting-platform).
86+
> Classic alerts in Azure Monitor were retired in August 2019. We recommended that you upgrade your classic storage account to use Resource Manager to retain alerting functionality with the new platform. For more information, see [classic alerts retirement](/previous-versions/azure/azure-monitor/alerts/monitoring-classic-retirement#retirement-of-classic-monitoring-and-alerting-platform).
8787
8888
## Design your storage accounts to prevent reaching the maximum subscription limit
8989

articles/aks/intro-kubernetes.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -183,7 +183,7 @@ Learn more about deploying and managing AKS.
183183
[conf-com-node]: ../confidential-computing/confidential-nodes-aks-overview.md
184184
[aad]: managed-aad.md
185185
[aks-monitor]: monitor-aks.md
186-
[azure-monitor]: ../azure-monitor/containers/containers.md
186+
[azure-monitor]: /previous-versions/azure/azure-monitor/containers/containers
187187
[azure-logs]: ../azure-monitor/logs/log-analytics-overview.md
188188
[helm]: quickstart-helm.md
189189
[aks-best-practices]: best-practices.md

articles/api-management/api-management-howto-app-insights.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ You need an Azure API Management instance. [Create one](get-started-create-servi
2525

2626
## Create an Application Insights instance
2727

28-
To use Application Insights, [create an instance of the Application Insights service](../azure-monitor/app/create-new-resource.md). To create an instance using the Azure portal, see [Workspace-based Application Insights resources](../azure-monitor/app/create-workspace-resource.md).
28+
To use Application Insights, [create an instance of the Application Insights service](/previous-versions/azure/azure-monitor/app/create-new-resource). To create an instance using the Azure portal, see [Workspace-based Application Insights resources](../azure-monitor/app/create-workspace-resource.md).
2929

3030
> [!NOTE]
3131
> The Application Insights resource **can be** in a different subscription or even a different tenant than the API Management resource.
@@ -40,7 +40,7 @@ To use Application Insights, [create an instance of the Application Insights ser
4040
1. Select **+ Add**.
4141
:::image type="content" source="media/api-management-howto-app-insights/apim-app-insights-logger-1.png" alt-text="Screenshot that shows where to add a new connection":::
4242
1. Select the **Application Insights** instance you created earlier and provide a short description.
43-
1. To enable [availability monitoring](../azure-monitor/app/monitor-web-app-availability.md) of your API Management instance in Application Insights, select the **Add availability monitor** checkbox.
43+
1. To enable [availability monitoring](/previous-versions/azure/azure-monitor/app/monitor-web-app-availability) of your API Management instance in Application Insights, select the **Add availability monitor** checkbox.
4444
* This setting regularly validates whether the API Management gateway endpoint is responding.
4545
* Results appear in the **Availability** pane of the Application Insights instance.
4646
1. Select **Create**.

articles/app-service/configure-language-java.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -277,7 +277,7 @@ Azure Blob Storage logging for Linux based App Services can only be configured u
277277

278278
::: zone-end
279279

280-
If your application uses [Logback](https://logback.qos.ch/) or [Log4j](https://logging.apache.org/log4j) for tracing, you can forward these traces for review into Azure Application Insights using the logging framework configuration instructions in [Explore Java trace logs in Application Insights](../azure-monitor/app/deprecated-java-2x.md#explore-java-trace-logs-in-application-insights).
280+
If your application uses [Logback](https://logback.qos.ch/) or [Log4j](https://logging.apache.org/log4j) for tracing, you can forward these traces for review into Azure Application Insights using the logging framework configuration instructions in [Explore Java trace logs in Application Insights](/previous-versions/azure/azure-monitor/app/deprecated-java-2x#explore-java-trace-logs-in-application-insights).
281281

282282
> [!NOTE]
283283
> Due to known vulnerability [CVE-2021-44228](https://logging.apache.org/log4j/2.x/security.html), be sure to use Log4j version 2.16 or later.

0 commit comments

Comments
 (0)