[jira] [Created] (METRON-1530) Default proxy config settings in metron-contrib need to be updated
Shane Ardell created METRON-1530: Summary: Default proxy config settings in metron-contrib need to be updated Key: METRON-1530 URL: https://issues.apache.org/jira/browse/METRON-1530 Project: Metron Issue Type: Bug Reporter: Shane Ardell The current default target settings inside of metron-config's proxy.conf.json file result in Gateway Timeout errors in the browser. I was able to resolve this by matching the settings inside of metron-alerts' proxy file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-1532) Getting started documentation improvements
Shane Ardell created METRON-1532: Summary: Getting started documentation improvements Key: METRON-1532 URL: https://issues.apache.org/jira/browse/METRON-1532 Project: Metron Issue Type: Improvement Reporter: Shane Ardell After running through a fresh install of full dev on my local machine, I think the documentation could improve by including some essential credential information in the full dev README. The credentials exist elsewhere in the Metron documentation, but for someone spinning up full dev for the first time, it's important to have credentials for apps like the Metron UI and Ambari easy to find. I also think it's worth documenting how to make full dev more stable on your machine by turning off various services via Ambari. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (METRON-1605) Travis CI build fails when building Metron Alerts UI
[ https://issues.apache.org/jira/browse/METRON-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell updated METRON-1605: - Summary: Travis CI build fails when building Metron Alerts UI (was: Travis CI build fails when building Metron Alerts) > Travis CI build fails when building Metron Alerts UI > > > Key: METRON-1605 > URL: https://issues.apache.org/jira/browse/METRON-1605 > Project: Metron > Issue Type: Bug >Reporter: Shane Ardell >Priority: Major > > The work in [PR #1004|https://github.com/apache/metron/pull/1004/files] > currently has no conflicts with the master branch but fails whenever Travis > builds. The Travis logs can be seen > [here|https://travis-ci.org/apache/metron/builds/388356505?utm_source=github_status&utm_medium=notification]. > Travis fails at the script that builds the UI app, and [the error instructs > to update node and > npm|https://travis-ci.org/apache/metron/builds/388356505#L3874-L3906]. A > little further up in the logs, there is a [403 error when npm tries to > retrieve > node-zopfli|https://travis-ci.org/apache/metron/builds/388356505#L3305-L3306]. > I don't see anything specific to this pull request's Travis build that is > different from other pull requests, and I'm able to run the maven build > script from the docs locally without a problem. > I would think the first step in resolving this is to upgrade the version of > node and npm inside of the Travis build settings, but I'm basing this off of > the error message. Apparently, [the node-zopfli error is a long-time > issue|https://github.com/pierreinglebert/node-zopfli/issues/87], but the same > error occurs in other Travis builds that are able to build the UI app and > pass fine, so I'm unsure if it's actually related or not. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-1605) Travis CI build fails when building Metron Alerts
Shane Ardell created METRON-1605: Summary: Travis CI build fails when building Metron Alerts Key: METRON-1605 URL: https://issues.apache.org/jira/browse/METRON-1605 Project: Metron Issue Type: Bug Reporter: Shane Ardell The work in [PR #1004|https://github.com/apache/metron/pull/1004/files] currently has no conflicts with the master branch but fails whenever Travis builds. The Travis logs can be seen [here|https://travis-ci.org/apache/metron/builds/388356505?utm_source=github_status&utm_medium=notification]. Travis fails at the script that builds the UI app, and [the error instructs to update node and npm|https://travis-ci.org/apache/metron/builds/388356505#L3874-L3906]. A little further up in the logs, there is a [403 error when npm tries to retrieve node-zopfli|https://travis-ci.org/apache/metron/builds/388356505#L3305-L3306]. I don't see anything specific to this pull request's Travis build that is different from other pull requests, and I'm able to run the maven build script from the docs locally without a problem. I would think the first step in resolving this is to upgrade the version of node and npm inside of the Travis build settings, but I'm basing this off of the error message. Apparently, [the node-zopfli error is a long-time issue|https://github.com/pierreinglebert/node-zopfli/issues/87], but the same error occurs in other Travis builds that are able to build the UI app and pass fine, so I'm unsure if it's actually related or not. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (METRON-1605) Travis CI build fails when building Metron Alerts UI
[ https://issues.apache.org/jira/browse/METRON-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16518071#comment-16518071 ] Shane Ardell commented on METRON-1605: -- This turned out to be an issue caused by user error. I failed to build the app before submitting my latest changes to the PR. Note that the node-zopfli error will still show up in the Travis logs, but it won't cause the build to fail. > Travis CI build fails when building Metron Alerts UI > > > Key: METRON-1605 > URL: https://issues.apache.org/jira/browse/METRON-1605 > Project: Metron > Issue Type: Bug >Reporter: Shane Ardell >Priority: Major > > The work in [PR #1004|https://github.com/apache/metron/pull/1004/files] > currently has no conflicts with the master branch but fails whenever Travis > builds. The Travis logs can be seen > [here|https://travis-ci.org/apache/metron/builds/388356505?utm_source=github_status&utm_medium=notification]. > Travis fails at the script that builds the UI app, and [the error instructs > to update node and > npm|https://travis-ci.org/apache/metron/builds/388356505#L3874-L3906]. A > little further up in the logs, there is a [403 error when npm tries to > retrieve > node-zopfli|https://travis-ci.org/apache/metron/builds/388356505#L3305-L3306]. > I don't see anything specific to this pull request's Travis build that is > different from other pull requests, and I'm able to run the maven build > script from the docs locally without a problem. > I would think the first step in resolving this is to upgrade the version of > node and npm inside of the Travis build settings, but I'm basing this off of > the error message. Apparently, [the node-zopfli error is a long-time > issue|https://github.com/pierreinglebert/node-zopfli/issues/87], but the same > error occurs in other Travis builds that are able to build the UI app and > pass fine, so I'm unsure if it's actually related or not. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-1626) Alerts UI: An empty result is returned when searching for a single alert contained in a metaalert
Shane Ardell created METRON-1626: Summary: Alerts UI: An empty result is returned when searching for a single alert contained in a metaalert Key: METRON-1626 URL: https://issues.apache.org/jira/browse/METRON-1626 Project: Metron Issue Type: Bug Reporter: Shane Ardell Attachments: Screen Shot 2018-06-19 at 3.18.43 PM.png, Screen Shot 2018-06-19 at 3.19.09 PM.png When a user tries to searc for a single alert contained within a metaalert, an empty result set is returned from the API. Upon further inspection, it looks like this is because the query string is not updated to use metron_alert in place of alert. [This change happend in METRON-1601|https://github.com/apache/metron/pull/1049]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-1627) Alerts UI: Metaalert name and status missing in details panel when trying to add alert to existing metaalert
Shane Ardell created METRON-1627: Summary: Alerts UI: Metaalert name and status missing in details panel when trying to add alert to existing metaalert Key: METRON-1627 URL: https://issues.apache.org/jira/browse/METRON-1627 Project: Metron Issue Type: Bug Reporter: Shane Ardell Attachments: Screen Shot 2018-06-19 at 6.56.27 PM.png When a user tries to add an alert to an already existing metaalert, the details panel should show metaalerts to select from with details, including name and status. Currently, those details do not show. To reproduce, click on the checkbox on the right-hand side to select an alert, click on the 'Actions' button dropdown and select 'Add to Alert'. The details panel that opens should have details for all the metaalerts, but the info is missing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (METRON-1627) Alerts UI: Metaalert details missing in details panel when trying to add alert to existing metaalert
[ https://issues.apache.org/jira/browse/METRON-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell updated METRON-1627: - Description: When a user tries to add an alert to an already existing metaalert, the details panel should show metaalerts to select from with details. Currently, those details do not show. To reproduce, click on the checkbox on the right-hand side to select an alert, click on the 'Actions' button dropdown and select 'Add to Alert'. The details panel that opens should have details for all the metaalerts, but the info is missing. (was: When a user tries to add an alert to an already existing metaalert, the details panel should show metaalerts to select from with details, including name and status. Currently, those details do not show. To reproduce, click on the checkbox on the right-hand side to select an alert, click on the 'Actions' button dropdown and select 'Add to Alert'. The details panel that opens should have details for all the metaalerts, but the info is missing.) > Alerts UI: Metaalert details missing in details panel when trying to add > alert to existing metaalert > > > Key: METRON-1627 > URL: https://issues.apache.org/jira/browse/METRON-1627 > Project: Metron > Issue Type: Bug >Reporter: Shane Ardell >Priority: Major > Attachments: Screen Shot 2018-06-19 at 6.56.27 PM.png > > > When a user tries to add an alert to an already existing metaalert, the > details panel should show metaalerts to select from with details. Currently, > those details do not show. To reproduce, click on the checkbox on the > right-hand side to select an alert, click on the 'Actions' button dropdown > and select 'Add to Alert'. The details panel that opens should have details > for all the metaalerts, but the info is missing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (METRON-1627) Alerts UI: Metaalert details missing in details panel when trying to add alert to existing metaalert
[ https://issues.apache.org/jira/browse/METRON-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell updated METRON-1627: - Summary: Alerts UI: Metaalert details missing in details panel when trying to add alert to existing metaalert (was: Alerts UI: Metaalert name and status missing in details panel when trying to add alert to existing metaalert) > Alerts UI: Metaalert details missing in details panel when trying to add > alert to existing metaalert > > > Key: METRON-1627 > URL: https://issues.apache.org/jira/browse/METRON-1627 > Project: Metron > Issue Type: Bug >Reporter: Shane Ardell >Priority: Major > Attachments: Screen Shot 2018-06-19 at 6.56.27 PM.png > > > When a user tries to add an alert to an already existing metaalert, the > details panel should show metaalerts to select from with details, including > name and status. Currently, those details do not show. To reproduce, click on > the checkbox on the right-hand side to select an alert, click on the > 'Actions' button dropdown and select 'Add to Alert'. The details panel that > opens should have details for all the metaalerts, but the info is missing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-1631) Alerts UI: Dash score does not show if only filtering by one group
Shane Ardell created METRON-1631: Summary: Alerts UI: Dash score does not show if only filtering by one group Key: METRON-1631 URL: https://issues.apache.org/jira/browse/METRON-1631 Project: Metron Issue Type: Bug Reporter: Shane Ardell Attachments: Screen Shot 2018-06-21 at 2.44.28 PM.png, Screen Shot 2018-06-21 at 2.44.34 PM.png When a user clicks on a single Group By button, the dash score doesn't display. If a user then clicks on another Group By button, the dash score will then display. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-1648) Use Cypress instead of Protractor to run e2e tests
Shane Ardell created METRON-1648: Summary: Use Cypress instead of Protractor to run e2e tests Key: METRON-1648 URL: https://issues.apache.org/jira/browse/METRON-1648 Project: Metron Issue Type: Bug Reporter: Shane Ardell There are a handful of major advantages we will gain if we switch from Protractor to Cypress: * As with most Selenium-based e2e testing frameworks, Protractor suffers from test flakiness. This is because Selenium runs outside of the browser and executes remote commands across the network. To work around this at the moment, we are using protractor-flake to re-run failed tests, but this is more of a crutch than a fix to Metron's flaky tests. Cypress executes in the same run loop as the application it's testing and does not suffer from the same flakiness. * In addition to being less flaky, Cypress runs much faster than Protractor. * Protractor is incredibly hard to debug. In contrast, Cypress can easily be debugged in the browser, has readable stack traces, has the ability to time travel, etc. * We are currently unable to integrate Protractor e2e tests into Travis. With Cypress, [it's possible to add these tests to our CI|https://docs.cypress.io/guides/guides/continuous-integration.html#Example-travis-yml-config-file]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-1683) Fix the download progress bar in the PCAP UI
Shane Ardell created METRON-1683: Summary: Fix the download progress bar in the PCAP UI Key: METRON-1683 URL: https://issues.apache.org/jira/browse/METRON-1683 Project: Metron Issue Type: Sub-task Reporter: Shane Ardell The download progress bar currently does not appear when a PCAP search is submitted. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (METRON-1683) PCAP UI: Fix the download progress bar
[ https://issues.apache.org/jira/browse/METRON-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell updated METRON-1683: - Summary: PCAP UI: Fix the download progress bar (was: Fix the download progress bar in the PCAP UI) > PCAP UI: Fix the download progress bar > -- > > Key: METRON-1683 > URL: https://issues.apache.org/jira/browse/METRON-1683 > Project: Metron > Issue Type: Sub-task >Reporter: Shane Ardell >Priority: Major > > The download progress bar currently does not appear when a PCAP search is > submitted. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (METRON-1683) PCAP UI - Fix the download progress bar
[ https://issues.apache.org/jira/browse/METRON-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell updated METRON-1683: - Summary: PCAP UI - Fix the download progress bar (was: PCAP UI: Fix the download progress bar) > PCAP UI - Fix the download progress bar > --- > > Key: METRON-1683 > URL: https://issues.apache.org/jira/browse/METRON-1683 > Project: Metron > Issue Type: Sub-task >Reporter: Shane Ardell >Priority: Major > > The download progress bar currently does not appear when a PCAP search is > submitted. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-1698) PCAP UI - Timestamp field contains both the epoch timestamp and the date
Shane Ardell created METRON-1698: Summary: PCAP UI - Timestamp field contains both the epoch timestamp and the date Key: METRON-1698 URL: https://issues.apache.org/jira/browse/METRON-1698 Project: Metron Issue Type: Improvement Reporter: Shane Ardell As pointed out in the initial PCAP UI work, [the timestamp field in the pcap results contains both the epoch timestamp and the date |https://github.com/apache/metron/pull/1103]. It seems like we either need to separate these values into two separate fields or choose one to display. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-1712) PCAP UI - Input validation
Shane Ardell created METRON-1712: Summary: PCAP UI - Input validation Key: METRON-1712 URL: https://issues.apache.org/jira/browse/METRON-1712 Project: Metron Issue Type: Sub-task Reporter: Shane Ardell The PCAP panel currently has input validation on the date, ip address and port number fields. What validation requirements are left for the remaining fields? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-1713) PCAP UI - Add a way to kill a pcap job
Shane Ardell created METRON-1713: Summary: PCAP UI - Add a way to kill a pcap job Key: METRON-1713 URL: https://issues.apache.org/jira/browse/METRON-1713 Project: Metron Issue Type: Sub-task Reporter: Shane Ardell Attachments: Screen Shot 2018-08-01 at 4.04.58 PM.png It looks like there is an endpoint to kill a running pcap query job, but we don't have a way in the UI to do so. Can we add a button to kill a running job to the UI? Attached image is from Swagger after building full-dev from the feature branch from METRON-1554. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-1718) Add tests to handle different input parameter values
Shane Ardell created METRON-1718: Summary: Add tests to handle different input parameter values Key: METRON-1718 URL: https://issues.apache.org/jira/browse/METRON-1718 Project: Metron Issue Type: Sub-task Reporter: Shane Ardell The parameters of a pcap request differ if you've never entered a field vs. entered then deleted it. For example, for ports (and possibly just the two port fields), it'll be empty string if never entered and null if entered then deleted. We should have tests to ensure being provided either works as expected. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (METRON-1648) Use Cypress instead of Protractor to run e2e tests
[ https://issues.apache.org/jira/browse/METRON-1648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell updated METRON-1648: - Issue Type: Improvement (was: Bug) > Use Cypress instead of Protractor to run e2e tests > -- > > Key: METRON-1648 > URL: https://issues.apache.org/jira/browse/METRON-1648 > Project: Metron > Issue Type: Improvement >Reporter: Shane Ardell >Priority: Major > > There are a handful of major advantages we will gain if we switch from > Protractor to Cypress: > * As with most Selenium-based e2e testing frameworks, Protractor suffers from > test flakiness. This is because Selenium runs outside of the browser and > executes remote commands across the network. To work around this at the > moment, we are using protractor-flake to re-run failed tests, but this is > more of a crutch than a fix to Metron's flaky tests. Cypress executes in the > same run loop as the application it's testing and does not suffer from the > same flakiness. > * In addition to being less flaky, Cypress runs much faster than Protractor. > * Protractor is incredibly hard to debug. In contrast, Cypress can easily be > debugged in the browser, has readable stack traces, has the ability to time > travel, etc. > * We are currently unable to integrate Protractor e2e tests into Travis. With > Cypress, [it's possible to add these tests to our > CI|https://docs.cypress.io/guides/guides/continuous-integration.html#Example-travis-yml-config-file]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-1723) PCAP UI - Unable to select/copy from packets details in PCAP query panel
Shane Ardell created METRON-1723: Summary: PCAP UI - Unable to select/copy from packets details in PCAP query panel Key: METRON-1723 URL: https://issues.apache.org/jira/browse/METRON-1723 Project: Metron Issue Type: Sub-task Reporter: Shane Ardell Attachments: expand-collapse-details-PCAP-query.mp4 Upon query completion, a user can click on a row and drill down (up to 2 levels) for a given packet. A SOC analyst might find it useful to select/copy specific information from the 2nd level granular details (E.g. MAC address, IP address, timestamps etc.) to be used subsequently for analysis/investigation. Currently, selecting or clicking on nested content fires an event that expands/collapses the information. See the attached video to view the behavior. It would be better if target for the collapse/expand event only applied to the top of the details section. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (METRON-1712) PCAP UI - Input validation
[ https://issues.apache.org/jira/browse/METRON-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell updated METRON-1712: - Description: The following fields need input validation: IP Source Address: should accept valid IPv4 address formats (v6 is not yet supported) IP Source Port: should accept integers from 0 to 65535 IP Source Address: should accept valid IPv4 address formats (v6 is not yet supported) IP Dest Port: should accept integers from 0 to 65535 Leave unvalidated: Protocol: number of valid protocols is around 150 and it could change in the future, validation possible makes more sense on the backend or by a separated endpoint Free text filtering: binary regular expression Broken inputs should be recognized by the UI and not submitted, with user-facing feedback. The REST API should also fail on queries outside reasonable parameters. was:The PCAP panel currently has input validation on the date, ip address and port number fields. What validation requirements are left for the remaining fields? > PCAP UI - Input validation > -- > > Key: METRON-1712 > URL: https://issues.apache.org/jira/browse/METRON-1712 > Project: Metron > Issue Type: Sub-task >Reporter: Shane Ardell >Priority: Major > > The following fields need input validation: > IP Source Address: should accept valid IPv4 address formats (v6 is not yet > supported) > IP Source Port: should accept integers from 0 to 65535 > IP Source Address: should accept valid IPv4 address formats (v6 is not yet > supported) > IP Dest Port: should accept integers from 0 to 65535 > Leave unvalidated: > Protocol: number of valid protocols is around 150 and it could change in the > future, validation possible makes more sense on the backend or by a separated > endpoint > Free text filtering: binary regular expression > Broken inputs should be recognized by the UI and not submitted, with > user-facing feedback. The REST API should also fail on queries outside > reasonable parameters. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (METRON-1713) PCAP UI - Add a way to kill a pcap job
[ https://issues.apache.org/jira/browse/METRON-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell updated METRON-1713: - Description: As a user, I would like to be able to cancel my ongoing PCAP query request. In order to do that, I would like to see a cancel button beside the progress bar of the query. An endpoint for this already exists in REST. Attached image is from Swagger after building full-dev from the feature branch from [METRON-1554|https://issues.apache.org/jira/browse/METRON-1554]. was: It looks like there is an endpoint to kill a running pcap query job, but we don't have a way in the UI to do so. Can we add a button to kill a running job to the UI? Attached image is from Swagger after building full-dev from the feature branch from METRON-1554. > PCAP UI - Add a way to kill a pcap job > -- > > Key: METRON-1713 > URL: https://issues.apache.org/jira/browse/METRON-1713 > Project: Metron > Issue Type: Sub-task >Reporter: Shane Ardell >Priority: Major > Attachments: Screen Shot 2018-08-01 at 4.04.58 PM.png > > > As a user, I would like to be able to cancel my ongoing PCAP query request. > In order to do that, I would like to see a cancel button beside the progress > bar of the query. > An endpoint for this already exists in REST. > Attached image is from Swagger after building full-dev from the feature > branch from [METRON-1554|https://issues.apache.org/jira/browse/METRON-1554]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (METRON-1683) PCAP UI - Fix the download progress bar
[ https://issues.apache.org/jira/browse/METRON-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-1683: Assignee: Shane Ardell > PCAP UI - Fix the download progress bar > --- > > Key: METRON-1683 > URL: https://issues.apache.org/jira/browse/METRON-1683 > Project: Metron > Issue Type: Sub-task >Reporter: Shane Ardell >Assignee: Shane Ardell >Priority: Major > > The download progress bar currently does not appear when a PCAP search is > submitted. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (METRON-1675) PCAP UI - Introduce the paging capability
[ https://issues.apache.org/jira/browse/METRON-1675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-1675: Assignee: Shane Ardell > PCAP UI - Introduce the paging capability > - > > Key: METRON-1675 > URL: https://issues.apache.org/jira/browse/METRON-1675 > Project: Metron > Issue Type: Sub-task >Reporter: Tibor Meller >Assignee: Shane Ardell >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (METRON-1723) PCAP UI - Unable to select/copy from packets details in PCAP query panel
[ https://issues.apache.org/jira/browse/METRON-1723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-1723: Assignee: Shane Ardell > PCAP UI - Unable to select/copy from packets details in PCAP query panel > > > Key: METRON-1723 > URL: https://issues.apache.org/jira/browse/METRON-1723 > Project: Metron > Issue Type: Sub-task >Reporter: Shane Ardell >Assignee: Shane Ardell >Priority: Major > Attachments: expand-collapse-details-PCAP-query.mp4 > > > Upon query completion, a user can click on a row and drill down (up to 2 > levels) for a given packet. > A SOC analyst might find it useful to select/copy specific information from > the 2nd level granular details (E.g. MAC address, IP address, timestamps > etc.) to be used subsequently for analysis/investigation. > Currently, selecting or clicking on nested content fires an event that > expands/collapses the information. See the attached video to view the > behavior. > It would be better if target for the collapse/expand event only applied to > the top of the details section. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (METRON-1662) PCAP UI - Downloading PCAP page files
[ https://issues.apache.org/jira/browse/METRON-1662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-1662: Assignee: Tibor Meller (was: Shane Ardell) > PCAP UI - Downloading PCAP page files > - > > Key: METRON-1662 > URL: https://issues.apache.org/jira/browse/METRON-1662 > Project: Metron > Issue Type: Sub-task >Reporter: Tibor Meller >Assignee: Tibor Meller >Priority: Major > > As a user, I like to be able to download the filtered PCAP query output in > PCAP binary format. > As a user, when I click the download button below the result grid, I like to > get the result page selected by the paginator component. > > *Acceptance criteria* > Given > * the user is logged in > * and navigated to the PCAP panel > * submitted a PCAP query > * the valid result appeared on the UI > When > * the user clicking the download button below the result grid > Then > * the selected page of the result should download in PCAP binary format -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (METRON-1662) PCAP UI - Downloading PCAP page files
[ https://issues.apache.org/jira/browse/METRON-1662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-1662: Assignee: Shane Ardell > PCAP UI - Downloading PCAP page files > - > > Key: METRON-1662 > URL: https://issues.apache.org/jira/browse/METRON-1662 > Project: Metron > Issue Type: Sub-task >Reporter: Tibor Meller >Assignee: Shane Ardell >Priority: Major > > As a user, I like to be able to download the filtered PCAP query output in > PCAP binary format. > As a user, when I click the download button below the result grid, I like to > get the result page selected by the paginator component. > > *Acceptance criteria* > Given > * the user is logged in > * and navigated to the PCAP panel > * submitted a PCAP query > * the valid result appeared on the UI > When > * the user clicking the download button below the result grid > Then > * the selected page of the result should download in PCAP binary format -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (METRON-1676) PCAP UI - Add data range selector to the filter bar
[ https://issues.apache.org/jira/browse/METRON-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-1676: Assignee: Shane Ardell > PCAP UI - Add data range selector to the filter bar > --- > > Key: METRON-1676 > URL: https://issues.apache.org/jira/browse/METRON-1676 > Project: Metron > Issue Type: Sub-task >Reporter: Tibor Meller >Assignee: Shane Ardell >Priority: Major > > As a user, I like to set a date range for my PCAP query request. > * Strat time (From) and end time (To) selectors should appear as the first > two elements of the filter bar > * Time selectors should have default values (end time: now, start time: now > - 5 days) > * Due to these fields are mandatory, the user should not be able to set time > selectors to an invalid state (eg. missing value, null value or any value > other than time) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (METRON-1676) PCAP UI - Add data range selector to the filter bar
[ https://issues.apache.org/jira/browse/METRON-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-1676: Assignee: Tibor Meller (was: Shane Ardell) > PCAP UI - Add data range selector to the filter bar > --- > > Key: METRON-1676 > URL: https://issues.apache.org/jira/browse/METRON-1676 > Project: Metron > Issue Type: Sub-task >Reporter: Tibor Meller >Assignee: Tibor Meller >Priority: Major > > As a user, I like to set a date range for my PCAP query request. > * Strat time (From) and end time (To) selectors should appear as the first > two elements of the filter bar > * Time selectors should have default values (end time: now, start time: now > - 5 days) > * Due to these fields are mandatory, the user should not be able to set time > selectors to an invalid state (eg. missing value, null value or any value > other than time) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (METRON-1713) PCAP UI - Add a way to kill a pcap job
[ https://issues.apache.org/jira/browse/METRON-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-1713: Assignee: Shane Ardell > PCAP UI - Add a way to kill a pcap job > -- > > Key: METRON-1713 > URL: https://issues.apache.org/jira/browse/METRON-1713 > Project: Metron > Issue Type: Sub-task >Reporter: Shane Ardell >Assignee: Shane Ardell >Priority: Major > Attachments: Screen Shot 2018-08-01 at 4.04.58 PM.png > > > As a user, I would like to be able to cancel my ongoing PCAP query request. > In order to do that, I would like to see a cancel button beside the progress > bar of the query. > An endpoint for this already exists in REST. > Attached image is from Swagger after building full-dev from the feature > branch from [METRON-1554|https://issues.apache.org/jira/browse/METRON-1554]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (METRON-1713) PCAP UI - Add a way to kill a pcap job
[ https://issues.apache.org/jira/browse/METRON-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-1713: Assignee: Tibor Meller (was: Shane Ardell) > PCAP UI - Add a way to kill a pcap job > -- > > Key: METRON-1713 > URL: https://issues.apache.org/jira/browse/METRON-1713 > Project: Metron > Issue Type: Sub-task >Reporter: Shane Ardell >Assignee: Tibor Meller >Priority: Major > Attachments: Screen Shot 2018-08-01 at 4.04.58 PM.png > > > As a user, I would like to be able to cancel my ongoing PCAP query request. > In order to do that, I would like to see a cancel button beside the progress > bar of the query. > An endpoint for this already exists in REST. > Attached image is from Swagger after building full-dev from the feature > branch from [METRON-1554|https://issues.apache.org/jira/browse/METRON-1554]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (METRON-1713) PCAP UI - Add a way to kill a pcap job
[ https://issues.apache.org/jira/browse/METRON-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-1713: Assignee: Tibor Meller (was: Shane Ardell) > PCAP UI - Add a way to kill a pcap job > -- > > Key: METRON-1713 > URL: https://issues.apache.org/jira/browse/METRON-1713 > Project: Metron > Issue Type: Sub-task >Reporter: Shane Ardell >Assignee: Tibor Meller >Priority: Major > Attachments: Screen Shot 2018-08-01 at 4.04.58 PM.png > > > As a user, I would like to be able to cancel my ongoing PCAP query request. > In order to do that, I would like to see a cancel button beside the progress > bar of the query. > An endpoint for this already exists in REST. > Attached image is from Swagger after building full-dev from the feature > branch from [METRON-1554|https://issues.apache.org/jira/browse/METRON-1554]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (METRON-1713) PCAP UI - Add a way to kill a pcap job
[ https://issues.apache.org/jira/browse/METRON-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-1713: Assignee: Shane Ardell (was: Tibor Meller) > PCAP UI - Add a way to kill a pcap job > -- > > Key: METRON-1713 > URL: https://issues.apache.org/jira/browse/METRON-1713 > Project: Metron > Issue Type: Sub-task >Reporter: Shane Ardell >Assignee: Shane Ardell >Priority: Major > Attachments: Screen Shot 2018-08-01 at 4.04.58 PM.png > > > As a user, I would like to be able to cancel my ongoing PCAP query request. > In order to do that, I would like to see a cancel button beside the progress > bar of the query. > An endpoint for this already exists in REST. > Attached image is from Swagger after building full-dev from the feature > branch from [METRON-1554|https://issues.apache.org/jira/browse/METRON-1554]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-1733) PCAP UI - PCAP queries don't work on Safari
Shane Ardell created METRON-1733: Summary: PCAP UI - PCAP queries don't work on Safari Key: METRON-1733 URL: https://issues.apache.org/jira/browse/METRON-1733 Project: Metron Issue Type: Sub-task Reporter: Shane Ardell On Safari, PCAP queries fail with a 500 internal server error. No issues seen with Chrome or Firefox. After digging into the search request, it looks like the values for the startTime and endTime are 'NaN'. It looks like Safari cannot parse the format of the time we are passing to the getDate() funciton. For more on this issue: https://stackoverflow.com/questions/21883699/safari-javascript-date-nan-issue--mm-dd-hhmmss -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (METRON-1733) PCAP UI - PCAP queries don't work on Safari
[ https://issues.apache.org/jira/browse/METRON-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-1733: Assignee: Shane Ardell > PCAP UI - PCAP queries don't work on Safari > --- > > Key: METRON-1733 > URL: https://issues.apache.org/jira/browse/METRON-1733 > Project: Metron > Issue Type: Sub-task >Reporter: Shane Ardell >Assignee: Shane Ardell >Priority: Major > > On Safari, PCAP queries fail with a 500 internal server error. No issues seen > with Chrome or Firefox. After digging into the search request, it looks like > the values for the startTime and endTime are 'NaN'. It looks like Safari > cannot parse the format of the time we are passing to the getDate() funciton. > For more on this issue: > https://stackoverflow.com/questions/21883699/safari-javascript-date-nan-issue--mm-dd-hhmmss -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-1749) Update Angular in Management UI
Shane Ardell created METRON-1749: Summary: Update Angular in Management UI Key: METRON-1749 URL: https://issues.apache.org/jira/browse/METRON-1749 Project: Metron Issue Type: Improvement Reporter: Shane Ardell Currently, the Management UI is on Angular v2. Not only as there been many updates and improvements to Angular, that release is no longer supported by the Angular team. This means critical fixes and security patches are no longer being done. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-1752) Prevent package.lock from changing during build
Shane Ardell created METRON-1752: Summary: Prevent package.lock from changing during build Key: METRON-1752 URL: https://issues.apache.org/jira/browse/METRON-1752 Project: Metron Issue Type: Bug Reporter: Shane Ardell As referenced in this mail list discussion, the package-lock.json file in metron-alerts updates whenever we run a maven build: https://lists.apache.org/thread.html/d0da3647f2955b4257c3eb0d89235779aed64a58097b416a18de6cd9@%3Cdev.metron.apache.org%3E The fix for this was originally included in [PR #1096, which upgrades the Angular version used in the alerts ui|https://github.com/apache/metron/pull/1096], but as mentioned in the comments, it would be best to fix this bug in a separate issue in order to simplify its inclusion in the next release. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-1763) Some Management UI endpoints returning 404
Shane Ardell created METRON-1763: Summary: Some Management UI endpoints returning 404 Key: METRON-1763 URL: https://issues.apache.org/jira/browse/METRON-1763 Project: Metron Issue Type: Bug Reporter: Shane Ardell Attachments: Screen Shot 2018-09-03 at 2.16.47 PM.png While testing on full-dev, I've noticed many 404 errors in the browser console when I click to open the details panel for different parsers in the management UI. Is this by design, or are these endpoints broken? I tested these endpoints in swagger and had the same results. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (METRON-1767) Unsubscribe from every observable in the pcap panel UI component
[
https://issues.apache.org/jira/browse/METRON-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16604216#comment-16604216
]
Shane Ardell commented on METRON-1767:
--
I agree that we should always unsubscribe from Observables when destroying
components to prevent memory leaks. However, what is the advantage to using an
observable instead of a promise for a single event like getPackets?
> Unsubscribe from every observable in the pcap panel UI component
>
>
> Key: METRON-1767
> URL: https://issues.apache.org/jira/browse/METRON-1767
> Project: Metron
> Issue Type: Improvement
>Reporter: Tamas Fodor
>Assignee: Tamas Fodor
>Priority: Major
>
> There are a lot of http requests performed in the pcap panel ui component and
> we just unsubscribe from some of them when the component is no longer
> rendered on the screen. It could cause memory consumption issues. Because of
> the active subscriptions, the garbage collector is not able to remove these
> objects from the memory, however they're not needed to be there anymore.
> There's another benefit of unsubscribing from these http calls. If the user
> leaves the pcap tab but there are pending requests, the unsubscribe method
> cancels the active xhrs immediately so it won't wait for fulfilment
> unnecessarily.
> [https://github.com/apache/metron/blob/master/metron-interface/metron-alerts/src/app/pcap/pcap-panel/pcap-panel.component.ts#L54]
> I would also refactor that part when we convert an observable to a promise. I
> would keep it as an observable. By doing this, we would be able to
> unsubscribe from it as well in the destructor method. Promises are not
> cancelable.
> [https://github.com/apache/metron/blob/master/metron-interface/metron-alerts/src/app/pcap/pcap-panel/pcap-panel.component.ts#L70]
>
> Resources:
> [https://angular.io/guide/lifecycle-hooks#ondestroy]
> {quote}This is the place to free resources that won't be garbage collected
> automatically. Unsubscribe from Observables and DOM events. Stop interval
> timers. Unregister all callbacks that this directive registered with global
> or application services. You risk memory leaks if you neglect to do so.
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (METRON-1648) Use Cypress instead of Protractor to run e2e tests
[ https://issues.apache.org/jira/browse/METRON-1648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell updated METRON-1648: - Description: There are a handful of major advantages we will gain if we switch from Protractor to Cypress: * As with most Selenium-based e2e testing frameworks, Protractor suffers from test flakiness. This is because Selenium runs outside of the browser and executes remote commands across the network. To work around this at the moment, we are using protractor-flake to re-run failed tests, but this is more of a crutch than a fix to Metron's flaky tests. Cypress executes in the same run loop as the application it's testing and does not suffer from the same flakiness. * In addition to being less flaky, Cypress runs much faster than Protractor. This is especially critical if e2e tests are added to the CI build in the future. * Protractor is incredibly hard to debug. In contrast, Cypress can easily be debugged in the browser, has readable stack traces, has the ability to time travel, etc. was: There are a handful of major advantages we will gain if we switch from Protractor to Cypress: * As with most Selenium-based e2e testing frameworks, Protractor suffers from test flakiness. This is because Selenium runs outside of the browser and executes remote commands across the network. To work around this at the moment, we are using protractor-flake to re-run failed tests, but this is more of a crutch than a fix to Metron's flaky tests. Cypress executes in the same run loop as the application it's testing and does not suffer from the same flakiness. * In addition to being less flaky, Cypress runs much faster than Protractor. * Protractor is incredibly hard to debug. In contrast, Cypress can easily be debugged in the browser, has readable stack traces, has the ability to time travel, etc. * We are currently unable to integrate Protractor e2e tests into Travis. With Cypress, [it's possible to add these tests to our CI|https://docs.cypress.io/guides/guides/continuous-integration.html#Example-travis-yml-config-file]. > Use Cypress instead of Protractor to run e2e tests > -- > > Key: METRON-1648 > URL: https://issues.apache.org/jira/browse/METRON-1648 > Project: Metron > Issue Type: Improvement >Reporter: Shane Ardell >Priority: Major > > There are a handful of major advantages we will gain if we switch from > Protractor to Cypress: > * As with most Selenium-based e2e testing frameworks, Protractor suffers from > test flakiness. This is because Selenium runs outside of the browser and > executes remote commands across the network. To work around this at the > moment, we are using protractor-flake to re-run failed tests, but this is > more of a crutch than a fix to Metron's flaky tests. Cypress executes in the > same run loop as the application it's testing and does not suffer from the > same flakiness. > * In addition to being less flaky, Cypress runs much faster than Protractor. > This is especially critical if e2e tests are added to the CI build in the > future. > * Protractor is incredibly hard to debug. In contrast, Cypress can easily be > debugged in the browser, has readable stack traces, has the ability to time > travel, etc. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (METRON-1648) Use Cypress instead of Protractor to run e2e tests
[ https://issues.apache.org/jira/browse/METRON-1648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell updated METRON-1648: - Description: There are a handful of major advantages we will gain if we switch from Protractor to Cypress: * As with most Selenium-based e2e testing frameworks, Protractor suffers from test flakiness. This is because Selenium runs outside of the browser and executes remote commands across the network. To work around this at the moment, we are using protractor-flake to re-run failed tests, but this is more of a crutch than a fix. Cypress executes in the same run loop as the application it's testing, and as a result does not suffer from the same flakiness. * Cypress runs much faster than Protractor. This is especially critical if e2e tests are added to the CI build in the future. * Protractor is incredibly hard to debug. In contrast, Cypress comes with a plethora of debugging features, some of which you can see here: https://vimeo.com/242961930#t=264s was: There are a handful of major advantages we will gain if we switch from Protractor to Cypress: * As with most Selenium-based e2e testing frameworks, Protractor suffers from test flakiness. This is because Selenium runs outside of the browser and executes remote commands across the network. To work around this at the moment, we are using protractor-flake to re-run failed tests, but this is more of a crutch than a fix to Metron's flaky tests. Cypress executes in the same run loop as the application it's testing and does not suffer from the same flakiness. * In addition to being less flaky, Cypress runs much faster than Protractor. This is especially critical if e2e tests are added to the CI build in the future. * Protractor is incredibly hard to debug. In contrast, Cypress can easily be debugged in the browser, has readable stack traces, has the ability to time travel, etc. > Use Cypress instead of Protractor to run e2e tests > -- > > Key: METRON-1648 > URL: https://issues.apache.org/jira/browse/METRON-1648 > Project: Metron > Issue Type: Improvement >Reporter: Shane Ardell >Priority: Major > > There are a handful of major advantages we will gain if we switch from > Protractor to Cypress: > * As with most Selenium-based e2e testing frameworks, Protractor suffers from > test flakiness. This is because Selenium runs outside of the browser and > executes remote commands across the network. To work around this at the > moment, we are using protractor-flake to re-run failed tests, but this is > more of a crutch than a fix. Cypress executes in the same run loop as the > application it's testing, and as a result does not suffer from the same > flakiness. > * Cypress runs much faster than Protractor. This is especially critical if > e2e tests are added to the CI build in the future. > * Protractor is incredibly hard to debug. In contrast, Cypress comes with a > plethora of debugging features, some of which you can see here: > https://vimeo.com/242961930#t=264s -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (METRON-1749) Update Angular to latest release in Management UI
[ https://issues.apache.org/jira/browse/METRON-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell updated METRON-1749: - Summary: Update Angular to latest release in Management UI (was: Update Angular in Management UI) > Update Angular to latest release in Management UI > - > > Key: METRON-1749 > URL: https://issues.apache.org/jira/browse/METRON-1749 > Project: Metron > Issue Type: Improvement >Reporter: Shane Ardell >Priority: Major > > Currently, the Management UI is on Angular v2. Not only as there been many > updates and improvements to Angular, that release is no longer supported by > the Angular team. This means critical fixes and security patches are no > longer being done. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (METRON-1749) Update Angular to latest release in Management UI
[ https://issues.apache.org/jira/browse/METRON-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell updated METRON-1749: - Description: Currently, the Management UI is on Angular v2. Not only has there been many updates and improvements to Angular, that release is no longer supported by the Angular team. This means critical fixes and security patches are no longer being done. (was: Currently, the Management UI is on Angular v2. Not only as there been many updates and improvements to Angular, that release is no longer supported by the Angular team. This means critical fixes and security patches are no longer being done.) > Update Angular to latest release in Management UI > - > > Key: METRON-1749 > URL: https://issues.apache.org/jira/browse/METRON-1749 > Project: Metron > Issue Type: Improvement >Reporter: Shane Ardell >Priority: Major > > Currently, the Management UI is on Angular v2. Not only has there been many > updates and improvements to Angular, that release is no longer supported by > the Angular team. This means critical fixes and security patches are no > longer being done. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (METRON-1763) Some Management UI endpoints returning 404
[ https://issues.apache.org/jira/browse/METRON-1763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16633919#comment-16633919 ] Shane Ardell commented on METRON-1763: -- This turned out to be expected behavior since the endpoints had to data available in full dev. > Some Management UI endpoints returning 404 > -- > > Key: METRON-1763 > URL: https://issues.apache.org/jira/browse/METRON-1763 > Project: Metron > Issue Type: Bug >Reporter: Shane Ardell >Priority: Major > Attachments: Screen Shot 2018-09-03 at 2.16.47 PM.png > > > While testing on full-dev, I've noticed many 404 errors in the browser > console when I click to open the details panel for different parsers in the > management UI. Is this by design, or are these endpoints broken? I tested > these endpoints in swagger and had the same results. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (METRON-1749) Update Angular to latest release in Management UI
[ https://issues.apache.org/jira/browse/METRON-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-1749: Assignee: Shane Ardell > Update Angular to latest release in Management UI > - > > Key: METRON-1749 > URL: https://issues.apache.org/jira/browse/METRON-1749 > Project: Metron > Issue Type: Improvement >Reporter: Shane Ardell >Assignee: Shane Ardell >Priority: Major > > Currently, the Management UI is on Angular v2. Not only has there been many > updates and improvements to Angular, that release is no longer supported by > the Angular team. This means critical fixes and security patches are no > longer being done. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-1830) Re-implement Alerts dialog box without jQuery
Shane Ardell created METRON-1830: Summary: Re-implement Alerts dialog box without jQuery Key: METRON-1830 URL: https://issues.apache.org/jira/browse/METRON-1830 Project: Metron Issue Type: Bug Reporter: Shane Ardell Currently, the dialog box class in both UIs directly manipulates the DOM with jQuery. This is problematic when using a framework like Angular because it causes a disconnect with how Angular handles and tracks DOM changes. We also don't take advantage of Angular's rendering engine. The dialog box can and should be implemented as a component and a singleton service (since we would never want to launch more than one modal at a time). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (METRON-1830) Re-implement Alerts dialog box without jQuery
[ https://issues.apache.org/jira/browse/METRON-1830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-1830: Assignee: Shane Ardell > Re-implement Alerts dialog box without jQuery > - > > Key: METRON-1830 > URL: https://issues.apache.org/jira/browse/METRON-1830 > Project: Metron > Issue Type: Bug >Reporter: Shane Ardell >Assignee: Shane Ardell >Priority: Minor > > Currently, the dialog box class in both UIs directly manipulates the DOM with > jQuery. This is problematic when using a framework like Angular because it > causes a disconnect with how Angular handles and tracks DOM changes. We also > don't take advantage of Angular's rendering engine. > The dialog box can and should be implemented as a component and a singleton > service (since we would never want to launch more than one modal at a time). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-1873) Update Bootstrap version in Management UI
Shane Ardell created METRON-1873: Summary: Update Bootstrap version in Management UI Key: METRON-1873 URL: https://issues.apache.org/jira/browse/METRON-1873 Project: Metron Issue Type: Bug Reporter: Shane Ardell We are currently using an alpha version of Bootstrap v4. We should update to the latest stable release (v4.1.3) for a couple of reasons. There were breaking changes between the alpha and stable release that make it impossible for us to use angular ports of Bootstrap like ng-bootstrap. In addition, there are quite a few features and fixes we would want in our project. The list is long, but if you're curious, [take a look at the changelog|https://github.com/twbs/bootstrap/releases]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-1898) Migrate existing e2e tests in Alerts UI to Cypress
Shane Ardell created METRON-1898: Summary: Migrate existing e2e tests in Alerts UI to Cypress Key: METRON-1898 URL: https://issues.apache.org/jira/browse/METRON-1898 Project: Metron Issue Type: Bug Reporter: Shane Ardell As discussed in [this thread|https://lists.apache.org/list.html?d...@metron.apache.org:lte=1M:cypress], we should migrate the existing e2e tests from Protractor to Cypress. This ticket focuses on the Alerts UI. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-1899) Migrate tests from Alert Details Pane
Shane Ardell created METRON-1899: Summary: Migrate tests from Alert Details Pane Key: METRON-1899 URL: https://issues.apache.org/jira/browse/METRON-1899 Project: Metron Issue Type: Sub-task Reporter: Shane Ardell Alert details pane (metron-alerts/e2e/alert-details/alert-status/alert-details-status.e2e-spec.ts) *Existing tests to move:* * Changing alert statuses * Adding comment for table view * Adding comment for tree view *Scenarios to add:* * Deleting comment -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (METRON-1899) Migrate tests from Alert Details Status spec
[ https://issues.apache.org/jira/browse/METRON-1899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell updated METRON-1899: - Summary: Migrate tests from Alert Details Status spec (was: Migrate tests from Alert Details Pane) > Migrate tests from Alert Details Status spec > > > Key: METRON-1899 > URL: https://issues.apache.org/jira/browse/METRON-1899 > Project: Metron > Issue Type: Sub-task >Reporter: Shane Ardell >Priority: Major > > Alert details pane > (metron-alerts/e2e/alert-details/alert-status/alert-details-status.e2e-spec.ts) > *Existing tests to move:* > * Changing alert statuses > * Adding comment for table view > * Adding comment for tree view > *Scenarios to add:* > * Deleting comment -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-1900) Migrate tests from Alert Filters spec
Shane Ardell created METRON-1900: Summary: Migrate tests from Alert Filters spec Key: METRON-1900 URL: https://issues.apache.org/jira/browse/METRON-1900 Project: Metron Issue Type: Sub-task Reporter: Shane Ardell Filtering alerts (metron-alerts/e2e/alerts-list/alert-filters/alert-filters.e2e-spec.ts) *Existing tests to migrate:* * Display facets data * Search when facet is selected -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (METRON-1899) Migrate and add tests from Alert Details Status spec
[ https://issues.apache.org/jira/browse/METRON-1899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell updated METRON-1899: - Summary: Migrate and add tests from Alert Details Status spec (was: Migrate tests from Alert Details Status spec) > Migrate and add tests from Alert Details Status spec > > > Key: METRON-1899 > URL: https://issues.apache.org/jira/browse/METRON-1899 > Project: Metron > Issue Type: Sub-task >Reporter: Shane Ardell >Priority: Major > > Alert details pane > (metron-alerts/e2e/alert-details/alert-status/alert-details-status.e2e-spec.ts) > *Existing tests to move:* > * Changing alert statuses > * Adding comment for table view > * Adding comment for tree view > *Scenarios to add:* > * Deleting comment -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-1901) Migrate tests from Alert List Status spec
Shane Ardell created METRON-1901: Summary: Migrate tests from Alert List Status spec Key: METRON-1901 URL: https://issues.apache.org/jira/browse/METRON-1901 Project: Metron Issue Type: Sub-task Reporter: Shane Ardell *Alert item status change on the list and tree view* (metron-alerts/e2e/alerts-list/alert-status/alerts-list-status.e2e-spec.ts) *Existing tests to migrate:* * change alert status for multiple alerts to OPEN * change alert status for multiple alerts to DISMISS * change alert status for multiple alerts to ESCALATE * change alert status for multiple alerts to RESOLVE * change alert status for multiple alerts to OPEN in tree view * change alert status for multiple alerts to DISMISS in tree view * change alert status for multiple alerts to ESCALATE in tree view * change alert status for multiple alerts to RESOLVE in tree view -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (METRON-1900) Migrate tests from Alert Filters spec
[ https://issues.apache.org/jira/browse/METRON-1900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell updated METRON-1900: - Description: *Filtering alerts* (metron-alerts/e2e/alerts-list/alert-filters/alert-filters.e2e-spec.ts) *Existing tests to migrate:* * Display facets data * Search when facet is selected was: Filtering alerts (metron-alerts/e2e/alerts-list/alert-filters/alert-filters.e2e-spec.ts) *Existing tests to migrate:* * Display facets data * Search when facet is selected > Migrate tests from Alert Filters spec > - > > Key: METRON-1900 > URL: https://issues.apache.org/jira/browse/METRON-1900 > Project: Metron > Issue Type: Sub-task >Reporter: Shane Ardell >Priority: Major > > *Filtering alerts* > (metron-alerts/e2e/alerts-list/alert-filters/alert-filters.e2e-spec.ts) > *Existing tests to migrate:* > * Display facets data > * Search when facet is selected -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-1902) Migrate tests from Configure Table spec
Shane Ardell created METRON-1902: Summary: Migrate tests from Configure Table spec Key: METRON-1902 URL: https://issues.apache.org/jira/browse/METRON-1902 Project: Metron Issue Type: Sub-task Reporter: Shane Ardell *Configure table view* (metron-alerts/e2e/alerts-list/configure-table/configure-table.e2e-spec.ts) *Existing tests to migrate:* * select columns from table configuration * rename columns from table configuration -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (METRON-1899) Migrate and add tests from Alert Details Status spec
[ https://issues.apache.org/jira/browse/METRON-1899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell updated METRON-1899: - Description: *__**Alert details pane* (metron-alerts/e2e/alert-details/alert-status/alert-details-status.e2e-spec.ts) *Existing tests to move:* * Changing alert statuses * Adding comment for table view * Adding comment for tree view *Scenarios to add:* * Deleting comment was: Alert details pane (metron-alerts/e2e/alert-details/alert-status/alert-details-status.e2e-spec.ts) *Existing tests to move:* * Changing alert statuses * Adding comment for table view * Adding comment for tree view *Scenarios to add:* * Deleting comment > Migrate and add tests from Alert Details Status spec > > > Key: METRON-1899 > URL: https://issues.apache.org/jira/browse/METRON-1899 > Project: Metron > Issue Type: Sub-task >Reporter: Shane Ardell >Priority: Major > > *__**Alert details pane* > > (metron-alerts/e2e/alert-details/alert-status/alert-details-status.e2e-spec.ts) > *Existing tests to move:* > * Changing alert statuses > * Adding comment for table view > * Adding comment for tree view > *Scenarios to add:* > * Deleting comment -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-1904) Migrate tests from Save Search spec
Shane Ardell created METRON-1904: Summary: Migrate tests from Save Search spec Key: METRON-1904 URL: https://issues.apache.org/jira/browse/METRON-1904 Project: Metron Issue Type: Sub-task Reporter: Shane Ardell *Search and save search* (metron-alerts/e2e/alerts-list/save-search/save-search.e2e-spec.ts) *Existing tests to migrate:* * should display all the default values for saved searches * should have all save search controls and they save search should be working * should delete search items from search box * should delete first search items from search box having multiple search fields * manually entering search queries to search box and pressing enter key should search -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-1905) Migrate tests from Table View spec
Shane Ardell created METRON-1905: Summary: Migrate tests from Table View spec Key: METRON-1905 URL: https://issues.apache.org/jira/browse/METRON-1905 Project: Metron Issue Type: Sub-task Reporter: Shane Ardell *Alerts table view* (metron-alerts/e2e/alerts-list/table-view/table-view.e2e-spec.ts) *Existing tests to migrate:* * sorting ASC by ip_src_addr * sorting DESC by ip_src_addr * sorting ASC by Score * sorting DESC by Score -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-1906) Migrate tests from Tree View spec
Shane Ardell created METRON-1906: Summary: Migrate tests from Tree View spec Key: METRON-1906 URL: https://issues.apache.org/jira/browse/METRON-1906 Project: Metron Issue Type: Sub-task Reporter: Shane Ardell *Alerts tree view* (metron-alerts/e2e/alerts-list/tree-view/tree-view.e2e-spec.ts) *Existing tests to migrate:* * should have all group by elements * drag and drop should change group order * should have group details for single group by * should have group details for multiple group by * should have sort working for group details for multiple sub groups * should have search working for group details for multiple sub groups -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-1908) Migrate alerts from Login spec
Shane Ardell created METRON-1908: Summary: Migrate alerts from Login spec Key: METRON-1908 URL: https://issues.apache.org/jira/browse/METRON-1908 Project: Metron Issue Type: Sub-task Reporter: Shane Ardell *Login* (metron-alerts/e2e/login/login.e2e-spec.ts) *Existing alerts to migrate:* * should display error message for invalid credentials * should login for valid credentials * should logout -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-1907) Migrate tests from Alerts List spec
Shane Ardell created METRON-1907: Summary: Migrate tests from Alerts List spec Key: METRON-1907 URL: https://issues.apache.org/jira/browse/METRON-1907 Project: Metron Issue Type: Sub-task Reporter: Shane Ardell *Alert list* (metron-alerts/e2e/alerts-list/alerts-list.e2e-spec.ts) *Existing tests to migrate:* * should have all the UI elements * should have all pagination controls and they should be working * should have all settings controls and they should be working * play pause should start polling and stop polling * should select columns from table configuration * should have all time-range controls * should have all time range values populated - 1 * should have all time range values populated - 2 * should have all time range values populated - 3 * should have all time range values populated - 4 * should disable date picker when timestamp is present in search * should have now included when to date is empty * should have all time-range included while searching -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-1903) Migrate tests from Meta Alerts spec
Shane Ardell created METRON-1903: Summary: Migrate tests from Meta Alerts spec Key: METRON-1903 URL: https://issues.apache.org/jira/browse/METRON-1903 Project: Metron Issue Type: Sub-task Reporter: Shane Ardell *Meta Alerts* (metron-alerts/e2e/alerts-list/meta-alerts/meta-alert.e2e-spec.ts) *Existing tests to migrate:* * should have all the steps for meta alerts workflow * should create a meta alert from nesting of more than one level * remove meta alerts -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-1930) Update webpack-dev-server in Alerts UI
Shane Ardell created METRON-1930: Summary: Update webpack-dev-server in Alerts UI Key: METRON-1930 URL: https://issues.apache.org/jira/browse/METRON-1930 Project: Metron Issue Type: Bug Reporter: Shane Ardell Attachments: Screen Shot 2018-12-10 at 4.46.33 PM.png After running `npm audit` in the Alerts UI, it looks like we need to update our version of webpack-dev-server. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-1936) Cypress fails when trying to parse double quotes
Shane Ardell created METRON-1936: Summary: Cypress fails when trying to parse double quotes Key: METRON-1936 URL: https://issues.apache.org/jira/browse/METRON-1936 Project: Metron Issue Type: Bug Reporter: Shane Ardell Double quotes that are used inside the parser list component are causing a parsing issue for Cypress, even if you switch them out with html encoded double quotes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-1958) Optimize Cypress to use best practices
Shane Ardell created METRON-1958: Summary: Optimize Cypress to use best practices Key: METRON-1958 URL: https://issues.apache.org/jira/browse/METRON-1958 Project: Metron Issue Type: Bug Reporter: Shane Ardell As of recent, there have been multiple unpredictable Cypress failures in Travis. While looking into these failures, I noticed a few anti-patterns we have in place that could definitely cause these failures: 1) We currently run `ng serve --aot` as a test server for Cypress. We are running this command in parallel with the command that starts Cypress. As you could imagine, this presents a race condition where Cypress could start running before the server starts. Instead of using Angular CLI to build and serve our project for Cypress to test against, we should first build the project, then serve the built project with the Express server we have in place already. Serving an already built project with Express is so fast we should be able to confidently run it in parallel with the Cypress test script and not worry about any race conditions failing our tests. This is the standard practice that has been shown in other Angular/Cypress test examples. 2) Per the Cypress team's best practice recommendations, [we should remove the command to logout in the afterEach hook|https://docs.cypress.io/guides/references/best-practices.html#Using-after-or-afterEach-hooks] since it's unnecessary for our needs and may be the cause for our failures regarding the logout link. 3) Again per the Cypress team's best practices, [we should set a baseUrl in our cypress.json config file|https://docs.cypress.io/guides/references/best-practices.html#Setting-a-global-baseUrl]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-1959) Ensure server starts before Cypress
Shane Ardell created METRON-1959: Summary: Ensure server starts before Cypress Key: METRON-1959 URL: https://issues.apache.org/jira/browse/METRON-1959 Project: Metron Issue Type: Bug Reporter: Shane Ardell Per the Cypress team's recommendation, we should be using the `wait-on` or `start-server-and-test` packages to ensure our server starts before Cypress runs and prevent a possible race condition. https://docs.cypress.io/guides/guides/continuous-integration.html#Boot-your-server -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (METRON-1908) Migrate alerts from Login spec
[ https://issues.apache.org/jira/browse/METRON-1908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-1908: Assignee: Shane Ardell > Migrate alerts from Login spec > -- > > Key: METRON-1908 > URL: https://issues.apache.org/jira/browse/METRON-1908 > Project: Metron > Issue Type: Sub-task >Reporter: Shane Ardell >Assignee: Shane Ardell >Priority: Major > > *Login* > (metron-alerts/e2e/login/login.e2e-spec.ts) > *Existing alerts to migrate:* > * should display error message for invalid credentials > * should login for valid credentials > * should logout -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (METRON-1908) Migrate tests from Login spec
[ https://issues.apache.org/jira/browse/METRON-1908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell updated METRON-1908: - Summary: Migrate tests from Login spec (was: Migrate alerts from Login spec) > Migrate tests from Login spec > - > > Key: METRON-1908 > URL: https://issues.apache.org/jira/browse/METRON-1908 > Project: Metron > Issue Type: Sub-task >Reporter: Shane Ardell >Assignee: Shane Ardell >Priority: Major > > *Login* > (metron-alerts/e2e/login/login.e2e-spec.ts) > *Existing alerts to migrate:* > * should display error message for invalid credentials > * should login for valid credentials > * should logout -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (METRON-1906) Migrate tests from Tree View spec
[ https://issues.apache.org/jira/browse/METRON-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-1906: Assignee: Shane Ardell > Migrate tests from Tree View spec > - > > Key: METRON-1906 > URL: https://issues.apache.org/jira/browse/METRON-1906 > Project: Metron > Issue Type: Sub-task >Reporter: Shane Ardell >Assignee: Shane Ardell >Priority: Major > > *Alerts tree view* > (metron-alerts/e2e/alerts-list/tree-view/tree-view.e2e-spec.ts) > *Existing tests to migrate:* > * should have all group by elements > * drag and drop should change group order > * should have group details for single group by > * should have group details for multiple group by > * should have sort working for group details for multiple sub groups > * should have search working for group details for multiple sub groups -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (METRON-1930) Update webpack-dev-server in Alerts UI
[ https://issues.apache.org/jira/browse/METRON-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-1930: Assignee: Shane Ardell > Update webpack-dev-server in Alerts UI > -- > > Key: METRON-1930 > URL: https://issues.apache.org/jira/browse/METRON-1930 > Project: Metron > Issue Type: Bug >Reporter: Shane Ardell >Assignee: Shane Ardell >Priority: Major > Attachments: Screen Shot 2018-12-10 at 4.46.33 PM.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > After running `npm audit` in the Alerts UI, it looks like we need to update > our version of webpack-dev-server. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (METRON-1902) Migrate tests from Configure Table spec
[ https://issues.apache.org/jira/browse/METRON-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-1902: Assignee: Tibor Meller > Migrate tests from Configure Table spec > --- > > Key: METRON-1902 > URL: https://issues.apache.org/jira/browse/METRON-1902 > Project: Metron > Issue Type: Sub-task >Reporter: Shane Ardell >Assignee: Tibor Meller >Priority: Major > > *Configure table view* > (metron-alerts/e2e/alerts-list/configure-table/configure-table.e2e-spec.ts) > *Existing tests to migrate:* > * select columns from table configuration > * rename columns from table configuration -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (METRON-1901) Migrate tests from Alert List Status spec
[ https://issues.apache.org/jira/browse/METRON-1901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-1901: Assignee: Tamas Fodor > Migrate tests from Alert List Status spec > - > > Key: METRON-1901 > URL: https://issues.apache.org/jira/browse/METRON-1901 > Project: Metron > Issue Type: Sub-task >Reporter: Shane Ardell >Assignee: Tamas Fodor >Priority: Major > > *Alert item status change on the list and tree view* > (metron-alerts/e2e/alerts-list/alert-status/alerts-list-status.e2e-spec.ts) > *Existing tests to migrate:* > * change alert status for multiple alerts to OPEN > * change alert status for multiple alerts to DISMISS > * change alert status for multiple alerts to ESCALATE > * change alert status for multiple alerts to RESOLVE > * change alert status for multiple alerts to OPEN in tree view > * change alert status for multiple alerts to DISMISS in tree view > * change alert status for multiple alerts to ESCALATE in tree view > * change alert status for multiple alerts to RESOLVE in tree view -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (METRON-1905) Migrate tests from Table View spec
[ https://issues.apache.org/jira/browse/METRON-1905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-1905: Assignee: Tibor Meller > Migrate tests from Table View spec > -- > > Key: METRON-1905 > URL: https://issues.apache.org/jira/browse/METRON-1905 > Project: Metron > Issue Type: Sub-task >Reporter: Shane Ardell >Assignee: Tibor Meller >Priority: Major > > *Alerts table view* > (metron-alerts/e2e/alerts-list/table-view/table-view.e2e-spec.ts) > *Existing tests to migrate:* > * sorting ASC by ip_src_addr > * sorting DESC by ip_src_addr > * sorting ASC by Score > * sorting DESC by Score -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (METRON-1936) Cypress fails when trying to parse double quotes
[ https://issues.apache.org/jira/browse/METRON-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-1936: Assignee: Shane Ardell > Cypress fails when trying to parse double quotes > > > Key: METRON-1936 > URL: https://issues.apache.org/jira/browse/METRON-1936 > Project: Metron > Issue Type: Bug >Reporter: Shane Ardell >Assignee: Shane Ardell >Priority: Major > Time Spent: 1h > Remaining Estimate: 0h > > Double quotes that are used inside the parser list component are causing a > parsing issue for Cypress, even if you switch them out with html encoded > double quotes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (METRON-1903) Migrate tests from Meta Alerts spec
[ https://issues.apache.org/jira/browse/METRON-1903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-1903: Assignee: Tamas Fodor > Migrate tests from Meta Alerts spec > --- > > Key: METRON-1903 > URL: https://issues.apache.org/jira/browse/METRON-1903 > Project: Metron > Issue Type: Sub-task >Reporter: Shane Ardell >Assignee: Tamas Fodor >Priority: Major > > *Meta Alerts* > (metron-alerts/e2e/alerts-list/meta-alerts/meta-alert.e2e-spec.ts) > *Existing tests to migrate:* > * should have all the steps for meta alerts workflow > * should create a meta alert from nesting of more than one level > * remove meta alerts -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (METRON-1958) Optimize Cypress to use best practices
[ https://issues.apache.org/jira/browse/METRON-1958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-1958: Assignee: Shane Ardell > Optimize Cypress to use best practices > -- > > Key: METRON-1958 > URL: https://issues.apache.org/jira/browse/METRON-1958 > Project: Metron > Issue Type: Bug >Reporter: Shane Ardell >Assignee: Shane Ardell >Priority: Major > Time Spent: 1h 10m > Remaining Estimate: 0h > > As of recent, there have been multiple unpredictable Cypress failures in > Travis. While looking into these failures, I noticed a few anti-patterns we > have in place that could definitely cause these failures: > 1) We currently run `ng serve --aot` as a test server for Cypress. We are > running this command in parallel with the command that starts Cypress. As you > could imagine, this presents a race condition where Cypress could start > running before the server starts. Instead of using Angular CLI to build and > serve our project for Cypress to test against, we should first build the > project, then serve the built project with the Express server we have in > place already. Serving an already built project with Express is so fast we > should be able to confidently run it in parallel with the Cypress test script > and not worry about any race conditions failing our tests. This is the > standard practice that has been shown in other Angular/Cypress test examples. > 2) Per the Cypress team's best practice recommendations, [we should remove > the command to logout in the afterEach > hook|https://docs.cypress.io/guides/references/best-practices.html#Using-after-or-afterEach-hooks] > since it's unnecessary for our needs and may be the cause for our failures > regarding the logout link. > 3) Again per the Cypress team's best practices, [we should set a baseUrl in > our cypress.json config > file|https://docs.cypress.io/guides/references/best-practices.html#Setting-a-global-baseUrl]. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (METRON-1907) Migrate tests from Alerts List spec
[ https://issues.apache.org/jira/browse/METRON-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-1907: Assignee: Tamas Fodor > Migrate tests from Alerts List spec > --- > > Key: METRON-1907 > URL: https://issues.apache.org/jira/browse/METRON-1907 > Project: Metron > Issue Type: Sub-task >Reporter: Shane Ardell >Assignee: Tamas Fodor >Priority: Major > > *Alert list* > (metron-alerts/e2e/alerts-list/alerts-list.e2e-spec.ts) > *Existing tests to migrate:* > * should have all the UI elements > * should have all pagination controls and they should be working > * should have all settings controls and they should be working > * play pause should start polling and stop polling > * should select columns from table configuration > * should have all time-range controls > * should have all time range values populated - 1 > * should have all time range values populated - 2 > * should have all time range values populated - 3 > * should have all time range values populated - 4 > * should disable date picker when timestamp is present in search > * should have now included when to date is empty > * should have all time-range included while searching -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (METRON-1900) Migrate tests from Alert Filters spec
[ https://issues.apache.org/jira/browse/METRON-1900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-1900: Assignee: Tamas Fodor (was: Shane Ardell) > Migrate tests from Alert Filters spec > - > > Key: METRON-1900 > URL: https://issues.apache.org/jira/browse/METRON-1900 > Project: Metron > Issue Type: Sub-task >Reporter: Shane Ardell >Assignee: Tamas Fodor >Priority: Major > > *Filtering alerts* > (metron-alerts/e2e/alerts-list/alert-filters/alert-filters.e2e-spec.ts) > *Existing tests to migrate:* > * Display facets data > * Search when facet is selected -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (METRON-1899) Migrate and add tests from Alert Details Status spec
[ https://issues.apache.org/jira/browse/METRON-1899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-1899: Assignee: Shane Ardell > Migrate and add tests from Alert Details Status spec > > > Key: METRON-1899 > URL: https://issues.apache.org/jira/browse/METRON-1899 > Project: Metron > Issue Type: Sub-task >Reporter: Shane Ardell >Assignee: Shane Ardell >Priority: Major > > *__**Alert details pane* > > (metron-alerts/e2e/alert-details/alert-status/alert-details-status.e2e-spec.ts) > *Existing tests to move:* > * Changing alert statuses > * Adding comment for table view > * Adding comment for tree view > *Scenarios to add:* > * Deleting comment -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (METRON-1900) Migrate tests from Alert Filters spec
[ https://issues.apache.org/jira/browse/METRON-1900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-1900: Assignee: Shane Ardell > Migrate tests from Alert Filters spec > - > > Key: METRON-1900 > URL: https://issues.apache.org/jira/browse/METRON-1900 > Project: Metron > Issue Type: Sub-task >Reporter: Shane Ardell >Assignee: Shane Ardell >Priority: Major > > *Filtering alerts* > (metron-alerts/e2e/alerts-list/alert-filters/alert-filters.e2e-spec.ts) > *Existing tests to migrate:* > * Display facets data > * Search when facet is selected -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-1971) Short timeout value in Cypress may cause build failures
Shane Ardell created METRON-1971: Summary: Short timeout value in Cypress may cause build failures Key: METRON-1971 URL: https://issues.apache.org/jira/browse/METRON-1971 Project: Metron Issue Type: Bug Reporter: Shane Ardell According to the Cypress docs, it is unnecessary to add a wait command after cy.visit. "Waiting for this is unnecessary because the cy.visit() resolves once the page fires its load event. By that time all of your assets have been loaded including javascript, stylesheets, and html." However, the problem is with an Angular application, the page firing a load event does not mean that the entire view has rendered yet. In systems where memory is scarce, such as a Travis environment or a machine that has memory-intensive applications running, this means a page load can take a few seconds (or possibly even longer). We currently use the default timeout in Cypress, which is only 4000ms. I believe this short timeout can cause failures like this in Metron: https://travis-ci.org/apache/metron/jobs/483945575 We should increase the defaultCommandTimeout in cypress.json to something like 3ms or greater to prevent failures like this in the future. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-1987) Upgrade Alert UI to stable Bootstrap 4
Shane Ardell created METRON-1987: Summary: Upgrade Alert UI to stable Bootstrap 4 Key: METRON-1987 URL: https://issues.apache.org/jira/browse/METRON-1987 Project: Metron Issue Type: Bug Reporter: Shane Ardell -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (METRON-1987) Upgrade Alert UI to stable Bootstrap 4
[ https://issues.apache.org/jira/browse/METRON-1987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell updated METRON-1987: - Description: Like we did for the Management UI, we should upgrade the version of Bootstrap that we are using to the latest stable version. We are currently on an alpha version which includes deprecated class names and values. > Upgrade Alert UI to stable Bootstrap 4 > -- > > Key: METRON-1987 > URL: https://issues.apache.org/jira/browse/METRON-1987 > Project: Metron > Issue Type: Bug >Reporter: Shane Ardell >Priority: Major > > Like we did for the Management UI, we should upgrade the version of Bootstrap > that we are using to the latest stable version. We are currently on an alpha > version which includes deprecated class names and values. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-2029) Configure Table should have filter
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)
[jira] [Created] (METRON-2059) Downgrade Cypress version back to non-failing version
Shane Ardell created METRON-2059: Summary: Downgrade Cypress version back to non-failing version Key: METRON-2059 URL: https://issues.apache.org/jira/browse/METRON-2059 Project: Metron Issue Type: Bug Reporter: Shane Ardell We currently have an intermittent failure happening in Travis stemming from yauzl, the unzipping tool used by Cypress. The issue is currently open in their issues and can be found here: https://github.com/cypress-io/cypress/issues/3515 According to some feedback on that linked issue, some have had luck downgrading the version of Cypress to 3.1.0. We should downgrade and test with multiple builds to try to resolve this issue. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (METRON-2059) Downgrade Cypress version back to non-failing version
[ https://issues.apache.org/jira/browse/METRON-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-2059: Assignee: Shane Ardell > Downgrade Cypress version back to non-failing version > - > > Key: METRON-2059 > URL: https://issues.apache.org/jira/browse/METRON-2059 > Project: Metron > Issue Type: Bug >Reporter: Shane Ardell >Assignee: Shane Ardell >Priority: Major > > We currently have an intermittent failure happening in Travis stemming from > yauzl, the unzipping tool used by Cypress. The issue is currently open in > their issues and can be found here: > https://github.com/cypress-io/cypress/issues/3515 > According to some feedback on that linked issue, some have had luck > downgrading the version of Cypress to 3.1.0. We should downgrade and test > with multiple builds to try to resolve this issue. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-2063) Prevent focused statements from being left in front-end tests
Shane Ardell created METRON-2063: Summary: Prevent focused statements from being left in front-end tests Key: METRON-2063 URL: https://issues.apache.org/jira/browse/METRON-2063 Project: Metron Issue Type: Improvement Reporter: Shane Ardell Focused statements are incredibly handy when creating and debugging unit tests. However, they sometimes find their way into our code, as seen here: https://github.com/apache/metron/pull/1372 We should think about adding a linter rule or possibly a 3rd party plugin to fail the build if a focused statement committed to code. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (METRON-1856) [UI] Implement parser grouping with drag and drop
[ https://issues.apache.org/jira/browse/METRON-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell updated METRON-1856: - Attachment: create-parser-group.gif > [UI] Implement parser grouping with drag and drop > - > > Key: METRON-1856 > URL: https://issues.apache.org/jira/browse/METRON-1856 > Project: Metron > Issue Type: New Feature >Reporter: Tibor Meller >Priority: Major > Attachments: create-parser-group.gif > > Time Spent: 1h 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (METRON-1856) [UI] Implement parser grouping with drag and drop
[ https://issues.apache.org/jira/browse/METRON-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell updated METRON-1856: - Description: The capability to group parsers via the CLI already exists in Metron, but it currently is not possible to do so through the Management UI. This feature seems important as it allows users to pass in groups of parsers to start, stop, disable and enable rather than enacting the action on each individual parser. An initial implementation of the UI was done by Tamás Fodor, Tibor Meller and myself (@ruffle1986, @tiborm and @sardell on GitHub, respectively), and the REST endpoint work was performed by Ryan Merriman in PR 1396: [https://github.com/apache/metron/pull/1396]. Here is a brief description of the UI changes. In order to create a parser group, simply drag and drop two parsers together. You can optionally update the name and add a description before creating the group. !create-parser-group.gif|width=601,height=330! > [UI] Implement parser grouping with drag and drop > - > > Key: METRON-1856 > URL: https://issues.apache.org/jira/browse/METRON-1856 > Project: Metron > Issue Type: New Feature >Reporter: Tibor Meller >Priority: Major > Attachments: create-parser-group.gif > > Time Spent: 1h 40m > Remaining Estimate: 0h > > The capability to group parsers via the CLI already exists in Metron, but it > currently is not possible to do so through the Management UI. This feature > seems important as it allows users to pass in groups of parsers to start, > stop, disable and enable rather than enacting the action on each individual > parser. > An initial implementation of the UI was done by Tamás Fodor, Tibor Meller and > myself (@ruffle1986, @tiborm and @sardell on GitHub, respectively), and the > REST endpoint work was performed by Ryan Merriman in PR 1396: > [https://github.com/apache/metron/pull/1396]. > Here is a brief description of the UI changes. > In order to create a parser group, simply drag and drop two parsers together. > You can optionally update the name and add a description before creating the > group. > !create-parser-group.gif|width=601,height=330! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (METRON-1856) [UI] Implement parser grouping with drag and drop
[ https://issues.apache.org/jira/browse/METRON-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell updated METRON-1856: - Attachment: save-parser-group.gif > [UI] Implement parser grouping with drag and drop > - > > Key: METRON-1856 > URL: https://issues.apache.org/jira/browse/METRON-1856 > Project: Metron > Issue Type: New Feature >Reporter: Tibor Meller >Priority: Major > Attachments: create-parser-group.gif, save-parser-group.gif > > Time Spent: 1h 40m > Remaining Estimate: 0h > > The capability to group parsers via the CLI already exists in Metron, but it > currently is not possible to do so through the Management UI. This feature > seems important as it allows users to pass in groups of parsers to start, > stop, disable and enable rather than enacting the action on each individual > parser. > An initial implementation of the UI was done by Tamás Fodor, Tibor Meller and > myself (@ruffle1986, @tiborm and @sardell on GitHub, respectively), and the > REST endpoint work was performed by Ryan Merriman in PR 1396: > [https://github.com/apache/metron/pull/1396]. > Here is a brief description of the UI changes. > In order to create a parser group, simply drag and drop two parsers together. > You can optionally update the name and add a description before creating the > group. > !create-parser-group.gif|width=601,height=330! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (METRON-1856) [UI] Implement parser grouping with drag and drop
[ https://issues.apache.org/jira/browse/METRON-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell updated METRON-1856: - Description: The capability to group parsers via the CLI already exists in Metron, but it currently is not possible to do so through the Management UI. This feature seems important as it allows users to pass in groups of parsers to start, stop, disable and enable rather than enacting the action on each individual parser. An initial implementation of the UI was done by Tamás Fodor, Tibor Meller and myself (@ruffle1986, @tiborm and @sardell on GitHub, respectively), and the REST endpoint work was performed by Ryan Merriman in PR 1396: [https://github.com/apache/metron/pull/1396]. Here is a brief description of the UI changes. In order to create a parser group, simply drag and drop two parsers together. A user can optionally update the name and add a description before creating the group. Notice that once a group is created, the parser group is highlighted in green and the parsers moved inside of a group are highlighted in yellow. !create-parser-group.gif|width=601,height=330! Once a user has created the parser groups they want, they can simply click on the apply button at the bottom of the screen. You'll notice the highlighting colors go away, a success message appears and controls for all the parsers in the group are available at the group level (in this case the start button). !save-parser-group.gif|width=601,height=330! If a user wants to delete a group, they can simply click on the trash can icon in the group's controls section. We chose to keep the confirmation popup in addition to the apply button in order to prevent accidental group deletions and prevent sending multiple http delete calls one after the other to the backend. If a user decides not to delete a group after confirming with the modal window, they can click on the discard button to return to the previous state. was: The capability to group parsers via the CLI already exists in Metron, but it currently is not possible to do so through the Management UI. This feature seems important as it allows users to pass in groups of parsers to start, stop, disable and enable rather than enacting the action on each individual parser. An initial implementation of the UI was done by Tamás Fodor, Tibor Meller and myself (@ruffle1986, @tiborm and @sardell on GitHub, respectively), and the REST endpoint work was performed by Ryan Merriman in PR 1396: [https://github.com/apache/metron/pull/1396]. Here is a brief description of the UI changes. In order to create a parser group, simply drag and drop two parsers together. You can optionally update the name and add a description before creating the group. !create-parser-group.gif|width=601,height=330! > [UI] Implement parser grouping with drag and drop > - > > Key: METRON-1856 > URL: https://issues.apache.org/jira/browse/METRON-1856 > Project: Metron > Issue Type: New Feature >Reporter: Tibor Meller >Priority: Major > Attachments: create-parser-group.gif, save-parser-group.gif > > Time Spent: 1h 40m > Remaining Estimate: 0h > > The capability to group parsers via the CLI already exists in Metron, but it > currently is not possible to do so through the Management UI. This feature > seems important as it allows users to pass in groups of parsers to start, > stop, disable and enable rather than enacting the action on each individual > parser. > An initial implementation of the UI was done by Tamás Fodor, Tibor Meller and > myself (@ruffle1986, @tiborm and @sardell on GitHub, respectively), and the > REST endpoint work was performed by Ryan Merriman in PR 1396: > [https://github.com/apache/metron/pull/1396]. > Here is a brief description of the UI changes. > In order to create a parser group, simply drag and drop two parsers together. > A user can optionally update the name and add a description before creating > the group. Notice that once a group is created, the parser group is > highlighted in green and the parsers moved inside of a group are highlighted > in yellow. > !create-parser-group.gif|width=601,height=330! > Once a user has created the parser groups they want, they can simply click on > the apply button at the bottom of the screen. You'll notice the highlighting > colors go away, a success message appears and controls for all the parsers in > the group are available at the group level (in this case the start button). > !save-parser-group.gif|width=601,height=330! > If a user wants to delete a group, they can simply click on the trash can > icon in the group's controls section. We chose to keep the confirmation popup > in addition to the apply button in order to prevent accidental group > deletions and preve
[jira] [Updated] (METRON-1856) [UI] Implement parser grouping with drag and drop
[ https://issues.apache.org/jira/browse/METRON-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell updated METRON-1856: - Attachment: delete-parser-group.gif > [UI] Implement parser grouping with drag and drop > - > > Key: METRON-1856 > URL: https://issues.apache.org/jira/browse/METRON-1856 > Project: Metron > Issue Type: New Feature >Reporter: Tibor Meller >Priority: Major > Attachments: create-parser-group.gif, delete-parser-group.gif, > merge-and-create-new-group.gif, save-parser-group.gif > > Time Spent: 1h 40m > Remaining Estimate: 0h > > The capability to group parsers via the CLI already exists in Metron, but it > currently is not possible to do so through the Management UI. This feature > seems important as it allows users to pass in groups of parsers to start, > stop, disable and enable rather than enacting the action on each individual > parser. > An initial implementation of the UI was done by Tamás Fodor, Tibor Meller and > myself (@ruffle1986, @tiborm and @sardell on GitHub, respectively), and the > REST endpoint work was performed by Ryan Merriman in PR 1396: > [https://github.com/apache/metron/pull/1396]. > Here is a brief description of the UI changes. > In order to create a parser group, simply drag and drop two parsers together. > A user can optionally update the name and add a description before creating > the group. Notice that once a group is created, the parser group is > highlighted in green and the parsers moved inside of a group are highlighted > in yellow. > !create-parser-group.gif|width=601,height=330! > Once a user has created the parser groups they want, they can simply click on > the apply button at the bottom of the screen. You'll notice the highlighting > colors go away, a success message appears and controls for all the parsers in > the group are available at the group level (in this case the start button). > !save-parser-group.gif|width=601,height=330! > If a user wants to delete a group, they can simply click on the trash can > icon in the group's controls section. We chose to keep the confirmation popup > in addition to the apply button in order to prevent accidental group > deletions and prevent sending multiple http delete calls one after the other > to the backend. If a user decides not to delete a group after confirming with > the modal window, they can click on the discard button to return to the > previous state. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (METRON-1856) [UI] Implement parser grouping with drag and drop
[ https://issues.apache.org/jira/browse/METRON-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell updated METRON-1856: - Attachment: merge-and-create-new-group.gif > [UI] Implement parser grouping with drag and drop > - > > Key: METRON-1856 > URL: https://issues.apache.org/jira/browse/METRON-1856 > Project: Metron > Issue Type: New Feature >Reporter: Tibor Meller >Priority: Major > Attachments: create-parser-group.gif, delete-parser-group.gif, > merge-and-create-new-group.gif, save-parser-group.gif > > Time Spent: 1h 40m > Remaining Estimate: 0h > > The capability to group parsers via the CLI already exists in Metron, but it > currently is not possible to do so through the Management UI. This feature > seems important as it allows users to pass in groups of parsers to start, > stop, disable and enable rather than enacting the action on each individual > parser. > An initial implementation of the UI was done by Tamás Fodor, Tibor Meller and > myself (@ruffle1986, @tiborm and @sardell on GitHub, respectively), and the > REST endpoint work was performed by Ryan Merriman in PR 1396: > [https://github.com/apache/metron/pull/1396]. > Here is a brief description of the UI changes. > In order to create a parser group, simply drag and drop two parsers together. > A user can optionally update the name and add a description before creating > the group. Notice that once a group is created, the parser group is > highlighted in green and the parsers moved inside of a group are highlighted > in yellow. > !create-parser-group.gif|width=601,height=330! > Once a user has created the parser groups they want, they can simply click on > the apply button at the bottom of the screen. You'll notice the highlighting > colors go away, a success message appears and controls for all the parsers in > the group are available at the group level (in this case the start button). > !save-parser-group.gif|width=601,height=330! > If a user wants to delete a group, they can simply click on the trash can > icon in the group's controls section. We chose to keep the confirmation popup > in addition to the apply button in order to prevent accidental group > deletions and prevent sending multiple http delete calls one after the other > to the backend. If a user decides not to delete a group after confirming with > the modal window, they can click on the discard button to return to the > previous state. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (METRON-1856) [UI] Implement parser grouping with drag and drop
[ https://issues.apache.org/jira/browse/METRON-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell updated METRON-1856: - Description: The capability to group parsers via the CLI already exists in Metron, but it currently is not possible to do so through the Management UI. This feature seems important as it allows users to pass in groups of parsers to start, stop, disable and enable rather than enacting the action on each individual parser. An initial implementation of the UI was done by Tamás Fodor, Tibor Meller and myself (@ruffle1986, @tiborm and @sardell on GitHub, respectively), and the REST endpoint work was performed by Ryan Merriman in PR 1396: [https://github.com/apache/metron/pull/1396]. Here is a brief description of the UI changes. In order to create a parser group, simply drag and drop two parsers together. A user can optionally update the name and add a description before creating the group. Notice that once a group is created, the parser group is highlighted in green and the parsers moved inside of a group are highlighted in yellow. !create-parser-group.gif|width=601,height=330! Once a user has created the parser groups they want, they can simply click on the apply button at the bottom of the screen. You'll notice the highlighting colors go away, a success message appears and controls for all the parsers in the group are available at the group level (in this case the start button). !save-parser-group.gif|width=601,height=330! If a user wants to add to a group or create a new group from nested parsers, they can choose to either merge or create a new group as shown below. !merge-and-create-new-group.gif|width=601,height=330! If a user wants to delete a group, they can simply click on the trash can icon in the group's controls section. We chose to keep the confirmation popup in addition to the apply button in order to prevent accidental group deletions and prevent sending multiple http delete calls one after the other to the backend. If a user decides not to delete a group after confirming with the modal window, they can click on the discard button to return to the previous state. !delete-parser-group.gif|width=601,height=330! was: The capability to group parsers via the CLI already exists in Metron, but it currently is not possible to do so through the Management UI. This feature seems important as it allows users to pass in groups of parsers to start, stop, disable and enable rather than enacting the action on each individual parser. An initial implementation of the UI was done by Tamás Fodor, Tibor Meller and myself (@ruffle1986, @tiborm and @sardell on GitHub, respectively), and the REST endpoint work was performed by Ryan Merriman in PR 1396: [https://github.com/apache/metron/pull/1396]. Here is a brief description of the UI changes. In order to create a parser group, simply drag and drop two parsers together. A user can optionally update the name and add a description before creating the group. Notice that once a group is created, the parser group is highlighted in green and the parsers moved inside of a group are highlighted in yellow. !create-parser-group.gif|width=601,height=330! Once a user has created the parser groups they want, they can simply click on the apply button at the bottom of the screen. You'll notice the highlighting colors go away, a success message appears and controls for all the parsers in the group are available at the group level (in this case the start button). !save-parser-group.gif|width=601,height=330! If a user wants to delete a group, they can simply click on the trash can icon in the group's controls section. We chose to keep the confirmation popup in addition to the apply button in order to prevent accidental group deletions and prevent sending multiple http delete calls one after the other to the backend. If a user decides not to delete a group after confirming with the modal window, they can click on the discard button to return to the previous state. > [UI] Implement parser grouping with drag and drop > - > > Key: METRON-1856 > URL: https://issues.apache.org/jira/browse/METRON-1856 > Project: Metron > Issue Type: New Feature >Reporter: Tibor Meller >Priority: Major > Attachments: create-parser-group.gif, delete-parser-group.gif, > merge-and-create-new-group.gif, save-parser-group.gif > > Time Spent: 1h 40m > Remaining Estimate: 0h > > The capability to group parsers via the CLI already exists in Metron, but it > currently is not possible to do so through the Management UI. This feature > seems important as it allows users to pass in groups of parsers to start, > stop, disable and enable rather than enacting the action on each individual > parser. > An initial implementat
[jira] [Updated] (METRON-1856) [UI] Implement parser grouping with drag and drop
[ https://issues.apache.org/jira/browse/METRON-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell updated METRON-1856: - Description: The capability to group parsers via the CLI already exists in Metron, but it currently is not possible to do so through the Management UI. This feature seems important as it allows users to pass in groups of parsers to start, stop, disable and enable rather than enacting the action on each individual parser. An initial implementation of the UI was done by Tamás Fodor, Tibor Meller and myself (@ruffle1986, @tiborm and @sardell on GitHub, respectively), and the REST endpoint work was performed by Ryan Merriman in PR 1396: [https://github.com/apache/metron/pull/1396]. Here is a brief description of the UI changes we proposing (and subsequently implemented in PR 1360). In order to create a parser group, simply drag and drop two parsers together. A user can optionally update the name and add a description before creating the group. Notice that once a group is created, the parser group is highlighted in green and the parsers moved inside of a group are highlighted in yellow. !create-parser-group.gif|width=601,height=330! Once a user has created the parser groups they want, they can simply click on the apply button at the bottom of the screen. You'll notice the highlighting colors go away, a success message appears and controls for all the parsers in the group are available at the group level (in this case the start button). !save-parser-group.gif|width=601,height=330! If a user wants to add to a group or create a new group from nested parsers, they can choose to either merge or create a new group as shown below. !merge-and-create-new-group.gif|width=601,height=330! If a user wants to delete a group, they can simply click on the trash can icon in the group's controls section. We chose to keep the confirmation popup in addition to the apply button in order to prevent accidental group deletions and prevent sending multiple http delete calls one after the other to the backend. If a user decides not to delete a group after confirming with the modal window, they can click on the discard button to return to the previous state. !delete-parser-group.gif|width=601,height=330! was: The capability to group parsers via the CLI already exists in Metron, but it currently is not possible to do so through the Management UI. This feature seems important as it allows users to pass in groups of parsers to start, stop, disable and enable rather than enacting the action on each individual parser. An initial implementation of the UI was done by Tamás Fodor, Tibor Meller and myself (@ruffle1986, @tiborm and @sardell on GitHub, respectively), and the REST endpoint work was performed by Ryan Merriman in PR 1396: [https://github.com/apache/metron/pull/1396]. Here is a brief description of the UI changes. In order to create a parser group, simply drag and drop two parsers together. A user can optionally update the name and add a description before creating the group. Notice that once a group is created, the parser group is highlighted in green and the parsers moved inside of a group are highlighted in yellow. !create-parser-group.gif|width=601,height=330! Once a user has created the parser groups they want, they can simply click on the apply button at the bottom of the screen. You'll notice the highlighting colors go away, a success message appears and controls for all the parsers in the group are available at the group level (in this case the start button). !save-parser-group.gif|width=601,height=330! If a user wants to add to a group or create a new group from nested parsers, they can choose to either merge or create a new group as shown below. !merge-and-create-new-group.gif|width=601,height=330! If a user wants to delete a group, they can simply click on the trash can icon in the group's controls section. We chose to keep the confirmation popup in addition to the apply button in order to prevent accidental group deletions and prevent sending multiple http delete calls one after the other to the backend. If a user decides not to delete a group after confirming with the modal window, they can click on the discard button to return to the previous state. !delete-parser-group.gif|width=601,height=330! > [UI] Implement parser grouping with drag and drop > - > > Key: METRON-1856 > URL: https://issues.apache.org/jira/browse/METRON-1856 > Project: Metron > Issue Type: New Feature >Reporter: Tibor Meller >Priority: Major > Attachments: create-parser-group.gif, delete-parser-group.gif, > merge-and-create-new-group.gif, save-parser-group.gif > > Time Spent: 1h 40m > Remaining Estimate: 0h > > The capability to group parsers via the C
[jira] [Created] (METRON-2108) Add Drag and Drop Capability to Parsers
Shane Ardell created METRON-2108: Summary: Add Drag and Drop Capability to Parsers Key: METRON-2108 URL: https://issues.apache.org/jira/browse/METRON-2108 Project: Metron Issue Type: Sub-task Reporter: Shane Ardell A user should have the capability to drag a parser onto another parser and create a group from the two parsers. There should be some sort of anchor for the user to use for drag and drop so they can still click on the parser elsewhere to open the details panel. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-2110) Setup Parser Grouping Service with Mock Backend
Shane Ardell created METRON-2110: Summary: Setup Parser Grouping Service with Mock Backend Key: METRON-2110 URL: https://issues.apache.org/jira/browse/METRON-2110 Project: Metron Issue Type: Sub-task Reporter: Shane Ardell In order to communicate with REST services, we need to setup a service in Angular to make calls. However, since the endpoints won't be exposed until after we are done developing the UI, we must make calls to a mock backend. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (METRON-2124) [UI] Move status information and start/stop to the Aggregate level
Shane Ardell created METRON-2124: Summary: [UI] Move status information and start/stop to the Aggregate level Key: METRON-2124 URL: https://issues.apache.org/jira/browse/METRON-2124 Project: Metron Issue Type: Sub-task Reporter: Shane Ardell When parsers are grouped, we want to be able to start/stop from the aggregate level. This means hiding individual parser controls when they are grouped, controlling multiple parsers with a single set of controls for a group, and displaying status information as a group. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (METRON-2124) [UI] Move status information and start/stop to the Aggregate level
[ https://issues.apache.org/jira/browse/METRON-2124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Ardell reassigned METRON-2124: Assignee: Shane Ardell > [UI] Move status information and start/stop to the Aggregate level > -- > > Key: METRON-2124 > URL: https://issues.apache.org/jira/browse/METRON-2124 > Project: Metron > Issue Type: Sub-task >Reporter: Shane Ardell >Assignee: Shane Ardell >Priority: Major > > When parsers are grouped, we want to be able to start/stop from the aggregate > level. This means hiding individual parser controls when they are grouped, > controlling multiple parsers with a single set of controls for a group, and > displaying status information as a group. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
