It is ok save signals using milliseconds in a custom monitor? #481
Replies: 1 comment
-
|
Ok, Just found that it will break at least the alerting system. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi @rajnandan1,
I'm working on a couple of additional monitors that I'd like to contribute once they're completed. One of them, called Pushback, tracks the number of events received between executions and checks if it falls within an expected count range.
During implementation, I noticed that timestamps in the
monitor_datatable are rounded to seconds (or sometimes truncated to the start of the minute). For my use case, I need to store the timestamp in milliseconds (for signals only), as multiple events may be received simultaneously.Do you think storing these signals as milliseconds would be acceptable, or could it cause issues in Kener?
Beta Was this translation helpful? Give feedback.
All reactions