Application Insights for Kubernetes enhances telemetries with K8s properties, works for .NET Core/.NET 6 applications in Kubernetes clusters.
⚠️ Microsoft Application Insights for Kubernetes
(this library) is designed to improve the functionality of Microsoft Application Insights. While it is possible to run Application Insights on a Kubernetes cluster without this library, it allows for Kubernetes-specific properties such as Pod-Name and Deployment to be included in all telemetry entries. Additionally, the library ensures that appropriate values are assigned, enabling advanced features like the Application Map to display multiple microservices or roles on a single Application Insights map.
Rolling Build | Nightly Build |
---|---|
This is a quick guide for ASP.NET Core projects. If you want to run it in a worker, see the instructions in the Walk-through section.
⚠️ For RBAC-enabled Kubernetes, make sure permissions are configured.
-
Add references to Application Insights SDK and Application Insights for Kubernetes by running:
dotnet add package Microsoft.ApplicationInsights.AspNetCore dotnet add package Microsoft.ApplicationInsights.Kubernetes
-
Enable Application Insights and Application Insights for Kubernetes Enricher in
Startup.cs
/Program.cs
:public void ConfigureServices(IServiceCollection services) { ... services.AddApplicationInsightsTelemetry("----Your Application Insights Instrumentation Key ----"); services.AddApplicationInsightsKubernetesEnricher(); ... }
-
Build the application in containers, then deploy the container with Kubernetes.
Notes: Those steps are not considered the best practice to set the instrumentation key for application insights. Refer to Enable Application Insights server-side telemetry for various options. Also, consider deploying Kubernetes Secrets to secure it. Refer to Deploy the application in Kubernetes for an example.
- Enable Application Insights for Kubernetes on WebAPI (Controller based or Minimal API).
- Enable Application Insights Kubernetes in worker project.
Customize configurations are supported. There are several ways to customize the settings. For example:
-
Using code:
services.AddApplicationInsightsKubernetesEnricher(option=> { option.InitializationTimeout = TimeSpan.FromSeconds(15); });
-
Using
appsettings.json
:{ "Logging": { // ... }, // Adding the following section to set the timeout to 15 seconds "AppInsightsForKubernetes": { "InitializationTimeout": "00:00:15" } }
-
Using environment variables:
AppInsightsForKubernetes__InitializationTimeout=3.1:12:15.34
All the related configurations have to be put in a section named
AppInsightsForKubernetes
. The supported keys/values are listed below:Key Value/Types Default Value Description InitializationTimeout TimeSpan 00:02:00 Maximum time to wait for spinning up the container. Accepted format: [d.]hh:mm:ss[.fffffff]. ClusterInfoRefreshInterval TimeSpan 00:10:00 Get or sets how frequent to refresh the Kubernetes cluster properties. DisablePerformanceCountersBooleanfalseDeprecated. Sets to true to avoid adding performance counter telemetry initializer.
Tips: Refer to AppInsightsForKubernetesOptions.cs for the latest customization supported.
The configuration uses the ASP.NET Core conventions. Refer to Configuration in ASP.NET Core for more information.
Use the troubleshooting image to verify the cluster is properly configured.
- To build a container for Kubernetes that have Application Insights baked in for the existing applications, please refer to the example of Zero Code light up.
- To enable diagnostic logs when Application Insights for Kubernetes doesn't work as expected, reference How to enable self diagnostics for ApplicationInsights.Kubernetes.
- Still want more? Read the Wikis.
Profile your application for performance improvement using Application Insights Profiler for Linux.
Please file bug, discussion or any other interesting topics in issues on GitHub.
Read the FAQ for common issues. When Microsoft.ApplicationInsights.Kubernetes doesn't work properly, you can turn on self-diagnostics to see the traces in Kubernetes' logs. Refer to How to enable self diagnostics for ApplicationInsights.Kubernetes for instructions.
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.