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

    Popular posts from this blog

    DevToys–A swiss army knife for developers

    As a developer there are a lot of small tasks you need to do as part of your coding, debugging and testing activities.  DevToys is an offline windows app that tries to help you with these tasks. Instead of using different websites you get a fully offline experience offering help for a large list of tasks. Many tools are available. Here is the current list: Converters JSON <> YAML Timestamp Number Base Cron Parser Encoders / Decoders HTML URL Base64 Text & Image GZip JWT Decoder Formatters JSON SQL XML Generators Hash (MD5, SHA1, SHA256, SHA512) UUID 1 and 4 Lorem Ipsum Checksum Text Escape / Unescape Inspector & Case Converter Regex Tester Text Comparer XML Validator Markdown Preview Graphic Color B

    Help! I accidently enabled HSTS–on localhost

    I ran into an issue after accidently enabling HSTS for a website on localhost. This was not an issue for the original website that was running in IIS and had a certificate configured. But when I tried to run an Angular app a little bit later on http://localhost:4200 the browser redirected me immediately to https://localhost . Whoops! That was not what I wanted in this case. To fix it, you need to go the network settings of your browser, there are available at: chrome://net-internals/#hsts edge://net-internals/#hsts brave://net-internals/#hsts Enter ‘localhost’ in the domain textbox under the Delete domain security policies section and hit Delete . That should do the trick…

    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.