Skip to content

Commit 4983f3c

Browse files
Merge pull request #2380 from MicrosoftDocs/main
Auto Publish – main to live - 2025-10-06 17:00 UTC
2 parents 519d7e7 + 3277a1d commit 4983f3c

10 files changed

+11
-11
lines changed

articles/service-fabric/cloud-services-to-service-fabric-migration-guide.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -580,7 +580,7 @@ You can also use [Azure Pipelines for automated deployments](how-to-managed-clus
580580

581581
### Monitoring and diagnostics
582582

583-
> [!IMPORTANT]
583+
> [!WARNING]
584584
> Application Insights for the Service Fabric SDK is no longer supported.
585585
586586
[Visualize your cluster with Service Fabric Explorer](service-fabric-visualizing-your-cluster.md)

articles/service-fabric/monitor-service-fabric.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.service: azure-service-fabric
1414

1515
[!INCLUDE [horz-monitor-intro](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-intro.md)]
1616

17-
> [!IMPORTANT]
17+
> [!WARNING]
1818
> Application Insights for the Service Fabric SDK is no longer supported.
1919
2020
## Azure Service Fabric monitoring

articles/service-fabric/service-fabric-best-practices-monitoring.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.date: 09/29/2025
1414

1515
[Monitoring and diagnostics](monitor-service-fabric.md) are critical to developing, testing, and deploying workloads in any cloud environment. For example, you can track how your applications are used, the actions taken by the Service Fabric platform, your resource utilization with performance counters, and the overall health of your cluster. You can use this information to diagnose and correct issues, and prevent them from occurring in the future.
1616

17-
> [!IMPORTANT]
17+
> [!WARNING]
1818
> Application Insights for the Service Fabric SDK is no longer supported.
1919
2020
## Application monitoring

articles/service-fabric/service-fabric-cluster-creation-via-portal.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ ms.date: 09/29/2025
1616
> * [Azure Resource Manager](service-fabric-cluster-creation-via-arm.md)
1717
> * [Azure portal](service-fabric-cluster-creation-via-portal.md)
1818
19-
> [!IMPORTANT]
19+
> [!WARNING]
2020
> Application Insights for the Service Fabric SDK is no longer supported.
2121
2222
This article is a step-by-step guide that walks you through the steps of setting up a Service Fabric cluster (Linux or Windows) in Azure using the Azure portal. This guide walks you through the following steps:

articles/service-fabric/service-fabric-diagnostics-common-scenarios.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.date: 09/29/2025
1414

1515
This article illustrates common scenarios users have encountered in the area of monitoring and diagnostics with Service Fabric. The scenarios presented cover all three layers of service fabric: Application, Cluster, and Infrastructure. Each solution uses Application Insights and Azure Monitor logs, Azure monitoring tools, to complete each scenario. The steps in each solution give users an introduction on how to use Application Insights and Azure Monitor logs in the context of Service Fabric.
1616

17-
> [!IMPORTANT]
17+
> [!WARNING]
1818
> Application Insights for the Service Fabric SDK is no longer supported.
1919
2020
## Prerequisites and Recommendations

articles/service-fabric/service-fabric-diagnostics-event-aggregation-eventflow.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.date: 09/29/2025
1414

1515
[Microsoft Diagnostics EventFlow](https://github.com/Azure/diagnostics-eventflow) can route events from a node to one or more monitoring destinations. Because it's included as a NuGet package in your service project, EventFlow code and configuration travel with the service, eliminating the per-node configuration issue mentioned earlier about Azure Diagnostics. EventFlow runs within your service process, and connects directly to the configured outputs. Because of the direct connection, EventFlow works for Azure, container, and on-premises service deployments. Be careful if you run EventFlow in high-density scenarios, such as in a container, because each EventFlow pipeline makes an external connection. So, if you host several processes, you get several outbound connections! This isn't as much a concern for Service Fabric applications, because all replicas of a `ServiceType` run in the same process, and this limits the number of outbound connections. EventFlow also offers event filtering, so that only the events that match the specified filter are sent.
1616

17-
> [!IMPORTANT]
17+
> [!WARNING]
1818
> Application Insights for the Service Fabric SDK is no longer supported.
1919
2020
## Set up EventFlow

articles/service-fabric/service-fabric-diagnostics-event-aggregation-lad.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ ms.date: 09/29/2025
1717
> * [Windows](service-fabric-diagnostics-event-aggregation-wad.md)
1818
> * [Linux](service-fabric-diagnostics-event-aggregation-lad.md)
1919
20-
> [!IMPORTANT]
20+
> [!WARNING]
2121
> Application Insights for the Service Fabric SDK is no longer supported.
2222
2323
When you're running an Azure Service Fabric cluster, it's a good idea to collect the logs from all the nodes in a central location. Having the logs in a central location helps you analyze and troubleshoot issues in your cluster, or issues in the applications and services running in that cluster.

articles/service-fabric/service-fabric-diagnostics-event-aggregation-wad.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ One way to upload and collect logs is to use the Microsoft Azure Diagnostics (WA
2323

2424
[!INCLUDE [updated-for-az](~/reusable-content/ce-skilling/azure/includes/updated-for-az.md)]
2525

26-
> [!IMPORTANT]
26+
> [!WARNING]
2727
> Application Insights for the Service Fabric SDK is no longer supported.
2828
2929
## Prerequisites
@@ -310,7 +310,7 @@ If you're using an Application Insights sink, as described in the section below,
310310

311311
### Configuring Application Insights with WAD
312312

313-
> [!IMPORTANT]
313+
> [!WARNING]
314314
> Application Insights for the Service Fabric SDK is no longer supported.
315315
316316
There are two primary ways to send data from WAD to Azure Application Insights, which is achieved by adding an Application Insights sink to the WAD configuration, through the Azure portal or through an Azure Resource Manager template.

articles/service-fabric/service-fabric-diagnostics-event-analysis-appinsights.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.date: 09/29/2025
1414

1515
Part of Azure Monitor, Application Insights is an extensible platform for application monitoring and diagnostics. It includes a powerful analytics and querying tool, customizable dashboard and visualizations, and further options including automated alerting. Application Insights's integration with Service Fabric includes tooling experiences for Visual Studio and Azure portal, as well as Service Fabric specific metrics, providing a comprehensive out-of-the-box logging experience. Though many logs are automatically created and collected for you with Application Insights, we recommend that you add further custom logging to your applications to create a richer diagnostics experience.
1616

17-
> [!IMPORTANT]
17+
> [!WARNING]
1818
> Application Insights for the Service Fabric SDK is no longer supported.
1919
2020
This article helps address the following common questions:

articles/service-fabric/service-fabric-tutorial-monitoring-aspnet.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.date: 09/29/2025
1414

1515
This tutorial is *part five* in a series. It walks through the steps to configure monitoring and diagnostics for an ASP.NET Core application running on an Azure Service Fabric cluster by using Application Insights. You collect telemetry from the application that's developed in [part one of the tutorial series](service-fabric-tutorial-create-dotnet-app.md).
1616

17-
> [!IMPORTANT]
17+
> [!WARNING]
1818
> Application Insights for the Service Fabric SDK is no longer supported.
1919
2020
In this tutorial, you learn how to:

0 commit comments

Comments
 (0)