Run the Threat View Event Simulator (optional)

The Threat View application receives threat events from mobile applications and visualizes them in dashboards. In an evaluation setup when there are no real mobile applications the Event Simulator can be used to provide data. The simulator will simulate mobile applications and send threat events to the data collector with a rate of about four events per second. In addition, it will connect to the database and insert mock historical data to evaluate the Threat View application.

The script to deploy Threat View, run_threat-view.sh, does not start the Event Simulator. To start the simulator, run the run_simulator.sh script located in the base directory. This will load the simulator image from the images archive folder and use Docker Compose to spin up the service.

To populate example data and start the simulator, call run_simulator.shafter run_threat-view.sh has completed. The Threat View services stack must be up and running before the simulator can be started. If the Threat View stack is not running the simulator startup will fail.

We recommend letting the Threat View application and the simulator run for a longer time (until the next day) to see realistic results in the visualizations. This ensure that the visualizations will show tomorrow the data that the simulator sent today. If the Threat View application is shut down and restarted, the database is cleared, and the data collection progress is lost.

For more information, see also Installation of OneSpan Threat View (evaluation package) and the installation recommendations.