Skip to main content

Monitor your application using Event Counters–Part II

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.

Yesterday I introduced EventCounters and showed a small example. Today let’s have a look on how we can monitor the EventCounters values.

Monitor EventCounters using dotnet-counters

There are multiple ways to read out EventCounters values but the way I want to use during the migration is through the dotnet-counters global tool:

dotnet-counters is a performance monitoring tool for ad-hoc health monitoring and first-level performance investigation. It can observe performance counter values that are published via the EventCounter API or the Meter API. For example, you can quickly monitor things like the CPU usage or the rate of exceptions being thrown in your .NET Core application to see if there's anything suspicious before diving into more serious performance investigation using PerfView or dotnet-trace.

If you don’t have the tool installed yet, you can install the latest version using dotnet install:

dotnet tool install --global dotnet-counters

Now that we have the dotnet-counters tool available, we can use dotnet-counters ps to display a list of .NET processes that can be monitored:

Now we can invoke the dotnet-counters monitor command and pass the process id as a parameter:

dotnet-counters monitor --process-id 28444

This will start the monitoring. By default we get a list of eventcounters from System.Runtime:

To view the EventCounter we created in the previous post, we should specify the counter name:

dotnet-counters monitor --process-id 28444 – --counters Migrator.MigratedRecordsCounter

Now we should see the values from our counter:


In the next post, we'll have a look at some of the other counters and see how we can further improve our example. Stay tuned!

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.