andyroyle
commented
8 years ago It may well be better to pick a small subset of ones that we know to be useful (for example: Requests/sec). There are a lot here that are duplicates of things that are already logged (e.g. responses by http code), plus stuff that is unlikely to be useful, except in a handful of cases (e.g. com+ transactions).
It's always easier to add stuff than it is to remove it.
One easy way for those using asp.net to include all the asp.net performance counters
There are more system counters that could be gathered but this are up do discussion The idea would be that this could be a blueprint to a more generic performance counter gathered that could be used passing only the category Or even one that gets all the performance counters from the machine.