[ 
https://issues.apache.org/jira/browse/METRON-1599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16506514#comment-16506514
 ] 

ASF GitHub Bot commented on METRON-1599:
----------------------------------------

Github user merrimanr commented on a diff in the pull request:

    https://github.com/apache/metron/pull/1047#discussion_r194168449
  
    --- Diff: 
metron-deployment/packaging/ambari/metron-mpack/src/main/resources/common-services/METRON/CURRENT/configuration/metron-env.xml
 ---
    @@ -137,4 +137,10 @@
             <value>yyyy.MM.dd.HH</value>
             <display-name>Elasticsearch Date Format</display-name>
         </property>
    +    <property>
    --- End diff --
    
    Do you think It might be more appropriate to have this property in 
metron-rest-env instead?  Now when I change it I'm prompted to restart all 
Metron components when really the only one that needs to be restarted is REST 
and the UIs.  Both UIs depend on REST so they will also be included in the 
restart list.


> Allow user to define global property 'source.type.field' in Ambari 
> -------------------------------------------------------------------
>
>                 Key: METRON-1599
>                 URL: https://issues.apache.org/jira/browse/METRON-1599
>             Project: Metron
>          Issue Type: Improvement
>            Reporter: Nick Allen
>            Assignee: Nick Allen
>            Priority: Major
>
> The user can specify the name of the message field containing the source type 
> in the global configuration.  This is used by the Alerts UI.
> Currently this necessitates a user using the CLI to add the field. This 
> property should be exposed to the user via Ambari.  The user should be able 
> to define this property directly in Ambari.



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

Reply via email to