After integrating Splunk application with Forcepoint ONE SSE using Forcepoint FONE App, you can troubleshoot issues if required.
Replace the <Splunk Index> with actual index in which data is
stored.
The event details should appear for selected time period.
You should configure the Forcepoint FONE App and then restart the Splunk to view SWG logs in Web Analysis dashboard.
Refer to step 7 in Integrating Splunk application with Forcepoint ONE SSE using Forcepoint FONE App to know the details of the form.
There can be three scenarios for this issue:
Scenario 1
The Forcepoint FONE App is running fine and there is no new SWG log event data available in Forcepoint ONE SSE's AWS S3 data lake. In this case, you just have to wait for some time till new SWG log event data is generated.
Scenario 2
There is an issue with the configuration or proxy details provided during the setup of Forcepoint FONE App.
Check the latest connection status to Forcepoint ONE SSE SWG log source by either of the following ways:
sudo su
tail -c 35K /opt/splunk/var/log/splunk/splunkd.log | grep "Connected to log source"Scenario 3
There is an issue with the Forcepoint FONE App other than configuration or proxy issue. In this case, enable the debugging mode in Forcepoint FONE App:
sudo su
cd /opt/splunk/etc/apps/fone/bin"logging.basicConfig(level=logging.INFO, format='%(levelname)s - %(message)s')" line with
the "logging.basicConfig(level=logging.DEBUG, format='%(levelname)s - %(message)s')" line using the Visual (Vi) Editor or similar.sudo su
tail -c 35K /opt/splunk/var/log/splunk/splunkd.log | grep "swg_log_exporter"
cat /opt/splunk/etc/apps/fone/local/state.dbCopy the contents of above two commands on to separate files and share those saved debug logs with Forcepoint support.