Settings and activity
17 results found
-
3 votesNikola Keskinov supported this idea ·
-
2 votesNikola Keskinov supported this idea ·
-
3 votes
An error occurred while saving the comment Nikola Keskinov supported this idea · -
7 votesNikola Keskinov supported this idea ·
-
3 votesNikola Keskinov supported this idea ·
-
7 votesNikola Keskinov supported this idea ·
-
8 votesNikola Keskinov supported this idea ·
-
3 votesNikola Keskinov supported this idea ·
-
5 votes
An error occurred while saving the comment Nikola Keskinov commentedAs an additional idea to treat the customer request to restrict the visibility of the banner (see previous comment / merged idea), we could also consider showing it only to Admin and Finance User roles + all DoiT users.
For customers that make a sensible use of our IAM, this potentially easy fix would largely resolve the issue, while all the more relevant stakeholders would still get the alert all the same.
Nikola Keskinov shared this idea · -
8 votesNikola Keskinov supported this idea ·
-
6 votesNikola Keskinov supported this idea ·
-
10 votesNikola Keskinov supported this idea ·
-
2 votesNikola Keskinov shared this idea ·
-
4 votesNikola Keskinov supported this idea ·
-
11 votesNikola Keskinov supported this idea ·
-
8 votesNikola Keskinov supported this idea ·
-
4 votesNikola Keskinov supported this idea ·
One addition that could even potentially simplify the implementation. Instead of trying to implicitly deduct if the customer found the anomaly too low for the threshold they have in mind for what an anomaly means, we could also add an option in the anomaly acknowledgment that says something along "The spike is too low to be considered an anomaly". This would be the exact use case for applying anomaly thresholds.