Configure Windows OpenTelemetry Collector Metrics with opensearch

I’m running a small Windows cluster—no more than five nodes—all hosting .NET services, and I want OpenTelemetry Collector installed and tuned so I can see CPU usage, memory usage and network traffic in near-real time.

The job is to produce a repeatable, production-ready setup:

• Windows-compatible Collector binaries and all required receivers/exporters
• A clear, commented YAML configuration that gathers CPU, memory and network metrics
• An automation script (PowerShell preferred) that installs the Collector, registers it as a service and applies the config across 1-5 nodes
• A concise guide showing how to verify the metrics from a fresh node and extend the config later

Acceptance criteria
• After following your guide on a clean node, my monitoring backend immediately begins displaying live CPU, memory and network data
• Collector starts automatically on boot and runs 24 h without errors or noticeable overhead

If you’ve tackled Windows-based OpenTelemetry deployments for .NET workloads before, I’d love to hear how quickly you can replicate that success here.