Skip to main content

Azure Application Insights– Query your log messages

By default when you have configured the Application Insights telemetry inside your application, an Application Insights logging provider is registered. This registered provider is configured to automatically capture log events with a severity of LogLevel.Warning or greater(Learn how to change this in one of my previous blog posts).

When you go to the Azure Portal and have a look at the Application Insights resource, you’ll see that by default multiple types of data are captured:

  • Requests
  • Traces
  • Dependencies
  • Exceptions

More information about the different types of data can be found in the Application Insights Data Model here.

This is important to know when you want to search for specific log information. The easiest way to do this is through Log Analytics (Go to Monitoring –> Logs).

But when you open Log Analytics, the available example packs are mainly focussed on Requests:

If you want to search for a specific log message, you should use the Traces:

Or if you want to search for a specific exception, you should use the Exceptions:

More information: https://docs.microsoft.com/en-us/azure/azure-monitor/app/ilogger

Popular posts from this blog

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...

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         ...