[GitHub] [metron] tiborm opened a new pull request #1353: METRON-2031 [UI] Turning off initial search request and polling by default on Alerts UI

2019-03-07 Thread GitBox
tiborm opened a new pull request #1353: METRON-2031 [UI] Turning off initial 
search request and polling by default on Alerts UI
URL: https://github.com/apache/metron/pull/1353
 
 
   ## Contributor Comments
   
   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.
   
   As part of this PR I fixing this issue by turning off polling by default 
(actually there was a previous atempt to turn it off but it had bug) and 
eliminating inital search request after login.
   
   Please review and merge if you find it ok!
   Thx
   
   ## 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:
   - [ ] 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).
   - [ ] Does your PR title start with METRON- where  is the JIRA 
number you are trying to resolve? Pay particular attention to the hyphen "-" 
character.
   - [ ] Has your PR been rebased against the latest commit within the target 
branch (typically master)?
   
   
   ### For code changes:
   - [ ] Have you included steps to reproduce the behavior or problem that is 
being changed or addressed?
   - [ ] Have you included steps or a guide to how the change may be verified 
and tested manually?
   - [ ] 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 
 ```
   
   - [ ] Have you written or updated unit tests and or integration tests to 
verify your changes?
   - [ ] 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)?
   - [ ] 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:
   - [ ] 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


[jira] [Created] (METRON-2031) [UI] Turning off initial search request and polling by default on Alerts UI

2019-03-07 Thread Tibor Meller (JIRA)
Tibor Meller created METRON-2031:


 Summary: [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


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)


[GitHub] [metron] merrimanr opened a new pull request #1352: METRON-2030: SensorParserGroupControllerIntegrationTest intermittent errors

2019-03-07 Thread GitBox
merrimanr opened a new pull request #1352: METRON-2030: 
SensorParserGroupControllerIntegrationTest intermittent errors
URL: https://github.com/apache/metron/pull/1352
 
 
   ## Contributor Comments
   This PR is intended to resolve the intermittent test errors seen in master 
recently.  Several `TestUtils.assertEventually` statements were added to ensure 
changes have been applied before tests are run.  Running the REST tests should 
no longer throw any errors.
   
   ## 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)?
   - [ ] 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:
   - [ ] 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


[jira] [Created] (METRON-2030) SensorParserGroupControllerIntegrationTest intermittent errors

2019-03-07 Thread Ryan Merriman (JIRA)
Ryan Merriman created METRON-2030:
-

 Summary: SensorParserGroupControllerIntegrationTest intermittent 
errors
 Key: METRON-2030
 URL: https://issues.apache.org/jira/browse/METRON-2030
 Project: Metron
  Issue Type: Bug
Reporter: Ryan Merriman


Recently I've seen some intermittent test failures in the recently added 
`SensorParserGroupControllerIntegrationTest`.  We likely need to add some 
assertEventually statements to ensure REST state is consistent before testing.



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


[jira] [Created] (METRON-2029) Configure Table should have filter

2019-03-07 Thread Shane Ardell (JIRA)
Shane Ardell created METRON-2029:


 Summary: Configure Table should have filter
 Key: METRON-2029
 URL: https://issues.apache.org/jira/browse/METRON-2029
 Project: Metron
  Issue Type: Improvement
Reporter: Shane Ardell


Currently, when a user opens the configure table panel, they must scroll down 
to see all their choices. This list can be really long, so it would be 
beneficial to have an input for a user to type into and have the options 
filtered.



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