Hey guys, thank you for the responses!
Yes, we are doing this on our dev environment for now. The thing is that we are actually trying to determine which classes are critical to the application/transactions, as there are lots of DLLs involved (also some 3rd frameworks).
We are basically doing a discover all, check what makes sense to monitor and skip all the rest, that for the custom part of it (frameworks, DLLs from other teams, etc), as there is no automatic instrumentation like the java agents. Besides that we are trying to keep the agent simple (using the typical pbl).
@Manish
Thanks for the tip on turning the perfmon off when it goes production mode
One last question is how we could reduce the number of metrics for the classes instrumented. We are using the BlamePointTracer but all we need at the moment is to monitor response times and keep those classes and methods showing on traces and errors tab (thats the blame part of it, right?).