This Confluence has been LDAP enabled, if you are an ASF Committer, please use your LDAP Credentials to login. Any problems file an INFRA jira ticket please.

Skip to end of metadata
Go to start of metadata
Step 0 – Verify Release
Verify that the maven artifacts are the right version by inspecting the top level pom.xml and looking at the version.
Verify that the release bits are the signed properly by running:
gpg --import KEYS
gpg --verify ./apache-metron-$VERSION-incubating.tar.gz.asc apache-metron-$VERSION-incubating.tar.gz
Step 1 – Build Metron

cd incubator-metron/
mvn clean install

Verify that all tests are passing

Step 2 – Deploy metron as a single VM via vagrant and ansible

cd metron-deployment/vagrant/full-dev-platform
vagrant plugin install vagrant-hostmanager
vagrant up

For a more complete set of instructions refer to: and



Verify metron is working:
- Check Ambari to make sure all the services are up by going to ambari in a browser at http://node1:8080
- Check Storm to make sure all the topologies are up
      From Ambari navigate to Storm -> Quick Links -> Storm UI
- Check that the enrichment topology has emitted some data (could take a few minutes to show
up in the Storm UI)
- Check indexes to make sure indexing is done correctly and data is visualized in Kibana in
a browser at http://node1:5000
- Check that some data is written into HDFS for at least one of the data sources
      Look in HDFS under /apps/metron/indexing/indexed/yaf|bro|snort
      This can be done by running hdfs dfs -ls /apps/metron/indexing/indexed/
- Test the Management UI at http://node1:4200/


Step 3 (optional) – Verify AWS Multi-Node Deploy with Ansible (NOTE: This will cost money to deploy AWS servers)
cd metron-deployment/amazon-ec2

For a more complete set of instructions refer to:

To verify the working build go through the same verifications as in Step2, but on AWS.  Reference
playbook.yml for location of the services.
Ambari-master contains Ambari, web contains Kibana and sensors.
  • No labels