How is the ResetTimeStamp field in the AlertStatus table used? It seems like most of the entries in the table have the value of '12/30/1899 12:00:00 AM' and I'm not sure what the purpose of such would be.
Thanks
I'd love to know this as well as how the "alert was re-activated" piece works.
The ResetTimeStamp is set to the current time when the reset condition is met for the alert. This time is set when an alert is in state = 2 (triggered) and is moving to state 4(reset) or is in state 3(reset but waiting for time duration) and moving to state 4.
This lets a user know when their reset condition was met. Not sure if we expose that anywhere in the UI by default, but should be available in reports.
@njoylif -- I think the answer is this... - Alerts are reactivated if they transition from triggered to reset and then back to triggered - for example your CPU goes above 80, then drops below and back above while the alert record still exists in the AlertStatus table. Trying to see if I can validate. Where are you seeing the message "alert was re-activated"?
Thanks for info. I see that in notes - mostly tying in with AlertCentral. created custom alerts view so see it there also:
Thank you for the reply. I am working to create custom alerts for selected traps. I can create the alerts, but they keep disappearing. I'm not sure if it is due to reset actions, orphan cleanup or something else. So I'm trying to work my way through the process.
good question. probably like "windows event" alerts. triggers for a cycle and goes away. Please post what you find.
Thx!
If you're talking about a Custom SQL alert, then the default reset query usually doesn't work. You need to custom write the reset query as well. An alert will trigger and then reset in the same second, as the logic triggers and resets within the same checking process.
Give some more detail about what exactly you're doing and we can go through some recommendations. If you're writing an alert on a trap and looking at the timestamp/datetime then you might be hitting the reset because the trap slips out of your time window.
More info on what I'm trying to do:
Upon receipt of selected traps, it sends the var bind data to a perl script. The script uses that info to construct an alert for insertion into the alertstatus table. Subsequent traps received just increment the triggercount and the lastupdate timestamp. That works OK. But the alert disppears within 5 or 6 minutes. I've been experimenting with the resettimestamp to see if that might be what is causing the disappearance. Anyway, the customer has requested that the alert remain open for six hours from the last receipt of the trap. I can delete the alert, but would like to use the reset, but have been unable to figure out the states and timing. Any explanations of the alert process would be greatly appreciated.
Thank you
