Skip to content

Commit e5297fd

Browse files
authored
Update service-fabric-diagnostics-how-to-setup-wad.md
1 parent d72fed9 commit e5297fd

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/service-fabric/service-fabric-diagnostics-how-to-setup-wad.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@
2323
- [Windows](service-fabric-diagnostics-how-to-setup-wad.md)
2424
- [Linux](service-fabric-diagnostics-how-to-setup-lad.md)
2525

26-
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 makes it easy to analyze and troubleshoot issues in your cluster or in the applications and services running in that cluster.
26+
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.
2727

2828
One way to upload and collect logs is to use the Azure Diagnostics extension, which uploads logs to Azure Storage. The logs are not that useful directly in storage. But you can use an external process to read the events from storage and place them in a product such as [Log Analytics](../log-analytics/log-analytics-service-fabric.md), [Elastic Search](service-fabric-diagnostic-how-to-use-elasticsearch.md), or another log-parsing solution.
2929

0 commit comments

Comments
 (0)