[Feature Request]: Diagnostics for processor count

[noahfalk]

Original combined issue here

The goal is to help customers better understand how their applications are running by adding events and counters that can give more insights and will help them debug potential performance issues. It'll also help us debug customer applications and write tools that would be able to glean insights from traces.

What was the value of Environment.ProcessorCount should be emitted in an event. I'm not sure which event is most appropriate for this (if we have an existing one) but we need a way to get the runtime settings.

Tagging subscribers to this area: @tommcdon, @krwq
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Original combined issue here

The goal is to help customers better understand how their applications are running by adding events and counters that can give more insights and will help them debug potential performance issues. It'll also help us debug customer applications and write tools that would be able to glean insights from traces.

What was the value of Environment.ProcessorCount should be emitted in an event. I'm not sure which event is most appropriate for this (if we have an existing one) but we need a way to get the runtime settings.

Author:	noahfalk
Assignees:	-
Labels:	area-System.Diagnostics
Milestone:	7.0.0

[noahfalk]

From the original thread I wrote:

Do you care about the number of processors on the machine, or specifically this value (which I believe might differ when apps run with restricted processor groups)? For the machine level info ETW emits that into every trace with the Windows Kernel/EventTrace event.

David replied:

Environment.ProcessorCount is separate because we can change it based on an environment variable now. I'd want that to be a part of the runtime settings blob we emit