[
https://issues.apache.org/jira/browse/KARAF-5792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16604094#comment-16604094
]
Jean-Baptiste Onofré commented on KARAF-5792:
---------------------------------------------
Actually, this change should be done across all collectors. I will create a
collector {{util}} module (as a jar) that will be embedded in all collectors
and doing the cleanup/population/handling of the properties before sending to
the dispatcher.
> Support add, rename, remove to the custom fields of Decanter collectors
> -----------------------------------------------------------------------
>
> Key: KARAF-5792
> URL: https://issues.apache.org/jira/browse/KARAF-5792
> Project: Karaf
> Issue Type: Improvement
> Components: decanter
> Affects Versions: decanter-2.0.0
> Reporter: Xilai Dai
> Assignee: Jean-Baptiste Onofré
> Priority: Major
> Fix For: decanter-2.1.0
>
>
> Now user can only "add" some custom fields with constant value in the
> org.apache.karaf.decanter.collector.log.cfg.
> {code}
> key1=value1
> key2=value2
> {code}
> But there is no chance to "rename" or "remove" some of the generated fields
> from the log collector, or add dynamic value e.g. UUID, Timestamp to the
> field.
> It would be benifit for user if the custom fields impl get improved in the
> log collector of Decanter. Configuration like this:
> {code}
> # custom fields
> fields.add.eventType=LOGEvent
> fields.add.eventUUID=UUID
> fields.add.serverTimestamp=TIMESTAMP
> fields.rename.MDC=customInfo
> fields.rename.level=severity
> fields.rename.renderedMessage=logMessage
> fields.remove.timestamp=true
> {code}
> Then it provides ability to "transformer" the json data on collector level,
> which will reduce the overhead user has to "transformer" the data later
> (using Filebeat or custom transformer bundle)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
