You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Splunk HFW inside the bosh deployment relies on the $SPLUNK_HOME/etc/system/local/outputs.conf, $SPLUNK_HOME/etc/apps/splunk_httpinputs/inputs.conf etc to do correct event forwarding. After deploying splunk-firehose-nozzle-release to bosh, i found the configuration directory is missing /var/vcap/jobs/splunk-forwarder/config/, and i will need manually create the directory and manually create the following sub directories and configuration files and do correct symlink to make the forwarding work.
vagrant@agent-id-bosh-0:/var/vcap$ ls /var/vcap/jobs/splunk-forwarder/config/ -lR
/var/vcap/jobs/splunk-forwarder/config/:
total 8
drwxr-xr-x 2 root root 4096 May 26 22:31 apps_splunk_httpinput_local
drwxr-xr-x 2 root root 4096 May 26 22:31 system_local
/var/vcap/jobs/splunk-forwarder/config/apps_splunk_httpinput_local:
total 8
-rw-r--r-- 1 root root 168 May 26 22:31 inputs.conf
-rw-r--r-- 1 root root 44 May 26 22:31 limits.conf
/var/vcap/jobs/splunk-forwarder/config/system_local:
total 8
-rw-r--r-- 1 root root 0 May 26 22:31 inputs.conf
-rw-r--r-- 1 root root 165 May 26 22:31 outputs.conf
-rw-r--r-- 1 root root 30 May 26 22:31 web.conf
The text was updated successfully, but these errors were encountered:
Splunk HFW inside the bosh deployment relies on the $SPLUNK_HOME/etc/system/local/outputs.conf, $SPLUNK_HOME/etc/apps/splunk_httpinputs/inputs.conf etc to do correct event forwarding. After deploying splunk-firehose-nozzle-release to bosh, i found the configuration directory is missing
/var/vcap/jobs/splunk-forwarder/config/
, and i will need manually create the directory and manually create the following sub directories and configuration files and do correct symlink to make the forwarding work.The text was updated successfully, but these errors were encountered: