You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2019/07/08 14:44:00 UTC

[jira] [Assigned] (KARAF-6355) improve usage for "log collector" + "mail alerter" usecases

     [ https://issues.apache.org/jira/browse/KARAF-6355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Baptiste Onofré reassigned KARAF-6355:
-------------------------------------------

    Assignee: Jean-Baptiste Onofré

> improve usage for "log collector" + "mail alerter" usecases
> -----------------------------------------------------------
>
>                 Key: KARAF-6355
>                 URL: https://issues.apache.org/jira/browse/KARAF-6355
>             Project: Karaf
>          Issue Type: Bug
>          Components: decanter
>    Affects Versions: decanter-2.2.0
>            Reporter: Markus Rathgeb
>            Assignee: Jean-Baptiste Onofré
>            Priority: Major
>
> If you would like to be informed per mail about special log events (e.g. log level warn) the current implementation does not work as (perhaps) expected.
> Assume you would like to be informed about every log message of level WARN.
> The current implementation will notify you about the first log message of level WARN and the next alert that is triggered is for a log message not using the WARN level.
> I would like to be informed about every WARN log message and not about any other (so not loosing multiple WARN messages that are followed immediately and not informed about a log message that is not WARN).
> Another improvement would about the combination of multiple patterns.
> E.g. keep me informed about
> type = log
> priority = WARN | ERROR
> not ( loc.class = Foo.class & loc.method = magic)
>  
> Perhaps we could reuse [https://osgi.org/javadoc/r2/org/osgi/framework/Filter.html]
> log.warn.filter = "(&((|(priority=WARN)(priority=ERROR))(loc.class=Foo.class)(loc.method=magic)))"
> (do not assume the filter above is correct)
>  
> Perhaps we could already reuse the current implementation and its match method.
> Just need to think about substring matching...



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