C# PowerShell HTML Other
Switch branches/tags
Clone or download
Permalink
Failed to load latest commit information.
.github PR template change Feb 5, 2018
.vsts fix typo in yml Dec 22, 2017
Schema Enable ServerTelemetryChannel in .net core by the default (#530) Sep 25, 2017
keys Tilee/test signing (#689) May 16, 2018
src/Microsoft.ApplicationInsights.AspNetCore Update base web to 2.7.2 Aug 14, 2018
test Cleanup after requests collection tests (#724) Jul 24, 2018
.gitattributes Update to RC2 along with the renaming of dependencies, Renaming To As… Mar 17, 2016
.gitignore Gitignore Dec 22, 2017
ApplicationInsights.AspNetCore.sln up Mar 9, 2018
CHANGELOG.md Update base web to 2.7.2 Aug 14, 2018
CleanPackages.ps1 Updating scripts and retaining old scripts May 6, 2016
CleanPackagesCore.ps1 Updating scripts and retaining old scripts May 6, 2016
Common.targets Remove roslyn and dotnetcore nuget sources Aug 15, 2015
GenerateReleaseMetadata.ps1 release metadata Apr 11, 2018
LICENSE Initial commit Mar 17, 2015
Microsoft-Security-Recommended.ruleset Added code analysis. Aug 15, 2016
NuGet.config Move back to 1.0.1 of runtime Nov 19, 2016
NuGet.exe Added EmptyApp20 and FunctionalTestUtils20 Aug 31, 2017
Readme.md fix product name Jun 15, 2018
RunTests.cmd Added intermediateoutput path to all projects without which 2.0 CLI h… Nov 21, 2017
RunTestsCore.ps1 Return to root solution dir after tests are executed (#406) Apr 26, 2017
SetEnv.targets Marked the analyzers for build only and not NuGet packaging. Rev'ed v… Sep 28, 2016
Signing.props Tilee/test signing (#689) May 16, 2018
ThirdPartyNotices.txt Removing unused external test dependencies and adding third party notice Sep 1, 2016
build.ps1 Making properties automatic and changing the build definition to release May 9, 2016
buildDebug.cmd Added intermediateoutput path to all projects without which 2.0 CLI h… Nov 21, 2017
buildRelease.cmd Added intermediateoutput path to all projects without which 2.0 CLI h… Nov 21, 2017
clean.cmd Modified clean.cmd Jul 14, 2017
dirs.proj Tilee/test signing (#689) May 16, 2018
disablestrongnamevalidation.ps1 Remove signing from test projects Feb 5, 2018
enablestrongnamevalidation.ps1 Remove signing from test projects Feb 5, 2018
findMsBuild.cmd latest dotnet cli sdk. fix local test run scripts Feb 5, 2018

Readme.md

NuGet packages

Microsoft Application Insights for ASP.NET Core applications

This repository has a code for Application Insights monitoring of ASP.NET Core applications. Read about contribution policies on Application Insights Home repository

Getting Started

Application Insights monitoring is a service that allows you to collect monitoring and diagnostics information about your application. The getting started guide shows how you can onboard your ASP.NET Core web application to use the Application Insights SDK.

Application Insights collects a lot of information out-of-the-box such as requests, dependencies, exceptions, and usage. It also allows you to configure additional data collection. The configure guide demonstrates the most common tasks you may want to do.

Repository structure

root\
    ApplicationInsights.AspNetCore.sln - Main Solution

    src\
        ApplicationInsights.AspNetCore - Application Insights package

    test\
        ApplicationInsights.AspNetCore.Tests - Unit tests
        FunctionalTestUtils - Test utilities for functional tests
        MVCFramework.FunctionalTests - functional tests for MVC application targetting NetCore1.1,NetCore2.0 and NET45
        WebApi.FunctionalTests - functional tests for Web API application targetting NetCore1.1,NetCore2.0 and NET45
		EmptyApp.FunctionalTests - functional tests for an Empty application targetting NetCore1.1,NetCore2.0 and NET45
        PerfTest - performance test

Developing

To successfully build the sources on your machine, make sure you've installed the following prerequisites:

Building

Once you've installed the prerequisites execute buildDebug.cmd or buildRelease.cmd script in the repository root to build the project locally. You can also open the solution in Visual Studio and build the ApplicationInsights.AspNetCore.sln solution directly.

Testing/Debugging

Execute the RunTests.cmd script in the repository root.

You can also open the solution in Visual Studio and run tests directly from Visual Studio Test Explorer. However, as the tests has multiple targets, Test Explorer only shows the first target from in .csproj. To debug/run tests from a particular TargetFramework with Visual Studio, only option is to re-arrange the such that the intented target comes first. This is a Visual Studio limitation and is likely removed in the future.

Running and writing tests

There are two sets of tests unit tests and functional tests. Please use unit tests for all features testing. The purpose of functional tests is just end-to-end validation of functionality on sample applications.

Functional tests Functional tests are regular web applications with unit tests integrated into them. Application can be compiled as a regular web application as well as set of tests. Typical functional tests will do the following:

  1. Host the current project in In-Proc server.
  2. Initialize application insights telemetry channel.
  3. Initiate request to self hosted web application using HttpClient.
  4. Check data received in telemetry channel.

The following are modifications made to a regular web application to make it work this way:

Add dependencies to .csproj:

"FunctionalTestUtils": "1.0.0-*",
"dotnet.test.xunit": "1.0.0-*",
"xunit": "2.1.0"

and test command:

"test": "xunit"

Add this initialization logic to Startup.cs:

services.AddFunctionalTestTelemetryChannel();

Branches

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.