Hello, I searched the entire internet and I could not find anything close to what I'd like to achieve so I will propose it here.
If this is already an existing feature, please let me know how I might be able to achieve this
I propose a way to display trigger counts and last occurrence in the problem widget in 2 additional columns
I put together a small example of what I mean:
This can be useful for the following reason: We want to be notified that something is wrong but we don't want to be notified every single time it happens but only the first time. So naturally we want to use single event generation.
However, when we wade through the list of problems, we want to see how many times this issue happened and when the last time is.
This usually applies to log file monitoring. We want to be notified when a specific error is logged as soon as it happens but having a count and last occurrence date helps us:
1. Count sort of helps us gauge the seriousness of the issue
2. Last updated date helps us see if this is still happening (without having to close the issue).
Now I could use multiple problem generation and that would indeed give me a count and a trail of events, but:
1. It would litter the problem list unnecessarily
2. It would alert on all instances or none
Maybe this sounds like a weird use case but we had this feature with Zenoss' event console and it is extremely useful
Let me know if anyone else finds this feature useful
If this is already an existing feature, please let me know how I might be able to achieve this
I propose a way to display trigger counts and last occurrence in the problem widget in 2 additional columns
I put together a small example of what I mean:
This can be useful for the following reason: We want to be notified that something is wrong but we don't want to be notified every single time it happens but only the first time. So naturally we want to use single event generation.
However, when we wade through the list of problems, we want to see how many times this issue happened and when the last time is.
This usually applies to log file monitoring. We want to be notified when a specific error is logged as soon as it happens but having a count and last occurrence date helps us:
1. Count sort of helps us gauge the seriousness of the issue
2. Last updated date helps us see if this is still happening (without having to close the issue).
Now I could use multiple problem generation and that would indeed give me a count and a trail of events, but:
1. It would litter the problem list unnecessarily
2. It would alert on all instances or none
Maybe this sounds like a weird use case but we had this feature with Zenoss' event console and it is extremely useful
Let me know if anyone else finds this feature useful
Comment