Hi all,
Is anyone able to explain why historical alarms count is showing non-zero number of alarms while the same applied filter returns zero alarms?
Alija Kusur [SLC] [DevOps Advocate] Selected answer as best 5 hours ago
Sometimes it is not possible to put the complete filter in the query towards the database, and then client-side filtering is still being applied afterwards. The tooltip indicates how many alarms will need to be downloaded, and then it is possible there is some additional filtering client-side. This way it is possible zero alarms are left to show to you...
Alija Kusur [SLC] [DevOps Advocate] Selected answer as best 5 hours ago

Thanks for the explanation. I now understand why I might be getting zero alarms, but I still find it confusing that count is not aligned with the number of fetched alarms. I believe there is a room to improve this, either by counting alarms client-side (that would most likely lead to the same processing times for both, count and show actions), or by adding the button tooltip explanations.