C
Chad Myers
I'm instrumenting my app with a few performance counters
and I'd like to ask you all for some advice on how to handle
performance counter instances.
I have a class library that is a base library for most of our
..NET applications. It provides configuration, logging, exception
management/publishing, data access, etc.
I have my counters, but I'm curious how I should handle instances.
Right now, the instance name is exename-procid like test.exe-5129.
However, I need to remove the instance when the process exits,
so I hook the AppDomain.DomainUnload or whatever it is, but it
doesn't seem to fire reliably.
Does anyone have experience with this? What did you do about
counter instances and how did you solve the problem of when/how
to remove them effectively?
Thanks,
Chad
and I'd like to ask you all for some advice on how to handle
performance counter instances.
I have a class library that is a base library for most of our
..NET applications. It provides configuration, logging, exception
management/publishing, data access, etc.
I have my counters, but I'm curious how I should handle instances.
Right now, the instance name is exename-procid like test.exe-5129.
However, I need to remove the instance when the process exits,
so I hook the AppDomain.DomainUnload or whatever it is, but it
doesn't seem to fire reliably.
Does anyone have experience with this? What did you do about
counter instances and how did you solve the problem of when/how
to remove them effectively?
Thanks,
Chad