[
https://issues.apache.org/jira/browse/METRON-1337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16370403#comment-16370403
]
ASF GitHub Bot commented on METRON-1337:
----------------------------------------
Github user merrimanr commented on the issue:
https://github.com/apache/metron/pull/853
I took @ottobackwards's suggestion and added a "type" parameter that can be
used to independently manage user settings for different types of clients. I
moved the users settings for the Alerts UI (the original intention of this PR)
back to the AlertController. I also went ahead and moved the low level client
code to the metron-hbase module so that this user settings abstraction can be
used anywhere in Metron. For examples of how to setup and use the client see
HBaseConfig and AlertServiceImpl in the metron-rest module.
Testing in full dev is slightly different now. Instead of the endpoints
being in the UserController they should now be tested in the AlertController.
The Alerts UI should also be tested. Navigate to the Alerts UI and you should
see the default facets on the left. Update the "facetFields" user setting with
Swagger and the new list should appear in the Alerts UI after refreshing. For
example, if you set facetFields = ip_src_addr, only that facet field should
appear in the Alerts UI.
> List of facets should not be hardcoded
> --------------------------------------
>
> Key: METRON-1337
> URL: https://issues.apache.org/jira/browse/METRON-1337
> Project: Metron
> Issue Type: Bug
> Reporter: Ryan Merriman
> Assignee: Ryan Merriman
> Priority: Major
>
> Currently the facet fields shown in the left panel of the Alerts UI is hard
> coded in a javascript file. This should be configurable.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
