Skip to main content

dotnet monitor–Run as a sidecar in a Kubernetes cluster

Yesterday I blogged about ‘dotnet monitor’ and how it can help you to collect diagnostic artifacts at runtime in a uniform way.

Let’s have a look today on how to use ‘dotnet monitor’ inside a Kubernetes cluster.

When running in a cluster, it is recommend to run the dotnet-monitor container as a sidecar alongside your application container in the same pod.

Here is an example manifest on how to set this up:

Most important to notice in the manifest is that you need to share a volume between the application container and the sidecar.

Let’s deploy this manifest:

$ kubectl apply –f ./dotnetmonitor.yaml

Once your pods are up and running, we need to use port forwarding to be able to access the diagnostics endpoint from our local machine.

To do this, we first need to find the name of the pod :

$ kubectl get pod -l app=dotnet-monitor-example
NAME                                 READY   STATUS    RESTARTS   AGE
dotnet-monitor-example-78997f8fdf-nrhp7   2/2     Running   0          5m

Now we know the pod name, we an forward traffic using the kubectl port-forward command:

$ kubectl port-forward pods/dotnet-monitor-example-78997f8fdf-nrhp7 52323:52323

Now we can invoke the different endpoints the same way as before:

$ curl -s http://localhost:52323/processes | jq

Remark: Although the example above worked on my local cluster, I got into trouble when I tried to do use the same steps on AKS. I'll share another post to explain where I got into trouble and how I fixed it.

Labels:

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

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