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

Popular posts from this blog

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...

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.

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...