Sure ! and thanks for your feedback !
Do you mind to create a corresponding Jira and assign to me ? Else I
will later today.
Regards
JB
On 08/07/2019 16:20, Markus Rathgeb wrote:
> Hi JB,
>
> sounds good.
> Thank you.
>
> Can you keep me informed?
>
> Would it make sense (e.g. for log alert
Hi Markus,
Correct, but you raised a valid point. Let me do the improvements on the
checker, adding an option to "always" send the alert, ignoring previous
ones.
I imagine something like:
log.level.warn.always=
I do the change for Decanter 2.3.0 and I will cut the release asap.
OK for you
Here it is: https://issues.apache.org/jira/browse/KARAF-6355
I did not find how to change the "assign to" field.
Perhaps I don't have the power.
I don't know which title would be a good one - feel free to change it.
Am Mo., 8. Juli 2019 um 16:25 Uhr schrieb Jean-Baptiste Onofré
:
>
> Sure ! and
Hi JB,
sounds good.
Thank you.
Can you keep me informed?
Would it make sense (e.g. for log alert usage) to enhance the checker
configuration also for multiple matches (excludes)?
E.g. type log,
* property level should match WARN
AND
* property message should not contain the regex foobar (or
Great, thanks !
Regards
JB
On 08/07/2019 16:40, Markus Rathgeb wrote:
> Here it is: https://issues.apache.org/jira/browse/KARAF-6355
>
> I did not find how to change the "assign to" field.
> Perhaps I don't have the power.
>
> I don't know which title would be a good one - feel free to change
I have a bundle with a blueprint.xml file that contains
managed-service-factory elements. Inside my java class that is implementing
the managed-service-factory (the "client") I would like to access a service
that is defined inside a different bundle (the "server").
The blueprint.xml for the
Hi,
I would like to setup a Karaf based system to send mails for log
messages of priority WARN and ERROR.
I read some of the "Apache Karaf Decanter 2.x" documentation.
$ tar xzf apache-karaf-4.2.6.tar.gz
$ cd apache-karaf-4.2.6/
$ bin/karaf
karaf@root()> feature:repo-add
After reading the code of
org.apache.karaf.decanter.alerting.checker.Checker I realized that the
checker configuration needs to be equal to:
===
log.level.error=match:ERROR
log.level.warn=match:WARN
===
Am Mo., 8. Juli 2019 um 14:10 Uhr schrieb Jean-Baptiste Onofré
:
>
> Let me try to reproduce
Hi Markus,
can you send the karaf.log to me ?
Maybe issue in the SMTP config ?
Regards
JB
On 08/07/2019 13:51, Markus Rathgeb wrote:
> Hi,
>
> I would like to setup a Karaf based system to send mails for log
> messages of priority WARN and ERROR.
>
> I read some of the "Apache Karaf Decanter
Let me try to reproduce on my machine. Give me couple of hours, I will
get back to you.
Regards
JB
On 08/07/2019 13:51, Markus Rathgeb wrote:
> Hi,
>
> I would like to setup a Karaf based system to send mails for log
> messages of priority WARN and ERROR.
>
> I read some of the "Apache Karaf
Yes, if the event property is log.level (you can find it in Kibana for
instance). I think it's actually log.level with Log4j2 (loggerLevel is
with Log4j1 afair).
Does it work like this ?
Regards
JB
On 08/07/2019 14:21, Markus Rathgeb wrote:
> After reading the code of
>
The mails content does not seem to be fully correct.
There is e.g. a mail with subject: Alert on level back to normal
and body:
===
warn alert: level was out of the pattern match:WARN, but back to normal now
Details:
hostName: pc05
alertPattern: match:WARN
component.name:
Hi Markus,
you can see the alert using decanter:alert command.
In the case of log, it's a bit special: you receive an alert as soon as
you have a log.level in WARN, and it's stored in the Decanter alerts.
Then, the next log message which is not a WARN will notify you.
I need to improve a bit
> In the case of log, it's a bit special: you receive an alert as soon as
> you have a log.level in WARN, and it's stored in the Decanter alerts.
> Then, the next log message which is not a WARN will notify you.
>
> I need to improve a bit the mail alerter to only send the first email in
> the
14 matches
Mail list logo
