We have recently rolled out a new detection engine for the Anodot revenue product. While most of the improvements are around stability, performance and supportability, there are some implication which you as a customer should be aware of.
In the past new months we ran extensive testing of the new infrastructure. Both existing and new infrastructure ran in parallel during this time and we compared the results to make sure we have parity.
What should you expect?
During the transition
We will be doing the transition behind the scenes and it should be transparent to you. This means the following:
- Links from old triggers will work as usual
- Old feedbacks and 'Acks' will be applied to the new alert triggers
- Old triggers will be presented in the new console and will have the TTL they originally had (per rollup)
After the transition
- We added pagination to the alert console - No need to filter and sort the triggers to see them all
- Easier tracking of triggers over anomaly mergers - The ID used in the opening trigger will be the one used throughout the trigger’s lifespan
- Easier tracking and managing of triggers in the alert console
- Trigger title
- When using variables, we keep showing the text of the opening trigger, so you can search for it.
- The trigger updates will link to the same line, without changing the presented title.
- Trigger Impact
- The impact factor value is stamped by the opening trigger
- The overall impact is cumulative throughout the trigger’s metrics.
- Number of metrics in the trigger
- Shows the total metrics of this trigger since it started
- Even when the filtering shows a partial list, the overall number is presented
- Trigger title
- Easier filtering of triggers - The filters work top-bottom, meaning the trigger is first checked, and only then the metrics included within it.
