You need to tell Elasticsearch to treat that field as a date. Once Elasticsearch knows that it is a date, then Kibana will display it properly. The Elasticsearch template for Bro that is shipped with Metron can be used as a guide. The template already handles this situation [1]. Either directly install that template or create your own template using Metron's as a guide. You can either define it specifically for one field, like this. Or specify multiple fields that should be treated as dates, like this. Also, note that the change will only take effect after the index rolls. if the indices roll every hour, then you need to wait until the next hour to see the change. Or if your data is disposable, just delete the index and see your change take effect immediately. ... View more

I doubt that is possible. At least, I don't know how to do it. Part of the Vagrant definition for each of these environments defines the virtual network that is used by each VM. I am not sure how you would bridge the two networks after each of these environments are already running. You could definitely create you own Vagrant definition that accomplishes this, but it is not something that can be done with the existing environments. ... View more

The `fastcapa-test-environment` was made specifically for testing Fastcapa only. I would suggest that you install Metron using one of the other installation methods and then after you have Metron installed, install Fastcapa. That will be much easier than installing Metron on top of `fastcapa-test-environment`. ... View more

The `fastcapa-test-environment` is only designed to test Fastcapa. It does not install Ambari or Kibana. The Kafka Broker is installed on the `source` host. You need to `vagrant ssh source`. You can see what is installed and where by looking at `metron-deployment/vagrant/fastcapa-test-platform/playbook.yml`. ... View more

If I am not mistaken, this is typically the exact error that you see when you are using an Ansible version that is not 2.0.0.2. Are you sure that when you upgraded `setuptools` (I see that you did this in another HCC thread) that the Ansible version did not also get quietly upgraded? I've seen this happen before. ... View more

All your software versions look correct. I would recommend trying master versus that TP1 release. There is a lot more functionality and the deployment process should be smoother. ... View more

You can also simply paste the output of `metron-deployment/scripts/platform-info.sh`. That should give us a good understanding of your environment. ... View more

Also, if you don't mind, please run the following script and post the information back to us. This is only available in master and was not included in the technical preview release. $ ./metron-deployment/scripts/platform-info.sh Metron 0.1BETA -- * master -- commit 91bb445e4c7b8a1f9f43fb6410c666b02baaf921 Author: nickwallen <nick@nickallen.org> Date: Tue May 3 17:47:37 2016 -0400 METRON-128 Install instructions added for 'Single Node Vagrant' (nickwallen) closes apache/incubator-metron#100 -- -- ansible 2.0.1.0 config file = configured module search path = Default w/o overrides -- Vagrant 1.8.1 -- Python 2.7.11 -- Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T11:41:47-05:00) Maven home: /usr/local/Cellar/maven/3.3.9/libexec Java version: 1.8.0_66, vendor: Oracle Corporation Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_66.jdk/Contents/Home/jre Default locale: en_US, platform encoding: UTF-8 OS name: "mac os x", version: "10.11.4", arch: "x86_64", family: "mac" -- Darwin HW12402.local 15.4.0 Darwin Kernel Version 15.4.0: Fri Feb 26 22:08:05 PST 2016; root:xnu-3248.40.184~3/RELEASE_X86_64 x86_64 ... View more