Enabling getting telemetry data for .NET Core application running inside containers that managed by Kubernetes.
xiaomi7732 Dev/saars/xmldoc (#140)
* Remove an unused file

* Geneate XML Documents upon build

* Change some comments per code reviews
Latest commit 5d0ca6c Sep 19, 2018


Microsoft Application Insights for Kubernetes

This repository has code for Application Insights for Kubernetes, which works on .NET Core applications within the containers, managed by Kubernetes, on Azure Container Service.

Note: Microsoft Application Insights for Kubernetes (this library) is an enhancement to the Microsoft Application Insights. You can choose to run Application Insights without this library in Kubernetes cluster too. However, when using Microsoft Application Insights for Kubernetes, you will see Kubernetes related properties like Pod-Name, Deployment ... on all your telemetry entries. Proper values will also be set to make use of the rich features like enabling the Application Map to show the multiple micro services on the same map.

Continous Integration Status

Rolling Build Nightly Build
Rolling-Build Status Nightly-Build Status

Get Started



We support ASP.NET Core application as well as .NET Core application.

  • For ASP.NET Core Application: Refer Getting Started for a simple walkthrough.

  • For .NET Core Application: Refer Getting Started for a simple walkthrough.

  • Follow this example for Role-based access control (RBAC) enabled Kubernetes clusters.

Verify the cluster configuration

Use the troubleshooting image to verify the cluster is properly configured.

Learn more

Next step

Profile your application for performance improvement using Application Insights Profiler for Linux.


Report issues

Please file bug, discussion or any other interesting topics in issues on github.

Trouble Shooting

When Microsoft.ApplicationInsights.Kubernetes doesn't work properly, you can turn on self-diagnostics to see the traces in Kubernetes' logs. Refer this wiki page for instructions to turn on trace.


Please refer the Develop Guide.

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.