Multiple Remote Hosts Support

[pankaj101A]

Component(s)

receiver/windowseventlog

Is your feature request related to a problem? Please describe.

The current windowseventlog receiver supports configuring only a single remote host per receiver instance.

In real-world deployments, customers often need to collect Windows Event Logs from multiple remote hosts (dozens or hundreds) that share the same credentials and configuration.

Current limitations:

Users must:

• Define one receiver per host
• Duplicate identical configuration (credentials, channel, etc.)
• Manually maintain large and repetitive YAML configurations

This leads to:

• Poor scalability
• Increased operational overhead
• Error-prone configuration management

---

Is there an existing solution today?

At present, there is no native or recommended way to configure multiple remote hosts within a single windowseventlog receiver instance. Users are required to duplicate receiver definitions for each host.

Describe the solution you'd like

As there is no native or recommended way for this usecase i want to propose this as Enhancement.

Proposed configuration:

receivers:
  windowseventlog:
    channel: security
    remote:
      hosts:
        - host1
        - host2
        - host3
      username: admin
      password: secret

Expected behavior
The receiver should internally:
Create a separate receiver per host
Reuse shared configuration (credentials, channel, polling settings, etc.)

Describe alternatives you've considered

No response

Additional context

No response

Tip

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.}

[github-actions]

Pinging code owners:

• receiver/windowseventlog: @armstrmi @pjanotti

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[pankaj101A]

@pjanotti what are your thoughts?