Splunk Add-on for Microsoft Windows to OTel Collector mapping
Maps Splunk Add-on for Windows input stanzas to OpenTelemetry Collector receivers and identifies collection gaps and workarounds.
Scope and source
This mapping covers event and log ingestion only. Data model normalization, including field extractions in props.conf, falls outside its scope.
Source: inputs.conf from Splunk_TA_windows (2024).
Windows Event Log channels
Receiver: windowseventlogreceiver. See the windowseventlogreceiver documentation.
| inputs.conf stanza | Enabled | OTel channel |
|---|---|---|
WinEventLog://Application |
no |
channel: Application |
WinEventLog://Security |
no |
channel: Security |
WinEventLog://System |
no |
channel: System |
WinEventLog://Microsoft-Windows-PrintService/Operational |
no |
channel: Microsoft-Windows-PrintService/Operational |
WinEventLog://ForwardedEvents |
no |
channel: ForwardedEvents |
WinEventLog://DFS Replication |
no |
channel: DFS Replication |
WinEventLog://Directory Service |
no |
channel: Directory Service |
WinEventLog://File Replication Service |
no |
channel: File Replication Service |
WinEventLog://Key Management Service |
no |
channel: Key Management Service |
WinEventLog://DNS Server |
no |
channel: DNS Server |
WinEventLog://Microsoft-Windows-Windows Defender/Operational |
no |
channel: Microsoft-Windows-Windows Defender/Operational |
Security event deny list gap
Splunk inputs.conf event filters:
blacklist1 = EventCode="4662" Message="Object Type:(?!\s*groupPolicyContainer)"
blacklist2 = EventCode="566" Message="Object Type:(?!\s*groupPolicyContainer)"
The windowseventlogreceiver exclude_events setting supports filtering by event_ids, but it doesn't support message-body regular expressions.
To replicate these filters, use a filterprocessor with OTTL conditions downstream.
XML event rendering
Splunk collects the Application, Security, and System channels with renderXml=true, which returns events in XML format. The windowseventlogreceiver delivers the raw XML event by default, which provides equivalent behavior.
File and monitor inputs
Receiver: filelogreceiver. See the filelogreceiver documentation.
| inputs.conf stanza | Enabled | OTel include path |
|---|---|---|
monitor://$WINDIR\System32\DHCP (whitelist=DhcpSrvLog*) |
no |
include: ['C:\Windows\System32\DHCP\DhcpSrvLog*'] |
monitor://$WINDIR\WindowsUpdate.log |
no |
include: ['C:\Windows\WindowsUpdate.log'] |
monitor://$SPLUNK_HOME\var\log\Splunk_TA_windows\WindowsUpdate.log |
no |
include: ['<splunk_home>\var\log\Splunk_TA_windows\WindowsUpdate.log'] |
monitor://$WINDIR\debug\netlogon.log |
no |
include: ['C:\Windows\debug\netlogon.log'] |
monitor://$WINDIR\System32\LogFiles\Firewall\* |
no |
include: ['C:\Windows\System32\LogFiles\Firewall\*'] |
monitor://$SPLUNK_HOME\var\log\Splunk_TA_windows\AnalyticalDNS\dns_log.log |
no |
include: ['<splunk_home>\var\log\Splunk_TA_windows\AnalyticalDNS\dns_log.log'] |
MonitorNoHandle gap for the DNS debug log
The Splunk stanza MonitorNoHandle://$WINDIR\System32\Dns\dns.log uses a Windows API to read files that another process holds open with exclusive locks. The DNS debug process holds the live dns.log file open this way.
The filelogreceiver opens files normally, so it can fail or return incomplete reads when another process locks a file. No reliable OTel equivalent exists. As a workaround, use a scheduled script to copy the file before monitoring it.
Scripted and PowerShell inputs
OTel has no built-in receiver that executes scripts on a schedule. The contrib repository has no execreceiver.
As a workaround, run the script externally, for example with Task Scheduler, write its output to a file, and monitor that file with filelogreceiver.
| inputs.conf stanza | Enabled | Schedule |
|---|---|---|
script://win_listening_ports.bat |
no |
hourly |
script://win_installed_apps.bat |
no |
daily |
script://win_timesync_status.bat |
no |
hourly |
script://win_timesync_configuration.bat |
no |
hourly |
script://netsh_address.bat |
no |
daily |
script://runpowershell.cmd nt6-repl-stat.ps1 |
no |
5 min |
script://runpowershell.cmd nt6-health.ps1 |
no |
5 min |
script://runpowershell.cmd nt6-siteinfo.ps1 |
no |
hourly |
script://runpowershell.cmd dns-zoneinfo.ps1 |
no |
hourly |
script://runpowershell.cmd dns-health.ps1 |
no |
hourly |
script://runpowershell.cmd dns-analytical.ps1 |
no |
hourly |
powershell://generate_windows_update_logs |
no |
daily |
powershell://Replication-Stats |
no |
5 min |
powershell://AD-Health |
no |
5 min |
powershell://Siteinfo |
no |
15 min |
powershell://windows_bios_data |
no |
daily |
Performance counters
Receiver: windowsperfcountersreceiver. See the windowsperfcountersreceiver documentation.
The source configuration sets all perfmon:// inputs in inputs.conf to no. Counter names and instance wildcards (instances = *) map directly to the receiver's instances and counters configuration.
| inputs.conf stanza | Enabled | OTel object |
|---|---|---|
perfmon://CPU |
no |
object: Processor |
perfmon://Processor |
no |
object: Processor |
perfmon://LogicalDisk |
no |
object: LogicalDisk |
perfmon://PhysicalDisk |
no |
object: PhysicalDisk |
perfmon://Memory |
no |
object: Memory |
perfmon://Network |
no |
object: Network Interface |
perfmon://Network_Interface |
no |
object: Network Interface |
perfmon://Process |
no |
object: Process |
perfmon://ProcessorInformation |
no |
object: Processor Information |
perfmon://System |
no |
object: System |
perfmon://DFS_Replicated_Folders |
no |
object: DFS Replicated Folders |
perfmon://NTDS |
no |
object: NTDS |
perfmon://DNS |
no |
object: DNS |
Inputs without an OTel equivalent
These inputs use Splunk-proprietary collection mechanisms that have no receiver in the OTel contrib repository.
| inputs.conf stanza | Type | Gap reason |
|---|---|---|
WinHostMon://Computer |
Splunk proprietary | WMI-based host inventory; no OTel receiver. |
WinHostMon://Process |
Splunk proprietary | Same as above. |
WinHostMon://Processor |
Splunk proprietary | Same as above. |
WinHostMon://NetworkAdapter |
Splunk proprietary | Same as above. |
WinHostMon://Service |
Splunk proprietary | Same as above. |
WinHostMon://OperatingSystem |
Splunk proprietary | Same as above. |
WinHostMon://Disk |
Splunk proprietary | Same as above. |
WinHostMon://Driver |
Splunk proprietary | Same as above. |
WinHostMon://Roles |
Splunk proprietary | Same as above. |
WinPrintMon://printer |
Splunk proprietary | Print monitoring; no OTel receiver. |
WinPrintMon://driver |
Splunk proprietary | Same as above. |
WinPrintMon://port |
Splunk proprietary | Same as above. |
WinNetMon://inbound |
Splunk proprietary | Network connection monitoring; no OTel receiver. |
WinNetMon://outbound |
Splunk proprietary | Same as above. |
admon://default |
Splunk proprietary | AD object change monitoring; no OTel receiver. |
WinRegMon://default |
Splunk proprietary | Registry change monitoring; no OTel receiver. |
WinRegMon://hkcu_run |
Splunk proprietary | Same as above. |
WinRegMon://hklm_run |
Splunk proprietary | Same as above. |
Overall coverage summary
| Input type | OTel receiver | Coverage |
|---|---|---|
| Windows Event Log channels | windowseventlogreceiver |
Full, except message regular expression event filtering. |
| File monitoring | filelogreceiver |
Full, except exclusively locked files. |
| DNS debug log (locked file) | None reliable | Gap; workaround required. |
| Scripted and PowerShell outputs | None built in | Gap; external scheduling workaround needed. |
| Performance counters | windowsperfcountersreceiver |
Full. |
WinHostMon, WinPrintMon, and WinNetMon |
None | Gap; no OTel receiver. |
Active Directory Monitor (admon) |
None | Gap; no OTel receiver. |
Registry Monitor (WinRegMon) |
None | Gap; no OTel receiver. |