Indicators: AlertKit, one alert per event and bar, no alert spam

[Automated-Trading]

AlertKit, one alert per event and bar, no alert spam:

A small include class that stops indicator alerts from firing on every tick. One alert per event and bar, silent about history on start, popup, push, email or sound, and an optional log of every decision. Comes with a working range break indicator as an example

Author: Mykyta Samoiliuk

[Vira Ohloblia]

The decision log is the best part. Alerts don't fire in the tester, so a CSV of sent / duplicate / history / cooldown is pretty much the only way to check alert logic before going live. Found one thing in Fire(): cooldown uses a single m_last_sent for all keys. So with Cooldown() set, a break_up alert blocks a break_down that comes a few seconds later. That goes against "a buy alert never blocks a sell alert" from the description. Last-sent time per key would fix it.

[Mykyta Samoiliuk]

Vira Ohloblia #:
The decision log is the best part. Alerts don't fire in the tester, so a CSV of sent / duplicate / history / cooldown is pretty much the only way to check alert logic before going live. Found one thing in Fire(): cooldown uses a single m_last_sent for all keys. So with Cooldown() set, a break_up alert blocks a break_down that comes a few seconds later. That goes against "a buy alert never blocks a sell alert" from the description. Last-sent time per key would fix it.

Thank you, you’re right. The cooldown was a single timestamp for the whole module, so with Cooldown() on, a break_up alert could hold back a break_down a few seconds later, which contradicts the description. Version 1.02 keeps the last sent time per key, the same way the bar memory already works, and the log note now says “too soon after the previous alert of this event”. Thanks for reading the code that closely