Skip to main content

Monitor your application using Event Counters - Part III

I'm building a data pipeline using TPL Dataflow to migrate data from a database to an external API. As this data pipeline could run for a long time, I was looking for a good way to monitor the progress. This turned out to be a perfect use case for Event Counters.

So far we have seen how to create a simple EventCounter using a PollingCounter and how to read out its value using the dotnet-counters global tool.

The PollingCounter uses a callback to determine the value that is reported. With each time interval, the user provided callback function is invoked and the return value is used as the counter value. This allows us to manage and track the number of migrated documents ourselves.

Let’s continue today and have a look at how we can use some of the other counters to improve our metrics.

Tracking the migration rate using the IncrementingPollingCounter

We are already tracking the number of migrated documents. Wouldn’t it be nice to also track the number of documents that are migrated in a certain interval, or better said the rate at which documents are migrated.

The good news is that we don’t have to do a lot to get this working. This is a perfect use case for the IncrementingPollingCounter.

From the documentation:

The IncrementingPollingCounter uses a callback to determine the reported increment value. With each time interval, the callback is invoked, and then the difference between the current invocation, and the last invocation is the reported value.

Let’s update our code to introduce this second metric.

  • We create a new variable of type IncrementingPollingCounter:
  • And instantiate this variable in our constructor.

Let’s run dotnet-counters again to see the results:

dotnet-counters monitor --process-id 32072--counters Migrator.MigratedRecordsCounter

Now we get 2 values back; our Migration Count total and the Migration Rate.

Remark: In the code above you saw that I also could specify a DisplayRateTimeScale.  I expected that this would allow me to set the interval at which the value should be read. However it turned out that this value is ignored and that the dotnet-counters will always use an interval of 1 second.

This is by design. More about this here.

 UPDATE: I made the full example available on Github: https://github.com/wullemsb/EventCounters

    Labels:

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

    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