[
https://issues.apache.org/jira/browse/METRON-1599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16515925#comment-16515925
]
ASF GitHub Bot commented on METRON-1599:
----------------------------------------
Github user nickwallen commented on a diff in the pull request:
https://github.com/apache/metron/pull/1047#discussion_r196130319
--- 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>
+ <name>source_type_field</name>
+ <display-name>Source Type Field</display-name>
+ <description>Name of the message field that contains the source
type.</description>
+ <value>source.type</value>
--- End diff --
I might also update this so the field only shows up under the "Advanced"
settings, since it is not something we expect the user to have to, nor want to
change in most cases. I *think* I can do that easily.
> 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)
