Visor cmd alerts

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Visor cmd alerts

Vasiliy Sisko
Hello.

I started work on issue "Visor CMD: Add ability to attach custom scripts to
alerts" https://issues.apache.org/jira/browse/IGNITE-29
<https://issues.apache.org/jira/browse/IGNITE-2856>19
and plan to add parameter -s=”script path” to configure path of script to
execute on generation of alert.

I notice that default frequency of alert generation is 15 min. I think that
time period is very large and suggest to change it to 1 min.

Also I faced with choice of alert generation frequency and suggest three
variants:
1. Execute script only once on first generation of alert.
2. Execute script after some cooldown period  from previous execution (f.e.
after 5 min from).
3. Execute script after specified count of alert generations from previous
execution (f.e every second or third or ...).

--
Vasiliy Sisko
GridGain Systems
www.gridgain.com
Reply | Threaded
Open this post in threaded view
|

Re: Visor cmd alerts

Denis Magda
Hi Vasiliy,

After a script is executed on the first alert I would follow these steps
to manage the frequency:
- execute the script only after alert's condition goes below set
watermark and then hits the watermark again.
- if the condition is fluctuating (goes up and down over the watermark)
too frequent (couple of times in 2 or so minutes) then I would avoid
calling the script to reduce possible spam generation.

--
Denis

On 4/4/2016 4:40 PM, Vasiliy Sisko wrote:

> Hello.
>
> I started work on issue "Visor CMD: Add ability to attach custom scripts to
> alerts" https://issues.apache.org/jira/browse/IGNITE-29
> <https://issues.apache.org/jira/browse/IGNITE-2856>19
> and plan to add parameter -s=”script path” to configure path of script to
> execute on generation of alert.
>
> I notice that default frequency of alert generation is 15 min. I think that
> time period is very large and suggest to change it to 1 min.
>
> Also I faced with choice of alert generation frequency and suggest three
> variants:
> 1. Execute script only once on first generation of alert.
> 2. Execute script after some cooldown period  from previous execution (f.e.
> after 5 min from).
> 3. Execute script after specified count of alert generations from previous
> execution (f.e every second or third or ...).
>