Install all the dependent node_modules using the following command
cd metron/metron-interface/metron-alerts npm install
UI can be run by using the following command
./scripts/start-dev.sh
NOTE: In the development mode ui by default connects to ES at http://node1:9200 for fetching data. If you wish to change it you can change the ES url at metron/metron-interface/metron-alerts/proxy.conf.json
An expressjs server is available for mocking the elastic search api.
Run e2e webserver :
cd metron/metron-interface/metron-alerts sh ./scripts/start-server-for-e2e.sh
run e2e test using the following command
cd metron/metron-interface/metron-alerts npm run e2e
E2E tests uses data from full-dev wherever applicable. The tests assume rest-api’s are available @http://node1:8082
NOTE: e2e tests covers all the general workflows and we will extend them as we need
Build Metron:
mvn clean package -DskipTests
Copy metron/metron-interface/metron-alerts/target/metron-alerts-METRON_VERSION-archive.tar.gz to the desired host.
Untar the archive in the target directory. The directory structure will look like:
bin start_alerts_ui.sh web alerts-ui package.json server.js web assets (html, css, js, ...)
Expressjs webserver script is included in the build that will serve the application. (The script has few rewrite rules and we can replace expressjs with any other webserver)
Then start the application with the script:
./bin/start_alerts_ui.sh Usage: server.js -p [port] -r [restUrl] Options: -p Port to run metron alerts ui [required] -r, --resturl Url where elastic search rest api is available [required]