[jira] [Assigned] (METRON-2091) SimpleHBaseEnrichmentWriterTest should be included in tests
[ https://issues.apache.org/jira/browse/METRON-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Leet reassigned METRON-2091: --- Assignee: Ryan Merriman > SimpleHBaseEnrichmentWriterTest should be included in tests > --- > > Key: METRON-2091 > URL: https://issues.apache.org/jira/browse/METRON-2091 > Project: Metron > Issue Type: Bug >Reporter: Ryan Merriman >Assignee: Ryan Merriman >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > The `SimpleHBaseEnrichmentWriterTest` test was accidentally left in the > metron-writer module instead of being moved to a new module. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (METRON-2091) SimpleHBaseEnrichmentWriterTest should be included in tests
[ https://issues.apache.org/jira/browse/METRON-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Leet updated METRON-2091: Fix Version/s: 0.7.1 > SimpleHBaseEnrichmentWriterTest should be included in tests > --- > > Key: METRON-2091 > URL: https://issues.apache.org/jira/browse/METRON-2091 > Project: Metron > Issue Type: Bug >Reporter: Ryan Merriman >Assignee: Ryan Merriman >Priority: Major > Fix For: 0.7.1 > > Time Spent: 0.5h > Remaining Estimate: 0h > > The `SimpleHBaseEnrichmentWriterTest` test was accidentally left in the > metron-writer module instead of being moved to a new module. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] [metron] asfgit closed pull request #1392: METRON-2091: SimpleHBaseEnrichmentWriterTest should be included in tests
asfgit closed pull request #1392: METRON-2091: SimpleHBaseEnrichmentWriterTest should be included in tests URL: https://github.com/apache/metron/pull/1392 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [metron] merrimanr commented on issue #1391: METRON-2090: Full dev is failing with missing org.mortbay.jetty:jetty-util:jar:6.1.26.hwx dependency
merrimanr commented on issue #1391: METRON-2090: Full dev is failing with missing org.mortbay.jetty:jetty-util:jar:6.1.26.hwx dependency URL: https://github.com/apache/metron/pull/1391#issuecomment-486346344 The latest travis failure was caused by new transitive dependencies being pulled in as a result of the initial changes in this PR. I don't think this is correct so I added the `hadoop-common` dependency before the `storm-hdfs` and that resolved the issue. We include `hadoop-common` near the top of several poms so I felt it was better to keep things consistent. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Updated] (METRON-1963) Remove left over integration test from before refactoring
[ https://issues.apache.org/jira/browse/METRON-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Leet updated METRON-1963: Fix Version/s: (was: 0.7.0) 0.7.1 > Remove left over integration test from before refactoring > - > > Key: METRON-1963 > URL: https://issues.apache.org/jira/browse/METRON-1963 > Project: Metron > Issue Type: Bug >Reporter: Otto Fowler >Assignee: Otto Fowler >Priority: Major > Fix For: 0.7.1 > > Time Spent: 40m > Remaining Estimate: 0h > > https://github.com/apache/metron/tree/master/metron-platform/metron-parsers -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (METRON-589) Dist area should only contain latest release
[ https://issues.apache.org/jira/browse/METRON-589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Leet updated METRON-589: --- Fix Version/s: (was: 0.7.1) 0.3.1 > Dist area should only contain latest release > > > Key: METRON-589 > URL: https://issues.apache.org/jira/browse/METRON-589 > Project: Metron > Issue Type: Bug >Reporter: John D. Ament >Assignee: Casey Stella >Priority: Major > Fix For: 0.3.1 > > > The dist area https://dist.apache.org/repos/dist/release/incubator/metron/ > should only contain the latest release. Older releases are found in the > archives. > Most projects don't directly link to this area, but instead provide the dyn > style links. See Geode for example: > http://geode.incubator.apache.org/releases/ - this works for older releases > as well. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (METRON-589) Dist area should only contain latest release
[ https://issues.apache.org/jira/browse/METRON-589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16825340#comment-16825340 ] Justin Leet commented on METRON-589: [~msmiklavcic] You're right, I'll figure it out. This is because I did a bulk search and apparently hit this ticket without catching it. > Dist area should only contain latest release > > > Key: METRON-589 > URL: https://issues.apache.org/jira/browse/METRON-589 > Project: Metron > Issue Type: Bug >Reporter: John D. Ament >Assignee: Casey Stella >Priority: Major > Fix For: 0.7.1 > > > The dist area https://dist.apache.org/repos/dist/release/incubator/metron/ > should only contain the latest release. Older releases are found in the > archives. > Most projects don't directly link to this area, but instead provide the dyn > style links. See Geode for example: > http://geode.incubator.apache.org/releases/ - this works for older releases > as well. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (METRON-650) Remove Kraken Maven dependency on opensoc github repo
[
https://issues.apache.org/jira/browse/METRON-650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Miklavcic updated METRON-650:
-
Fix Version/s: (was: 0.3.1)
> Remove Kraken Maven dependency on opensoc github repo
> -
>
> Key: METRON-650
> URL: https://issues.apache.org/jira/browse/METRON-650
> Project: Metron
> Issue Type: Improvement
>Reporter: Michael Miklavcic
>Priority: Major
>
> Metron common's pom is referencing the opensoc repo to get Kraken:
>
>
> Metron-Kraken-Repo
> Metron Kraken Repository
> https://raw.github.com/opensoc/kraken/mvn-repo
>
>
> ...
>
> org.krakenapps
> kraken-pcap
> ${global_pcap_version}
>
>
> slf4j-api
> org.slf4j
>
>
> slf4j-simple
> org.slf4j
>
>
>
> This library does not currently reside in mvn central (searched by package
> and libname) and should instead be staged in Apache with Metron.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (METRON-589) Dist area should only contain latest release
[ https://issues.apache.org/jira/browse/METRON-589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16825334#comment-16825334 ] Michael Miklavcic commented on METRON-589: -- [~justinleet], not sure if it matters, but this is from 2016. Should this be set to something other than 0.7.1, e.g. 0.3.1 or some such? > Dist area should only contain latest release > > > Key: METRON-589 > URL: https://issues.apache.org/jira/browse/METRON-589 > Project: Metron > Issue Type: Bug >Reporter: John D. Ament >Assignee: Casey Stella >Priority: Major > Fix For: 0.7.1 > > > The dist area https://dist.apache.org/repos/dist/release/incubator/metron/ > should only contain the latest release. Older releases are found in the > archives. > Most projects don't directly link to this area, but instead provide the dyn > style links. See Geode for example: > http://geode.incubator.apache.org/releases/ - this works for older releases > as well. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (METRON-650) Remove Kraken Maven dependency on opensoc github repo
[
https://issues.apache.org/jira/browse/METRON-650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16825330#comment-16825330
]
Justin Leet commented on METRON-650:
I don't think we have a typical answer. I'm fine with Done + no version.
> Remove Kraken Maven dependency on opensoc github repo
> -
>
> Key: METRON-650
> URL: https://issues.apache.org/jira/browse/METRON-650
> Project: Metron
> Issue Type: Improvement
>Reporter: Michael Miklavcic
>Priority: Major
> Fix For: 0.3.1
>
>
> Metron common's pom is referencing the opensoc repo to get Kraken:
>
>
> Metron-Kraken-Repo
> Metron Kraken Repository
> https://raw.github.com/opensoc/kraken/mvn-repo
>
>
> ...
>
> org.krakenapps
> kraken-pcap
> ${global_pcap_version}
>
>
> slf4j-api
> org.slf4j
>
>
> slf4j-simple
> org.slf4j
>
>
>
> This library does not currently reside in mvn central (searched by package
> and libname) and should instead be staged in Apache with Metron.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (METRON-650) Remove Kraken Maven dependency on opensoc github repo
[
https://issues.apache.org/jira/browse/METRON-650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16825328#comment-16825328
]
Michael Miklavcic commented on METRON-650:
--
[~justinleet] IIRC, this is not relevant any longer. We don't have a "won't
fix" Done option - what do we typically do in that case? Done + no version?
> Remove Kraken Maven dependency on opensoc github repo
> -
>
> Key: METRON-650
> URL: https://issues.apache.org/jira/browse/METRON-650
> Project: Metron
> Issue Type: Improvement
>Reporter: Michael Miklavcic
>Priority: Major
> Fix For: 0.3.1
>
>
> Metron common's pom is referencing the opensoc repo to get Kraken:
>
>
> Metron-Kraken-Repo
> Metron Kraken Repository
> https://raw.github.com/opensoc/kraken/mvn-repo
>
>
> ...
>
> org.krakenapps
> kraken-pcap
> ${global_pcap_version}
>
>
> slf4j-api
> org.slf4j
>
>
> slf4j-simple
> org.slf4j
>
>
>
> This library does not currently reside in mvn central (searched by package
> and libname) and should instead be staged in Apache with Metron.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] [metron] ottobackwards edited a comment on issue #1261: METRON-1860 new developer option for ansible in docker to deploy to vagrant
ottobackwards edited a comment on issue #1261: METRON-1860 new developer option for ansible in docker to deploy to vagrant URL: https://github.com/apache/metron/pull/1261#issuecomment-486301641  > NOTE: I added 'awareness' to not run the rpm docker if we were in the ansible docker a while ago This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [metron] ottobackwards commented on issue #1261: METRON-1860 new developer option for ansible in docker to deploy to vagrant
ottobackwards commented on issue #1261: METRON-1860 new developer option for ansible in docker to deploy to vagrant URL: https://github.com/apache/metron/pull/1261#issuecomment-486301641  > NOTE: I added 'awareness' to not run the rpm docker if we where in the ansible docker a while ago This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Issue Comment Deleted] (METRON-2088) Support HDP 3.1.0
[ https://issues.apache.org/jira/browse/METRON-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Allen updated METRON-2088: --- Comment: was deleted (was: This document was also created during scoping: https://docs.google.com/spreadsheets/d/1ZHAOHk8qMODoMFkKsFydaeJKRqu3jkZFhHhJYjNgMe8/edit#gid=0) > Support HDP 3.1.0 > - > > Key: METRON-2088 > URL: https://issues.apache.org/jira/browse/METRON-2088 > Project: Metron > Issue Type: New Feature >Reporter: Nick Allen >Assignee: Nick Allen >Priority: Major > > Metron currently supports HDP 2.6.5. We need to upgrade Metron to run against > the stack provided by HDP 3.1.0. > HDP Component Versions > * [HDP > 3.1.0|https://docs.hortonworks.com/HDPDocuments/HDP3/HDP-3.1.0/release-notes/content/comp_versions.html] > > * [HDP > 2.6.5|https://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.6.5/bk_release-notes/content/comp_versions.html] > * [HDP > 2.5.6|https://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.5.6/bk_release-notes/content/comp_versions.html] > See initial [discuss thread > here.|https://lists.apache.org/thread.html/37cc29648f0592cc39d3c78a0d07fce38521bdbbc4cf40e022a7a8ea@%3Cdev.metron.apache.org%3E] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] [metron] ottobackwards commented on issue #1261: METRON-1860 new developer option for ansible in docker to deploy to vagrant
ottobackwards commented on issue #1261: METRON-1860 new developer option for ansible in docker to deploy to vagrant URL: https://github.com/apache/metron/pull/1261#issuecomment-486296150 No, it is not accurate exactly, I'll post an updated version of that This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (METRON-2088) Support HDP 3.1.0
[ https://issues.apache.org/jira/browse/METRON-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16825246#comment-16825246 ] Nick Allen commented on METRON-2088: This document was also created during scoping: https://docs.google.com/spreadsheets/d/1ZHAOHk8qMODoMFkKsFydaeJKRqu3jkZFhHhJYjNgMe8/edit#gid=0 > Support HDP 3.1.0 > - > > Key: METRON-2088 > URL: https://issues.apache.org/jira/browse/METRON-2088 > Project: Metron > Issue Type: New Feature >Reporter: Nick Allen >Assignee: Nick Allen >Priority: Major > > Metron currently supports HDP 2.6.5. We need to upgrade Metron to run against > the stack provided by HDP 3.1.0. > HDP Component Versions > * [HDP > 3.1.0|https://docs.hortonworks.com/HDPDocuments/HDP3/HDP-3.1.0/release-notes/content/comp_versions.html] > > * [HDP > 2.6.5|https://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.6.5/bk_release-notes/content/comp_versions.html] > * [HDP > 2.5.6|https://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.5.6/bk_release-notes/content/comp_versions.html] > See initial [discuss thread > here.|https://lists.apache.org/thread.html/37cc29648f0592cc39d3c78a0d07fce38521bdbbc4cf40e022a7a8ea@%3Cdev.metron.apache.org%3E] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] [metron] nickwallen commented on issue #1261: METRON-1860 new developer option for ansible in docker to deploy to vagrant
nickwallen commented on issue #1261: METRON-1860 new developer option for ansible in docker to deploy to vagrant URL: https://github.com/apache/metron/pull/1261#issuecomment-486280152 @ottobackwards Does this accurately describe the changes? You are effectively adding the blue "Docker 2" box?  This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [metron] ruffle1986 commented on issue #1373: METRON-2058: UI: Actions -> Add to Alert can still be selected from dropdown when no alerts are selected.
ruffle1986 commented on issue #1373: METRON-2058: UI: Actions -> Add to Alert can still be selected from dropdown when no alerts are selected. URL: https://github.com/apache/metron/pull/1373#issuecomment-486270408 @tiborm Good point. Renamed it from `e` to `event` This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Updated] (METRON-1893) Create a syslog 3164 parser
[ https://issues.apache.org/jira/browse/METRON-1893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otto Fowler updated METRON-1893: Fix Version/s: 0.7.1 > Create a syslog 3164 parser > --- > > Key: METRON-1893 > URL: https://issues.apache.org/jira/browse/METRON-1893 > Project: Metron > Issue Type: Sub-task >Reporter: Otto Fowler >Assignee: Otto Fowler >Priority: Major > Fix For: 0.7.1 > > Time Spent: 2h 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (METRON-1934) Stellar should built without error prone messages
[ https://issues.apache.org/jira/browse/METRON-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otto Fowler updated METRON-1934: Fix Version/s: 0.7.1 > Stellar should built without error prone messages > - > > Key: METRON-1934 > URL: https://issues.apache.org/jira/browse/METRON-1934 > Project: Metron > Issue Type: Improvement >Reporter: Otto Fowler >Assignee: Otto Fowler >Priority: Major > Fix For: 0.7.1 > > Time Spent: 0.5h > Remaining Estimate: 0h > > We should fix as many error prone messages as we can to build clean. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (METRON-1956) prepare-commit does not run all the tests it should
[ https://issues.apache.org/jira/browse/METRON-1956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otto Fowler updated METRON-1956: Fix Version/s: 0.7.1 > prepare-commit does not run all the tests it should > --- > > Key: METRON-1956 > URL: https://issues.apache.org/jira/browse/METRON-1956 > Project: Metron > Issue Type: Bug >Reporter: Otto Fowler >Assignee: Otto Fowler >Priority: Major > Fix For: 0.7.1 > > Time Spent: 3h 40m > Remaining Estimate: 0h > > prepare-commit currently does not: > * run the alert-ui end to end tests ( only the config ) > * build the rpms > It should do both -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (METRON-1963) Remove left over integration test from before refactoring
[ https://issues.apache.org/jira/browse/METRON-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otto Fowler updated METRON-1963: Fix Version/s: 1.7.1 > Remove left over integration test from before refactoring > - > > Key: METRON-1963 > URL: https://issues.apache.org/jira/browse/METRON-1963 > Project: Metron > Issue Type: Bug >Reporter: Otto Fowler >Assignee: Otto Fowler >Priority: Major > Fix For: 1.7.1 > > Time Spent: 40m > Remaining Estimate: 0h > > https://github.com/apache/metron/tree/master/metron-platform/metron-parsers -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (METRON-1963) Remove left over integration test from before refactoring
[ https://issues.apache.org/jira/browse/METRON-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otto Fowler updated METRON-1963: Fix Version/s: (was: 1.7.1) 0.7.0 > Remove left over integration test from before refactoring > - > > Key: METRON-1963 > URL: https://issues.apache.org/jira/browse/METRON-1963 > Project: Metron > Issue Type: Bug >Reporter: Otto Fowler >Assignee: Otto Fowler >Priority: Major > Fix For: 0.7.0 > > Time Spent: 40m > Remaining Estimate: 0h > > https://github.com/apache/metron/tree/master/metron-platform/metron-parsers -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (METRON-1957) 5424 and 3164 parser configurations are packaged in wrong place
[ https://issues.apache.org/jira/browse/METRON-1957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otto Fowler updated METRON-1957: Fix Version/s: 0.7.1 > 5424 and 3164 parser configurations are packaged in wrong place > --- > > Key: METRON-1957 > URL: https://issues.apache.org/jira/browse/METRON-1957 > Project: Metron > Issue Type: Bug >Reporter: Otto Fowler >Assignee: Otto Fowler >Priority: Major > Fix For: 0.7.1 > > Time Spent: 0.5h > Remaining Estimate: 0h > > they should be in -common -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] [metron] ottobackwards commented on issue #1261: METRON-1860 new developer option for ansible in docker to deploy to vagrant
ottobackwards commented on issue #1261: METRON-1860 new developer option for ansible in docker to deploy to vagrant URL: https://github.com/apache/metron/pull/1261#issuecomment-486226437 Like having a top level script, where you pick ubuntu or centos7 that just sets it all up instead having multiple top level areas This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [metron] ottobackwards commented on issue #1261: METRON-1860 new developer option for ansible in docker to deploy to vagrant
ottobackwards commented on issue #1261: METRON-1860 new developer option for ansible in docker to deploy to vagrant URL: https://github.com/apache/metron/pull/1261#issuecomment-486226032 @nickwallen , I took your statement to mean that only that role runs in or executes docker, when I'm running the entire ansible run in docker. If that is not what you meant, then we are just misunderstanding and are on the same page. Glad that you have ansible with centos7 working. So the question is: Since I'm going to refactor this to _replace_ the centos6, maybe in light of what we are going to do with centos7 there would be a different better way. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [metron] nickwallen commented on issue #1261: METRON-1860 new developer option for ansible in docker to deploy to vagrant
nickwallen commented on issue #1261: METRON-1860 new developer option for ansible in docker to deploy to vagrant URL: https://github.com/apache/metron/pull/1261#issuecomment-486214969 > no, that is not correct. Ansible + the build run in Docker. Which part of what I said is not correct? Can you elaborate? Sounds like you are saying is that Ansible + Docker is what is going to change, which is also my understanding. > My understanding from looking at centos 7 and full dev in the past was that it was not trivial wrt ansible changes. Is that no longer true? I already have a branch with Full Dev running on CentOS 7. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [metron] nickwallen edited a comment on issue #1261: METRON-1860 new developer option for ansible in docker to deploy to vagrant
nickwallen edited a comment on issue #1261: METRON-1860 new developer option for ansible in docker to deploy to vagrant URL: https://github.com/apache/metron/pull/1261#issuecomment-486214969 > no, that is not correct. Ansible + the build run in Docker. Which part of what I said is not correct? Can you elaborate? Sounds like you are saying that Ansible + Docker is what is going to change, which is also my understanding. > My understanding from looking at centos 7 and full dev in the past was that it was not trivial wrt ansible changes. Is that no longer true? I already have a branch with Full Dev running on CentOS 7. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Updated] (METRON-1371) Enhance Mpack for Ubuntu Deployments
[ https://issues.apache.org/jira/browse/METRON-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Allen updated METRON-1371: --- Fix Version/s: (was: 0.7.1) 0.5.0 > Enhance Mpack for Ubuntu Deployments > > > Key: METRON-1371 > URL: https://issues.apache.org/jira/browse/METRON-1371 > Project: Metron > Issue Type: Improvement >Reporter: Nick Allen >Assignee: Nick Allen >Priority: Major > Labels: Ubuntu > Fix For: 0.5.0 > > > The current Mpack supports installation on CentOS and RPM-based environments > only. We should enhance the Mpack so that users can deploy on Ubuntu also. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (METRON-1005) Create Decodable Row Key for Profiler
[ https://issues.apache.org/jira/browse/METRON-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Allen updated METRON-1005: --- Fix Version/s: (was: Next + 1) > Create Decodable Row Key for Profiler > - > > Key: METRON-1005 > URL: https://issues.apache.org/jira/browse/METRON-1005 > Project: Metron > Issue Type: Improvement >Affects Versions: 0.3.0 >Reporter: Nick Allen >Assignee: Nick Allen >Priority: Major > > To be able to answer the types of questions that I outlined in METRON-450, we > need a row key that is decodable. Right now there is no logic to decode a > row key, nor is the existing row key easily decodable. > Once the row keys can be decoded, you could scan all of the row keys in the > Profiler's HBase table, decode each of them and extract things like, the > names of all your profiles, the names of entities within a profile, the > period duration of a given profile. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (METRON-1005) Create Decodable Row Key for Profiler
[ https://issues.apache.org/jira/browse/METRON-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16825074#comment-16825074 ] Nick Allen commented on METRON-1005: [~justinleet] yes, you are correct. I will do that. > Create Decodable Row Key for Profiler > - > > Key: METRON-1005 > URL: https://issues.apache.org/jira/browse/METRON-1005 > Project: Metron > Issue Type: Improvement >Affects Versions: 0.3.0 >Reporter: Nick Allen >Assignee: Nick Allen >Priority: Major > Fix For: Next + 1 > > > To be able to answer the types of questions that I outlined in METRON-450, we > need a row key that is decodable. Right now there is no logic to decode a > row key, nor is the existing row key easily decodable. > Once the row keys can be decoded, you could scan all of the row keys in the > Profiler's HBase table, decode each of them and extract things like, the > names of all your profiles, the names of entities within a profile, the > period duration of a given profile. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] [metron] tiborm opened a new pull request #1390: METRON-2089: [UI] Adding loading state to Alerts details view
tiborm opened a new pull request #1390: METRON-2089: [UI] Adding loading state
to Alerts details view
URL: https://github.com/apache/metron/pull/1390
## Contributor Comments
Adding a loading state to Alerts UI solves the following issues:
#1
*When*
- clicking on a relatively large meta alert
*Expected*
- to show details on the opening pane (or a loading state)
*Actual*
- user sees a different guid while loading
- then when data arrives screen switching to the details of the actual meta
alert
#2 State retention problem
*When*
- click on an item
- close the Pane
- click on another item
*Expected*
- to see details of the item clicked second
*Actual*
- user sees the details of the previous alert till the details of the item
arrive
(in case of meta alerts, this means seconds)
As part of this changeset, I aligned the alert details pane's css to the
changes in the very similar table config pane. This alignment is just a small
but necessary part of the fix.
## Pull Request Checklist
Thank you for submitting a contribution to Apache Metron.
Please refer to our [Development
Guidelines](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61332235)
for the complete guide to follow for contributions.
Please refer also to our [Build Verification
Guidelines](https://cwiki.apache.org/confluence/display/METRON/Verifying+Builds?show-miniview)
for complete smoke testing guides.
In order to streamline the review of the contribution we ask you follow
these guidelines and ask you to double check the following:
### For all changes:
- [x] Is there a JIRA ticket associated with this PR? If not one needs to be
created at [Metron
Jira](https://issues.apache.org/jira/browse/METRON/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel).
- [x] Does your PR title start with METRON- where is the JIRA
number you are trying to resolve? Pay particular attention to the hyphen "-"
character.
- [x] Has your PR been rebased against the latest commit within the target
branch (typically master)?
### For code changes:
- [x] Have you included steps to reproduce the behavior or problem that is
being changed or addressed?
- [x] Have you included steps or a guide to how the change may be verified
and tested manually?
- [x] Have you ensured that the full suite of tests and checks have been
executed in the root metron folder via:
```
mvn -q clean integration-test install &&
dev-utilities/build-utils/verify_licenses.sh
```
- [x] Have you written or updated unit tests and or integration tests to
verify your changes?
- [x] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [x] Have you verified the basic functionality of the build by building and
running locally with Vagrant full-dev environment or the equivalent?
### For documentation related changes:
- [x] Have you ensured that format looks appropriate for the output in which
it is rendered by building and verifying the site-book? If not then run the
following commands and the verify changes via
`site-book/target/site/index.html`:
```
cd site-book
mvn site
```
Note:
Please ensure that once the PR is submitted, you check travis-ci for build
issues and submit an update to your PR as soon as possible.
It is also recommended that [travis-ci](https://travis-ci.org) is set up for
your personal repository such that your branches are built there before
submitting a pull request.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
[GitHub] [metron] tiborm commented on issue #1390: METRON-2089: [UI] Adding loading state to Alerts details view
tiborm commented on issue #1390: METRON-2089: [UI] Adding loading state to Alerts details view URL: https://github.com/apache/metron/pull/1390#issuecomment-486157404 Temporarily closing to restart Travis build. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [metron] tiborm closed pull request #1390: METRON-2089: [UI] Adding loading state to Alerts details view
tiborm closed pull request #1390: METRON-2089: [UI] Adding loading state to Alerts details view URL: https://github.com/apache/metron/pull/1390 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Updated] (METRON-2052) [UI] Changing default query time range to 15 minutes
[ https://issues.apache.org/jira/browse/METRON-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Meller updated METRON-2052: - Fix Version/s: 0.7.1 > [UI] Changing default query time range to 15 minutes > > > Key: METRON-2052 > URL: https://issues.apache.org/jira/browse/METRON-2052 > Project: Metron > Issue Type: Improvement >Reporter: Tibor Meller >Assignee: Tibor Meller >Priority: Major > Fix For: 0.7.1 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > To change default time range on Alert UI from "All time" to "Last 15 minutes" > was asked by metron users. In many cases querying all alerts without > narrowing time range causing performance issues in elastic and solr. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (METRON-2031) [UI] Turning off initial search request and polling by default on Alerts UI
[ https://issues.apache.org/jira/browse/METRON-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Meller updated METRON-2031: - Fix Version/s: 0.7.1 > [UI] Turning off initial search request and polling by default on Alerts UI > --- > > Key: METRON-2031 > URL: https://issues.apache.org/jira/browse/METRON-2031 > Project: Metron > Issue Type: Bug >Reporter: Tibor Meller >Assignee: Tibor Meller >Priority: Critical > Fix For: 0.7.1 > > Time Spent: 40m > Remaining Estimate: 0h > > The metron alert UI by default searches for everything, on login. > It also has a default refresh rate of 1 min. > This search is activated every time a user login to metron alerts UI. This is > causing a heavy load on elastic search and as a result, slows down the RA > indexing. > Furthermore, the 1-minute refresh rate sends another search request even > before the first search results are returned. > We have to wait for the first query to finish before changing the refresh > rate. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (METRON-1973) Upgrade Alert UI's webpack-dev-server to 3.1.14
[ https://issues.apache.org/jira/browse/METRON-1973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Meller updated METRON-1973: - Fix Version/s: 0.7.1 > Upgrade Alert UI's webpack-dev-server to 3.1.14 > --- > > Key: METRON-1973 > URL: https://issues.apache.org/jira/browse/METRON-1973 > Project: Metron > Issue Type: Improvement >Reporter: Tibor Meller >Assignee: Tibor Meller >Priority: Major > Fix For: 0.7.1 > > Time Spent: 40m > Remaining Estimate: 0h > > nallen@HW12402 : ~/tmp/metron-pr1322/metron-interface/metron-alerts > $ npm audit > === npm audit security report === > # Run npm update webpack-dev-server --depth 2 to resolve 1 vulnerability > ┌───┬──┐ > │ High │ Missing Origin Validation │ > ├───┼──┤ > │ Package │ webpack-dev-server │ > ├───┼──┤ > │ Dependency of │ @angular-devkit/build-angular [dev] │ > ├───┼──┤ > │ Path │ @angular-devkit/build-angular > webpack-dev-server │ > ├───┼──┤ > │ More info │ https://nodesecurity.io/advisories/725 │ > └───┴──┘ > found 1 high severity vulnerability in 24740 scanned packages > run `npm audit fix` to fix 1 of them. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (METRON-1999) Adding validation against special characters to parser name field
[ https://issues.apache.org/jira/browse/METRON-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Meller updated METRON-1999: - Fix Version/s: 0.7.1 > Adding validation against special characters to parser name field > - > > Key: METRON-1999 > URL: https://issues.apache.org/jira/browse/METRON-1999 > Project: Metron > Issue Type: Improvement >Reporter: Tibor Meller >Assignee: Tibor Meller >Priority: Major > Fix For: 0.7.1 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (METRON-1969) Adding Cypress documentation to Alert UI's README.md
[ https://issues.apache.org/jira/browse/METRON-1969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Meller updated METRON-1969: - Fix Version/s: 0.7.1 > Adding Cypress documentation to Alert UI's README.md > > > Key: METRON-1969 > URL: https://issues.apache.org/jira/browse/METRON-1969 > Project: Metron > Issue Type: Improvement >Reporter: Tibor Meller >Assignee: Tibor Meller >Priority: Major > Fix For: 0.7.1 > > Time Spent: 1h 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
