GitHub user iraghumitra opened a pull request:
https://github.com/apache/metron/pull/768
Metron 1123: Add group by option using faceted search capabilities of
metron-rest-api
## Contributor Comments
This PR extends the Metron Alerts GUI capabilities to do group by on Alerts
Data
The PR is on top of METRON-1189
The group by buttons appear on top of the table. When user selects a group,
the table view changes to a tree view with the values of the groups as the root
of the tree. The individual alerts would be shown as the leaf nodes of the tree.
Tree view has all the following features
- Search will search through all the groups
- Users can click on the data inside the table to search
- Users can select and table inside tree to view the details
- Users can escalate the alerts from the table inside the tree
- Tree view is refreshed automatically depending on the polling setting in
the settings
- A cumulative score and number of alerts in a group is shown next to
group name
- Table inside a group can be paginated
- The column names for the alerts table in the tree can be configured via
configure column pane
The table config settings is moved next to settings on the GUI as it makes
more meaning there.
## Testing
E2E test cases are available to test groups functionality. From root of the
project
```
cd metron-interface/metron-alerts
sh ./scripts/start-server-for-e2e.sh
```
In othere shell run the test cases
```
npm run e2e
```
All the features listed in contributor comments can be verified manually
## Pull Request Checklist
Thank you for submitting a contribution to Apache Metron.
Please refer to our [Development
Guidelines](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61332235)
for the complete guide to follow for contributions.
Please refer also to our [Build Verification
Guidelines](https://cwiki.apache.org/confluence/display/METRON/Verifying+Builds?show-miniview)
for complete smoke testing guides.
In order to streamline the review of the contribution we ask you follow
these guidelines and ask you to double check the following:
### For all changes:
- [x] Is there a JIRA ticket associated with this PR? If not one needs to
be created at [Metron
Jira](https://issues.apache.org/jira/browse/METRON/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel).
- [x] Does your PR title start with METRON-XXXX where XXXX is the JIRA
number you are trying to resolve? Pay particular attention to the hyphen "-"
character.
- [x] Has your PR been rebased against the latest commit within the target
branch (typically master)?
### For code changes:
- [x] Have you included steps to reproduce the behavior or problem that is
being changed or addressed?
- [x] Have you included steps or a guide to how the change may be verified
and tested manually?
- [x] Have you ensured that the full suite of tests and checks have been
executed in the root metron folder via:
```
mvn -q clean integration-test install && build_utils/verify_licenses.sh
```
- [x] Have you written or updated unit tests and or integration tests to
verify your changes?
- [x] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [x] Have you verified the basic functionality of the build by building
and running locally with Vagrant full-dev environment or the equivalent?
### For documentation related changes:
- [x] Have you ensured that format looks appropriate for the output in
which it is rendered by building and verifying the site-book? If not then run
the following commands and the verify changes via
`site-book/target/site/index.html`:
```
cd site-book
mvn site
```
#### Note:
Please ensure that once the PR is submitted, you check travis-ci for build
issues and submit an update to your PR as soon as possible.
It is also recommended that [travis-ci](https://travis-ci.org) is set up
for your personal repository such that your branches are built there before
submitting a pull request.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/iraghumitra/incubator-metron METRON-1123
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/metron/pull/768.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #768
----
commit b89d2e4698b5fd32a85e078b55718682f02ac161
Author: iraghumitra <[email protected]>
Date: 2017-09-19T09:43:13Z
Initial check-in for alerts grouping
commit 60b979427ba76af3c664f42b9f94e021ff4b715d
Author: iraghumitra <[email protected]>
Date: 2017-09-20T13:24:49Z
e2e tests for groups and suport for escalation action in tree view
----
---
