Alerting

How to send alert once if message doesn't change?

Julia1231
Communicator

Hi,

I am doing the sending alert if a machine has no activity in the span = 1h.

I configure to send it each hour. The thing is if the machine has no activity at 7:00, it will send the alert every hour (7h, 8h, 9h, etc) saying the same message that the machine has no activity at 7:00

Is anyway to send it once if the message is always the same (in this case, machine has no activity at 7:00).

If the machine is restarted, it has activities from 10:00 - 15:00, then it downs, I will receive an alert saying that machine has no activity at 15:00)

 

Thanks in advanced.

Labels (3)
0 Karma

gcusello
Esteemed Legend

Hi @Julia1231,

did you tried to configure throttling for your alert?

You can do this in the alert definition page.

Ciao.

Giuseppe

0 Karma

Julia1231
Communicator

@gcusello This is my configuration:

Sorry it's in french but the function is same as in english. Do you find where I can do it please?

Julia1231_0-1669114910106.png

 

0 Karma

gcusello
Esteemed Legend

Hi @Julia1231,

you have to flag "Throttle" and define a time period that the alert will not be fired.

Only for the next time if you go in the address bar of your browser, replace "fr-FR" with "en-US", you'll have the dashboard in english, I'm italian and I usually have the same problem.

ciao.

Giuseppe

0 Karma

Julia1231
Communicator

@gcusello thank you. 

So what I understand, because the Throttle goes with the Suppress triggering for (time), I can only suppress for the period that I define here.

For example if I put the suppress triggering for 3 hours, I will always receive the same email each 3h? It can reduce the number of duplicate email sent but cannot avoid, is it true?
And even if my machine is restarted, it has activity again, there is always the alert sent for inform a fault in the pass. 

Thanks,

Julia

0 Karma

gcusello
Esteemed Legend

Hi @Julia1231,

my hint is to analyze throttle feature to use it at the best.

Otherwise a much more complicated workaround is to to write all your alerts in a summary index (as e.g. ES does) and then use this summary index to exclude the triggered alerts from results, but, as I said, it isn't so immediate to realize.

Ciao.

Giuseppe

0 Karma
Get Updates on the Splunk Community!

Don't wait! Accept the Mission Possible: Splunk Adoption Challenge Now and Win ...

Attention everyone! We have exciting news to share! We are recruiting new members for the Mission Possible: ...

Unify Your SecOps with Splunk Mission Control

In today’s post, I'm excited to share some recent Splunk Mission Control innovations. With Splunk Mission ...

Data Preparation Made Easy: SPL2 for Edge Processor

By now, you may have heard the exciting news that Edge Processor, the easy-to-use Splunk data preparation tool ...