There is currently a PR up for review that allows a user to configure and save the list of facet fields that appear in the left column of the Alerts UI: https://github.com/apache/metron/pull/853. The REST layer has ORM support which means we can store those in a relational database.
However I'm not 100% sure this is the best place to keep this. As we add more use cases like this the backing tables in the RDBMS will need to be managed. This could make upgrading more tedious and error-prone. Is there are a better way to store this, assuming we can leverage a component that's already included in our stack? Ryan
