We've noticed the out of the box event source 'Liebert_Condition_Events' is triggering alarm where the actual date of the event is in the future (example below):
NOTE: Blurred the device name (in order to protect our client information)
I've already accessed the device in question & the system time is correct.
Could this be an issue with the data source 'timestamp' handling? Or there's another thing that I might be missing?
Question
Vitor Santos 71
Hello,
We've noticed the out of the box event source 'Liebert_Condition_Events' is triggering alarm where the actual date of the event is in the future (example below):
NOTE: Blurred the device name (in order to protect our client information)
I've already accessed the device in question & the system time is correct.
Could this be an issue with the data source 'timestamp' handling? Or there's another thing that I might be missing?
Thank you!
Link to post
Share on other sites
3 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.