![]() We have installed the Universal Forwarder on one of our laptops and created the following configuration within the nf file. The last step is to install Splunk Universal Forwarder on the roaming user’s laptop and configure HTTP Out using the new httpout stanza in nf. Step 3: Configure The Universal Forwarder The AWS Application Load Balancer provides a DNS A record which we will be using in the Universal Forwarder outputs configuration. The Load Balancer has a listener created for receiving connection requests on port 443 and forwards them to the Splunk Indexer on port 8088 (the default port used for HEC). For this use case, we have created an Application Load Balancer in AWS. HTTP Out on the Splunk Universal Forwarder supports Network Load Balancers and Application Load Balancers. The next thing we need is a Load Balancer which is Internet facing. Detailed steps for enabling HEC and creating a token can be found on the Splunk Documentation site here. On our Splunk Indexers we have already configured the HTTP Event Collector (HEC) and created a token for receiving data from the Universal Forwarder.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |