[jira] [Commented] (METRON-939) Upgrade ElasticSearch and Kibana

2018-02-10 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/METRON-939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16359635#comment-16359635
 ] 

ASF GitHub Bot commented on METRON-939:
---

Github user wardbekker commented on the issue:

https://github.com/apache/metron/pull/619
  
agreed @nickwallen 


> Upgrade ElasticSearch and Kibana
> 
>
> Key: METRON-939
> URL: https://issues.apache.org/jira/browse/METRON-939
> Project: Metron
>  Issue Type: Improvement
>Reporter: Jon Zeolla
>Assignee: Michael Miklavcic
>Priority: Major
>  Labels: backwards-incompatible
> Attachments: Metron-Dashboard - Kibana.pdf, Metron-Error-Dashboard - 
> Kibana.pdf
>
>
> Upgrade ElasticSearch and Kibana (latest is 5.4 as of writing this).  Among 
> other benefits, this allows us to use periods in field names 
> (https://github.com/elastic/elasticsearch/pull/19937/files), which has been 
> available as of 5.0 and 2.4, and the ability to index an IPv6 address 
> properly 
> (https://www.elastic.co/blog/indexing-ipv6-addresses-in-elasticsearch).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (METRON-939) Upgrade ElasticSearch and Kibana

2018-02-10 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/METRON-939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16359636#comment-16359636
 ] 

ASF GitHub Bot commented on METRON-939:
---

Github user wardbekker closed the pull request at:

https://github.com/apache/metron/pull/619


> Upgrade ElasticSearch and Kibana
> 
>
> Key: METRON-939
> URL: https://issues.apache.org/jira/browse/METRON-939
> Project: Metron
>  Issue Type: Improvement
>Reporter: Jon Zeolla
>Assignee: Michael Miklavcic
>Priority: Major
>  Labels: backwards-incompatible
> Attachments: Metron-Dashboard - Kibana.pdf, Metron-Error-Dashboard - 
> Kibana.pdf
>
>
> Upgrade ElasticSearch and Kibana (latest is 5.4 as of writing this).  Among 
> other benefits, this allows us to use periods in field names 
> (https://github.com/elastic/elasticsearch/pull/19937/files), which has been 
> available as of 5.0 and 2.4, and the ability to index an IPv6 address 
> properly 
> (https://www.elastic.co/blog/indexing-ipv6-addresses-in-elasticsearch).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (METRON-939) Upgrade ElasticSearch and Kibana

2018-02-10 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/METRON-939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16359575#comment-16359575
 ] 

ASF GitHub Bot commented on METRON-939:
---

Github user nickwallen commented on the issue:

https://github.com/apache/metron/pull/619
  
This functionality was completed in #840.  As mentioned in #840 this 
inspired much of that work.  Is there anything else needed from this PR?  If 
not, can you close this PR @wardbekker ?

Thanks




> Upgrade ElasticSearch and Kibana
> 
>
> Key: METRON-939
> URL: https://issues.apache.org/jira/browse/METRON-939
> Project: Metron
>  Issue Type: Improvement
>Reporter: Jon Zeolla
>Assignee: Michael Miklavcic
>Priority: Major
>  Labels: backwards-incompatible
> Attachments: Metron-Dashboard - Kibana.pdf, Metron-Error-Dashboard - 
> Kibana.pdf
>
>
> Upgrade ElasticSearch and Kibana (latest is 5.4 as of writing this).  Among 
> other benefits, this allows us to use periods in field names 
> (https://github.com/elastic/elasticsearch/pull/19937/files), which has been 
> available as of 5.0 and 2.4, and the ability to index an IPv6 address 
> properly 
> (https://www.elastic.co/blog/indexing-ipv6-addresses-in-elasticsearch).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (METRON-1318) Cannot deploy into EC2

2018-02-10 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/METRON-1318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16359566#comment-16359566
 ] 

ASF GitHub Bot commented on METRON-1318:


Github user asfgit closed the pull request at:

https://github.com/apache/metron/pull/930


> Cannot deploy into EC2
> --
>
> Key: METRON-1318
> URL: https://issues.apache.org/jira/browse/METRON-1318
> Project: Metron
>  Issue Type: Bug
>Affects Versions: 0.4.2
> Environment: AWS
>Reporter: Paweł Białasiewicz
>Priority: Major
>
> I'm trying to deploy Metron on AWS using the cloud deployment method. 
> It looks like it is having problems with building the master node 
> {code:java}
> [metron-test] sensors,ambari_master,ec2,monit
> {code}
> I tried rebuilding the node from scratch and running the run script multiple 
> times, always with the same result.
> During the installation I'm getting the following log:
> {code:java}
> TASK [setup] 
> ***
> ok: [localhost]
> ok: [ec2-34-227-190-43.compute-1.amazonaws.com]
> ok: [ec2-34-201-150-57.compute-1.amazonaws.com]
> ok: [ec2-54-162-174-97.compute-1.amazonaws.com]
> ok: [ec2-34-207-187-45.compute-1.amazonaws.com]
> ok: [ec2-52-91-15-158.compute-1.amazonaws.com]
> ok: [ec2-34-229-153-26.compute-1.amazonaws.com]
> ok: [ec2-52-73-77-81.compute-1.amazonaws.com]
> ok: [ec2-54-175-242-208.compute-1.amazonaws.com]
> ok: [ec2-54-85-210-26.compute-1.amazonaws.com]
> ok: [ec2-34-229-86-210.compute-1.amazonaws.com]
> TASK [metron-builder : Build Metron] 
> ***
> fatal: [ec2-34-227-190-43.compute-1.amazonaws.com -> localhost]: FAILED! => 
> {"changed": true, "cmd": "cd 
> /root/metron/metron-deployment/amazon-ec2/../playbooks/../.. && mvn clean 
> package -DskipTests -T 2C -P HDP-2.5.0.0,mpack", "delta": "0:00:03.308032", 
> "end": "2017-11-16 14:04:52.835967", "failed": true, "rc": 1, "start": 
> "2017-11-16 14:04:49.527935", "stderr": "", "stdout": "Warning: JAVA_HOME 
> environment variable is not set.\n[INFO] Scanning for projects...\n[INFO] 
> \n[INFO]
>  Reactor Build Order:\n[INFO] \n[INFO] Metron\n[INFO] metron-stellar\n[INFO] 
> stellar-common\n[INFO] metron-analytics\n[INFO] metron-maas-common\n[INFO] 
> metron-platform\n[INFO] metron-zookeeper\n[INFO] 
> metron-test-utilities\n[INFO] metron-integration-test\n[INFO] 
> metron-maas-service\n[INFO] metron-common\n[INFO] metron-statistics\n[INFO] 
> metron-writer\n[INFO] metron-storm-kafka-override\n[INFO] 
> metron-storm-kafka\n[INFO] metron-hbase\n[INFO] 
> metron-profiler-common\n[INFO] metron-profiler-client\n[INFO] 
> metron-profiler\n[INFO] metron-hbase-client\n[INFO] metron-enrichment\n[INFO] 
> m
> etron-indexing\n[INFO] metron-solr\n[INFO] metron-pcap\n[INFO] 
> metron-parsers\n[INFO] metron-pcap-backend\n[INFO] 
> metron-data-management\n[INFO] metron-api\n[INFO] metron-management\n[INFO] 
> elasticsearch-shaded\n[INFO] metron-elasticsearch\n[INFO] 
> metron-deployment\n[INFO] Metron Ambari Management Pack\n[INFO] 
> metron-contrib\n[INFO] metron-docker\n[INFO] metron-interface\n[INFO] 
> metron-config\n[INFO] metron-alerts\n[INFO] metron-rest-client\n[INFO] 
> metron-rest\n[INFO] site-book\n[INFO] 3rd party Functions (just for 
> tests)\n[INFO] \n[INFO] Using the MultiThreadedBuilder implementation with a 
> thread count of 4\n[INFO] 
> \n[INFO] 
> \n[INFO]
>  Building Metron 0.4.2\n[INFO] 
> \n[INFO]
>  \n[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ Metron 
> ---\n[INFO] \n[INFO] --- maven-enforcer-plugin:1.4.1:enforce 
> (enforce-versions) @ Metron ---\n[INFO] \n[INFO] --- 
> jacoco-maven-plugin:0.7.9:prepare-agent (default) @ Metron ---
> \n[INFO] argLine set to 
> -javaagent:/root/.m2/repository/org/jacoco/org.jacoco.agent/0.7.9/org.jacoco.agent-0.7.9-runtime.jar=destfile=/root/metron/target/jacoco.exec\n[INFO]
>  \n[INFO] --- jacoco-maven-plugin:0.7.9:report (report) @ Metron ---\n[INFO] 
> Skipping JaCoCo execution due to missing execution data file.\n[INFO] 
> \n[INFO] 
> \n[INFO]
>  Building metron-stellar 0.4.2\n[INFO] 
> \n[INFO]
>  
> \n[INFO] 
> \n[INFO]
>  Building metron-analytics 0.4.2\n[INFO]