diff --git a/articles/service-fabric/service-fabric-diagnostics-partners.md b/articles/service-fabric/service-fabric-diagnostics-partners.md index 018be361f0..b17af4c5e2 100644 --- a/articles/service-fabric/service-fabric-diagnostics-partners.md +++ b/articles/service-fabric/service-fabric-diagnostics-partners.md @@ -30,9 +30,9 @@ The Service Fabric integration with AppDynamics is at the application level. By New Relic is another Application Performance Management tool that integrates well with Service Fabric applications. You can install the New Relic NuGet packages and add specific environment variables in your manifest files to send your application telemetry to New Relic. Check out these [instructions](https://docs.newrelic.com/docs/agents/net-agent/azure-installation/install-net-agent-azure-service-fabric) to enable New Relic telemetry for your .NET Service Fabric applications. -## ELK +## Elasticsearch -The ELK stack is a collection of open-source technologies: Elasticsearch, Logstash, and Kibana. By using these technologies in combination, you can collect, store, and analyze Service Fabric monitoring and diagnostics data. We have a tutorial for how to do this with Service Fabric native Java applications [here](service-fabric-tutorial-java-elk.md). +Elasticsearch offers a powerful and flexible platform for observing and monitoring your Microsoft Fabric infrastructure. By leveraging Elasticsearch's robust search and analytics engine, you can ingest, store, and analyze diverse telemetry data, including logs, metrics, and traces, from your Service Fabric applications and the underlying cluster. This comprehensive approach allows for deep insights into the health, performance, and operational state of your services. Refer to these [instructions](https://learn.microsoft.com/azure/partner-solutions/elastic/create?pivots=elastic-search#logs--metrics-tab-optional) on how to establish your Elastic deployment and begin forwarding your Fabric and all other Azure resource logs for evaluation and insights. ## Humio