The DCN uses port 443 to determine the kind of data to collect, such as performance, inventory, or hierarchy data. After Splunk App for VMware establishes a connection with vCenter Server, the DCN uses port 443 to obtain the credentials for vCenter Server. You can choose to edit the configuration files through the command line. Uses port 9997 to forward data it has retrieved from the vCenter Server using the API. In the current state, the indexer configuration is in the nf and which is taking effect. Effectively when I deploy my application, the sidecar is starting. The forwarder writes configurations for forwarding data to nf in $SPLUNK_HOME/etc/system/local/).Įdit the configuration files through the command line The splunk universal forwarder is setup as a different docker image where I copy custom nf and nf through docker COPY (shown below). This prevents typos and other mistakes that can occur when you edit configuration files directly. When you make configuration changes with the CLI, the universal forwarder writes the configuration files.
You can edit them however you normally edit files, such as through a text editor or the command line, or you can use the Splunk Deployment Server.
nf for connecting to a deployment server.nf for connection and performance tuning.nf controls how the forwarder sends data to an indexer or other forwarder.nf controls how the forwarder collects data.Navigate to nf in $SPLUNK_HOME/etc/system/local/ to locate your Universal Forwarder configuration files. Optionally edit the Universal forwarder configuration files to further modify how your machine data is streamed to your indexers. Configure the universal forwarder using configuration files
0 kommentar(er)
