|Number of watchers on Github||71|
|Number of open issues||107|
|Average time to close an issue||8 days|
|Average time to merge a PR||1 day|
|Open pull requests||14+|
|Closed pull requests||17+|
|Last commit||over 1 year ago|
|Repo Created||almost 4 years ago|
|Repo Last Updated||over 1 year ago|
|Organization / Author||microsoft|
|Do you use ApplicationInsights-dotnet-server? Leave a review!|
|View open issues (107)|
|View ApplicationInsights-dotnet-server activity|
|View on github|
|Fresh, new opensource launches 🚀🚀🚀|
Trendy new open source projects in your inbox! View examples
The code in this repository is the .NET web application SDK for Application Insights. Application Insights is a service that lets you monitor your live application's performance and usage. This SDK sends telemetry to the service. It collects data such as web request timings and success rates, dependency calls, exceptions, and server performance counters. You can also use the SDK to send your own telemetry and add modules to collect logs. You can use this SDK in any .NET web application, hosted either on your own servers or on Microsoft Azure.
The SDK is installed on each project by the Application Insights tools in Visual Studio (2013 and later).
Follow contributor's guide
Our projects target multiple frameworks (ex: Net45 & NetCore). We have framework specific projects and a shared project for common files between them. (ex: Perf.Net45, Perf.NetCore, Perf.Shared). If a file is used by both frameworks, we prefer to store that file in a Shared project and use preprocessor directives to separate framework specific code (ex:
#if NETCORE, #if !NETCORE). We also use a conditional ItemGroup to assign files to a framework (ex:
ItemGroup Condition=" '$(TargetFramework)' != 'netcoreapp1.0' ").
We've found that this makes our projects easier to maintain because it keeps Framework assignments in a single project. As an added bonus our Framework specific projects can include a single Shared project instead of individual files, which keeps our project files neat and clean.
We strongly welcome and encourage contributions to this project. Please read the contributor's guide. If making a large change we request that you open an issue first. If we agree that an issue is a bug, we'll add the
bug label, and issues that we plan to fix are labeled with an iteration number. We follow the Git Flow approach to branching.