Search for a command to run...
I used to be a .NET developer. Nowaways, I am a DevOps solutions architect with a focus on Azure and Kubernetes.
I also love productivity topics, especially when it comes to doing more with less of my time. I'm also a daddy, so time is a limited resource for me.
No comments yet. Be the first to comment.
I'm going to share all my secrets with you
Using a pull-request workflow
This is the guide I wish I had
Connecting your GitHub Workflows to Azure AD using OpenID Connect
In this post, I’ll walk through the essentials of configuring an AKS cluster to use Argo CD with an NGINX Ingress Controller. Pre-Requisites You’ll need: An AKS cluster. Here’s a Gist I use to create a simple cluster. Helm 3 Azure CLI A Custom DNS/A...
Oof that title is a mouthful. Adding application insights to a containerized asp.net core application is not too difficult. It’s pretty simple.
Using ARM, create an application insights resource like this:
{
"apiVersion": "2014-04-01",
"name": "[variables('appInsightsName')]",
"type": "Microsoft.Insights/components",
"location": "[resourceGroup().location]",
"properties": {
"applicationId": "[parameters('appName')]"
}
}
Using an appSetting, you can also populate the instrumentation key onto the app service. You’ll also need a dependsOn declaration.
"appSettings": [
{
"name": "APPINSIGHTS_INSTRUMENTATIONKEY",
"value": "[reference(variables('appInsights')).InstrumentationKey]"
}
]
The instrumentation key is the only setting required by the app insights sdk to be able to work correctly. If you need more help on setting an app setting on an azure web app, here’s the arm schema.
APPINSIGHTS_INSTRUMENTATIONKEY app setting will get translated to an environment variable when the container spins up in the app service. The sdk that you’ll be adding will know too look for an instrumentation key based on an environment variable with the name APPINSIGHTS_INSTRUMENTATIONKEY or ApplicationInsights:InstrumentationKey
There’s two main ways to add app insights. The codeless way or through the sdk. I prefer the sdk for greater control and flexibility later.
Right click on your asp.net core project and select “Configure Application Insights”.
Then select, “Get Started”
Lastly, don’t worry about creating an app insights resource on Azure, this is what the arm template will be used for. Click on the small link “Or just add the SDK to try local mode.”
You’ll notice that it adds references to a new NuGet package. Also, it makes small modifications to the ASP.NET Core service registration.
Now before deploying, deploy your arm template. Do always consider deploying your arm templates through a pipeline.
To recap:
To get a more detailed example of what it should look like, check out this pull request. Also, here’s another link for the official guide by Microsoft.