What happened:
When enabling ETW logging via Geneva for both CNS and CNI components, only one of the services emits logs successfully. The other service’s logs are either missing or not routed correctly. This appears to be a conflict in the Geneva logging pipeline.

What you expected to happen:
Both CNS and CNI should be able to emit logs concurrently to Geneva using ETW without interfering with each other’s telemetry.

How to reproduce it:

1. Enable Geneva ETW logging for both CNS and CNI on a Windows node.
2. Use the same Geneva profile name (e.g., ACN-Monitoring) for both services.
3. Observe that only one of the services (typically CNS) emits logs to Geneva, while the other (CNI) does not.

Orchestrator and Version (e.g. Kubernetes, Docker):
Kubernetes (AKS), version details can vary — issue observed in multiple clusters.

Operating System (Linux/Windows):
Windows

Kernel (e.g. uanme -a for Linux or $(Get-ItemProperty -Path "C:\windows\system32\hal.dll").VersionInfo.FileVersion for Windows):
Applicable to Windows kernel versions used in AKS Windows node pools.

Anything else we need to know?:
[Miscellaneous information that will assist in solving the issue.]

• Both CNS and CNI are configured to use the same Geneva profile name: ACN-Monitoring.
• This may cause a conflict in the Geneva Monitoring Agent or ETW session registration.
• A workaround might involve assigning unique profile names per component or isolating their ETW providers.