[
https://issues.apache.org/jira/browse/KARAF-4645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Achim Finke updated KARAF-4645:
-------------------------------
Description:
Currently alerters are not throtteble. Thats especially an issue when using
ranges. Imagine you have a memory leak in your application and defined a heap
sla checker. You will detect your memory leak soon but get spammed with alerts
because the alerter is depending on your scheduler period what results in one
alert every five seconds when using the default configuration.
I would like to configure a throttle period within the alerter which will send
a recurrent alert just once within the defined throttle period.
was:
Currently alerters are not throtteble. Thats especially an issue when using
ranges. Imagine you have a memory leak in your application and defined a heap
sla checker. You will detect your memory leak soon but get spammed with alerts
because the alerter is depending on your scheduler period what results in one
alert every five seconds when using the default configuration.
I would like to configure a throttle period within the alerter which will send
a recurrent event just once within the defined throttle period.
> Alerters should be throtteble
> -----------------------------
>
> Key: KARAF-4645
> URL: https://issues.apache.org/jira/browse/KARAF-4645
> Project: Karaf
> Issue Type: Improvement
> Components: decanter
> Affects Versions: decanter-1.1.0
> Reporter: Achim Finke
>
> Currently alerters are not throtteble. Thats especially an issue when using
> ranges. Imagine you have a memory leak in your application and defined a heap
> sla checker. You will detect your memory leak soon but get spammed with
> alerts because the alerter is depending on your scheduler period what results
> in one alert every five seconds when using the default configuration.
> I would like to configure a throttle period within the alerter which will
> send a recurrent alert just once within the defined throttle period.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)