KO | EN

GitLite

Minimalist Open Source Repository Search Engine

gitlite — search

#dsh #dsh-plugin #typescript #developer-tools #claude-code #ai-agent #codex #deepseek-harness #ai-agents #cli #react #mcp

Azure-Service-Fabric-Logging-And-Monitoring

★ 26 Open GitHub ↗

This repository contains an Azure Service Fabric application that integrates Application Insights with Service Fabric using structured logging.

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# Overview

This repository contains an Azure Service Fabric application that provides some guidance and examples on how to setup and configure logging and demonstrates some approaches. It is probably not production ready but it gives a working overview on how things are working together. Please see it as a good starting point for your own integration.

The application consist of two stateless services, one hosting an ASP.Net Core application that acts as an Web Api and a stateless service that is being called from the Web Api using [Service Remoting](https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-reliable-services-communication-remoting).

![Application Overview](https://raw.githubusercontent.com/Expecho/Azure-Service-Fabric-Logging-And-Monitoring/master/blobs/asf-application.PNG)

It uses a structured logging framework called [Serilog](https://serilog.net/) to log events. The logged events are then written to [Application Insights](https://azure.microsoft.com/en-us/services/application-insights/) using [this](https://github.com/serilog/serilog-sinks-applicationinsights) Serilog sink. By using Serilog to capture the events instead of logging directly to Application Insights using the SDK it is easy to add different outputs for the logged events.

Also this repository contains the NuGet package [ServiceFabric.Logging](https://www.nuget.org/packages/ServiceFabric.Logging/).

You can directly install this library from [Nuget][6]

PM> Install-Package ServiceFabric.Logging
    
  [![NuGet package](https://badge.fury.io/nu/ServiceFabric.Logging.svg)](https://www.nuget.org/packages/ServiceFabric.Logging/)
 [![NuGet](https://img.shields.io/nuget/dt/ServiceFabric.Logging.svg)]()

[6]: http://nuget.org

# How it works

.Net Core provides [a logging abstraction](https://docs.microsoft.com/en-us/aspnet/core/fundamentals/logging) that provides support for structured logging. Since Serilog is supported by the .Net Core logging abstraction we can seperate the calls to the logger from the actual implementation. (For more background about this, read [this excellent blog post](https://msdn.microsoft.com/en-us/magazine/mt694089.aspx))

By using [custom Middleware](/src/ServiceFabric.Logging/Middleware/RequestTrackingMiddleware.cs) in the ASP.Net Core pipeline we can capture the trace id of the request and use that in the logging to correlate log events. Calls from the Web Api to the other stateless service are [intercepted and logged](/src/ServiceFabric.Logging/Remoting/ServiceRemoting.cs).

Most other logging frameworks provide Application Insights sinks that are only capable of writing Trace entities to Application Insights. Using structured logging gives the advantage to transform the log events to specific Application Insights entities like Requests, Dependencies, Metrics and Exceptions. This is done by the [TelemetryBuilder](/src/ServiceFabric.Logging/ApplicationInsights/TelemetryBuilder.cs) class.

# Features
 - Full Application Insights Integration
 - Structured Logging
 - Easy to add other sinks
 - Integration with .Net Core logging framework
 
# Getting started

This source is build and tested using Azure Service Fabric 6.2 and SDK 3.1, with Visual Studio 2017 v15.1

Before running the sample [create a new Application Insights resource](https://docs.microsoft.com/en-us/azure/application-insights/app-insights-create-new-resource) and copy the Instrumentation Key to the application parameter in the [Service Fabric Application manifest file](/src/AzureServiceFabric.Demo.Diagnostics/ApplicationPackageRoot/ApplicationManifest.xml#L6):

```xml
<ApplicationManifest xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" ApplicationTypeName="AzureServiceFabric.Demo.DiagnosticsType" ApplicationTypeVersion="1.0.0" xmlns="http://schemas.microsoft.com/2011/01/fabric">
  <Parameters>
    <Parameter Name="WebApi_InstanceCount" DefaultValue="-1" />
    <Parameter Name="MyStateless_InstanceCount" DefaultValue="-1" />
    <Parameter Name="ApplicationInsightsKey" DefaultValue="[YOUR_KEY-HERE]" />
  </Parameters>
  ```

Deploy the application, wait for all services to be up and running and point the browser to the web api at http://localhost:8700/api/values?a=1&b=2

## Application Insights integration

Observe the events written to application insights:

![Application Insights](https://raw.githubusercontent.com/Expecho/Azure-Service-Fabric-Logging-And-Monitoring/master/blobs/app-insights.PNG)

All telemetry includes service fabric specific metadata:

![Application Insights](https://raw.githubusercontent.com/Expecho/Azure-Service-Fabric-Logging-And-Monitoring/master/blobs/app-insights-telemetrydata.PNG)

Live telemetry like cluster load (per node) and traffic can be viewed in the Live Metrics Stream:

![Application Insights Live Metrics Stream](https://raw.githubusercontent.com/Expecho/Azure-Service-Fabric-Logging-And-Monitoring/master/blobs/live-metrics.PNG)

# Additional Resources

This repository is focused on using structured logging using Serilog in order to provide rich en detailed logging output. If you are not familiar with structured logging these links provide some insights about the what and why:

- [The concept of structured logging](https://nblumhardt.com/2016/06/structured-logging-concepts-in-net-series-1/)
- [Benefits of structured logging](http://softwareengineering.stackexchange.com/questions/312197/benefits-of-structured-logging-vs-basic-logging)

Azure-Service-Fabric-Logging-And-Monitoring

Explore Similar Repositories

Was this content helpful?

Recent Feedback

Download README