Chaining profilers

[bobuva]

In years past, I've spoken with various people at Microsoft who were interested in running multiple profilers (that use the .NET Profiler API) on the same machine. Has any consideration been given to this for the now open-source profiler here in coreclr?

[RussKeldorph]

@noahfalk

[lt72]

@bobuva: yes, we have considered the issue, but we do not believe we will proceed to design/implementation any time soon. Although this is definitely on our TODO list, we did not have many concrete requests on this subject yet.

[bobuva]

@lt72 Thanks for the reply. Although you haven't seen many requests, there are in fact products on the market that use the profiler API. Attempting to have another profiler api-based tool reside side-by-side with one of them is currently impossible. I would be interested in continuing to speak to whomever is keeping an eye on that item.

[lt72]

That would me either myself or @noahfalk

[bobuva]

@lt72 , @noahfalk : I'll be at //build in May. Will either of you be at the conference? Maybe we could chat more there?

[lt72]

We are not participating directly, but it will be a pleasure to stop by and chat! I'll send you my contact so you can ping me directly when the time comes and we can agree on details then.

[bobuva]

Thanks!

[davmason]

The runtime does not support multiple profilers, but Microsoft provides the CLR instrumentation engine that allows you do host multiple IL rewriting profilers at once: https://github.com/microsoft/CLRInstrumentationEngine

[dotnet-policy-service]

Due to lack of recent activity, this issue has been marked as a candidate for backlog cleanup. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will undo this process.

This process is part of our issue cleanup automation.

[dotnet-policy-service]

This issue will now be closed since it had been marked no-recent-activity but received no further activity in the past 14 days. It is still possible to reopen or comment on the issue, but please note that the issue will be locked if it remains inactive for another 30 days.