Skip to main content

Activate Application Insights on IIS using Powershell

There are 2 ways to start using Application Insights in your applications:

  • Option 1: You install and add the Application Insights SDK to your application. This is easy thanks to the Visual Studio integration but requires you to open, configure and release each application separately
  • Option 2: Use the Application Insights Status Monitor tool. This tool allows you to instrument a live web app with Visual Studio Application Insights, without having to modify or redeploy your code.

Remark: Note there is a third option through the Application Insights extension but this only applies to applications hosted on Azure.

After installing the Application Insights Status Monitor tool, you can pick the installed web applications that you want to monitor. Of course, ‘real’ administrators don’t use a UI but choose Powershell instead Winking smile. Application Insights supports this through the Microsoft.Diagnostics.Agent.StatusMonitor.PowerShell.dll module.

Here is an example how to use it:

  • Open a Powershell command prompt.
  • Load the Application Insights Powershell module
    • Import-Module 'C:\Program Files\Microsoft Application Insights\Status Monitor\PowerShell\Microsoft.Diagnostics.Agent.StatusMonitor.PowerShell.dll'
    • If you get an error that the module could not be loaded, check your Powershell version (use the $PSVersionTable variable). Probably you have to update it first.
  • Go to the Azure Portal
    • Create a new Application Insights subscription

image

    • Once created click on Properties

image

    • Copy the Instrumentation key from the Properties page. This key is required to link your web application to the Application Insights resource.
  • Go back to your Powershell command line
  • Type the following command to start monitoring an application
    • Start-ApplicationInsightsMonitoring -Name appName -InstrumentationKey 00000000-000-000-000-0000000
    • Hereby is -Name the name of the app in IIS and -InstrumentationKey the ikey of the Application Insights resource where you want the results to be displayed.
  • After doing this, you can check which applications are monitored using following command
    • Get-ApplicationInsightsMonitoringStatus
Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...
Read more