OpenDotNetDiagnostics.Counters.Triggers.ProcessStart 1.0.0-beta4

This is a prerelease version of OpenDotNetDiagnostics.Counters.Triggers.ProcessStart.
There is a newer prerelease version of this package available.
See the version list below for details.
dotnet add package OpenDotNetDiagnostics.Counters.Triggers.ProcessStart --version 1.0.0-beta4                
NuGet\Install-Package OpenDotNetDiagnostics.Counters.Triggers.ProcessStart -Version 1.0.0-beta4                
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="OpenDotNetDiagnostics.Counters.Triggers.ProcessStart" Version="1.0.0-beta4" />                
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add OpenDotNetDiagnostics.Counters.Triggers.ProcessStart --version 1.0.0-beta4                
#r "nuget: OpenDotNetDiagnostics.Counters.Triggers.ProcessStart, 1.0.0-beta4"                
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install OpenDotNetDiagnostics.Counters.Triggers.ProcessStart as a Cake Addin
#addin nuget:?package=OpenDotNetDiagnostics.Counters.Triggers.ProcessStart&version=1.0.0-beta4&prerelease

// Install OpenDotNetDiagnostics.Counters.Triggers.ProcessStart as a Cake Tool
#tool nuget:?package=OpenDotNetDiagnostics.Counters.Triggers.ProcessStart&version=1.0.0-beta4&prerelease                

Welcome to Open DotNET Diagnostics

Integrate .NET diagnostics tools into your code and seamlessly deliver results to multiple destinations.

Vision for the project

Please note that while this repository is open source, it is not a Microsoft/dotnet repository. We welcome contributions from anyone interested in improving our solution.

Our approach prioritizes the developer experience and therefore requires some code instrumentation, typically just a few lines. If you prefer an operational approach that doesn't require any code changes, we recommend checking out the official dotnet-monitor repository.

Get Started (dotnet-counters)

Assuming you have an ASP.NET Core WebAPI project:

  1. Add NuGet packages:

  2. Instrument the code to register the proper service and map the end point, for example:

    var builder = WebApplication.CreateBuilder(args);
    
    // Register `dotnet-counters` service and its sink.
    builder.Services.AddDotNetCounters()
        .WithLocalFileSink()
        .Register();
    
    var app = builder.Build();
    
    app.MapGet("/", () => "Hello World!");
    
    // Add an endpoint of `/dotnet-counters`
    app.MapDotNetCounters("/dotnet-counters");
    app.Run();
    

    Other sinks, for example, Azure Blob or Application Insights are also supported. See wiki for more details.

  3. Optionally, customize the settings, for example, you could specify a invoking secret than the default of 1123 by putting this in your appsettings.json:

    "DotNetCounters": {
        "InvokingSecret": "1111"
    },
    
  4. Run your app.

  5. To enable dotnet-counters, invoke a HttpPUT on the endpoint, for example:

    Invoking dotnet-counters

    Tips: You can turn off dotnet-counters at anytime by invoke another PUT request with isEnabled parameter set to false.

  6. Get the output

    • In a local environment, by default, the file is in %tmp%, you will have files like Counters_2023031600.csv;
    • In Azure App Service, the default output path would be %HOME%/LogFiles/Application/, and the file name would carry a unique id for the service instance, like this:
      • Counters_82177b41d89d4b2dce789b4903a7e0dc0a76412697ac6069b750097059c09ed7_2023031523.csv Counters Output on Kudu
  7. And you shall be able to download analysis the result in tools you already familiar with, for example, in the Excel:

    Analysis example in excel for working set

    What we see: it is a pretty small amount of working set used over the period, yet we could still see dips, probably GC?

Vision

We aim to alleviate the following pain points:

  1. You no longer need to deliver dotnet diagnostic tool binaries such as dotnet-counters, dotnet-trace, or dotnet-dump to your environment..

    1. Some environments, such as containers, make it inconvenient to add additional binaries, while others, like Azure App Service/WebSite, are sandboxed and unable to run .NET tools.
    2. With our solution, you can enjoy a consistent experience whether you are diagnosing issues locally or remotely.
  2. You no longer need to export diagnostic data, such as dotnet-counter output, from a constrained environment.

    1. By adding proper sinks, you can easily access these files through Kudu or Azure Blob Storage and so on.
    2. Your data will persist externally even if your machine or containers are recycled.
  3. With our solution, you can write once and run everywhere, including locally, on Azure WebSite, in containers, or on AKS, with a unified experience.

Road map

  1. Add support for more .NET diagnostics tools.
  2. Update to support more complex environments - scaled out multiple instances.
  3. Support triggers - that automatically starts the diagnostic tools.
  4. Add guidance for extending sinks.
DotNet Tools Local Environment Azure App Service Container Remarks
dotnet-counters OpenDotNetDiagnostics.Counters.WebEndpoints +<br /> OpenDotNetDiagnostics.Counters.Sinks.LocalFile OpenDotNetDiagnostics.Counters.WebEndpoints +<br /> OpenDotNetDiagnostics.Counters.Sinks.LocalFile or OpenDotNetDiagnostics.Counters.Sinks.AzureBlob OpenDotNetDiagnostics.Counters.WebEndpoints +<br /> OpenDotNetDiagnostics.Counters.Sinks.AzureBlob MVP
dotnet-dump Planning Planning Planning Coming next
dotnet-trace Planning Planning Planning Backlog

There are quite a few to crewing through. Please feel free to contact if want to contribute.

  • Core projects

    • Core - fundamental utilities, data contracts, abstractions.
    • Counters - dotnet-counters specific implementations.
  • Endpoints

    • dotnet-counters
      • WebEndpoints - expose dotnet-counters as a WebAPI endpoint. Default to PUT /dotnet-counters.
  • Sinks

    • dotnet-counters
      • Local file - beta, outputs data to local file.
      • Azure Blob - beta, outputs data to Azure Storage for easy access.
      • Application insights - beta, outputs data to Application Insights for powerful query.
Product Compatible and additional computed target framework versions.
.NET net6.0 is compatible.  net6.0-android was computed.  net6.0-ios was computed.  net6.0-maccatalyst was computed.  net6.0-macos was computed.  net6.0-tvos was computed.  net6.0-windows was computed.  net7.0 was computed.  net7.0-android was computed.  net7.0-ios was computed.  net7.0-maccatalyst was computed.  net7.0-macos was computed.  net7.0-tvos was computed.  net7.0-windows was computed.  net8.0 was computed.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
1.0.0-beta5 101 6/9/2023
1.0.0-beta4 94 4/12/2023
1.0.0-beta3 92 4/6/2023