Splunk topology:
Logs from all network devices, get forwarded to two Universal Intermediate Forwarders which then send them to On-Prem Indexers and further forwarded to another Forwarder hosted outside.
There is a queue blockage issue on the Universal Forwarder (UF).
The file props.conf is configured on the UFs.
props.conf can never be configured on the UF, however, UF doesn't have parsing capabilities hence the performance/queue blockage issues.
Here are how some common Splunk server configurations correspond to these phases:
| Universal/Light Forwarder | ? | Indexer |
| Input | ? | Parsing, Indexing, Search |
| Heavy Forwarder | ? | Indexer |
| Input, Parsing | ? | Indexing, Search |
| Universal/Light Forwarder | ? | Indexer | ? | Search Head |
| Input | ? | Parsing, Indexing | ? | Search |
| Universal/Light Forwarder | ? | Heavy Forwarder | ? | Indexer |
| Input | ? | Parsing | ? | Indexing, Search |
| Universal/Light Forwarder | ? | Heavy Forwarder | ? | Indexer | ? | Search Head |
| Input | ? | Parsing | ? | Indexing | ? | Search |
Moving the props.conf from Universal forwarder to Indexer resolved the queue blockage.
Splunk Community
Why is Universal Forwarder unable to process props.conf configuration for structured data?
Why-is-Universal-Forwarder-unable-to-process-props-conf
Splunk Wiki
Where do I configure my Splunk settings?
Where_do_I_configure_my_Splunk_settings
| Revision | Publish Date | Comments |
|---|---|---|
1.0 |
29-Sep-2026
|
Initial Release |