You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Publish point values (same as COV event) for all points periodically
May not be needed. Discussion required
Nice to have so everything stays up to date...
MQTT by default will retain the latest value for every topic and send this on ANY connection reset meaning periodic publishing could prevent us from finding any bugs in any of the services
Need way to tell if services go down / haven't received update for long time
Periodic pushes might prevent this from being detectable depending on how it's implemented
global service level would not allow for detection
source_driver level would allow for detection (EventServiceBase._internal_timeout_thread will need tweaking for multiple timeouts. i.e. normal poll loop and point re-publish loop)
i.e. driver publishes points on a loop for example 60 point = 1 hour loop = 1 point every minute
This will create unnecessary histories unless unless handled for (might be hacking and over complicated to handle)
REST endpoint might be better way to detect service status
This discussion was converted from issue #118 on February 02, 2021 21:33.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Publish point values (same as COV event) for all points periodically
May not be needed. Discussion required
Nice to have so everything stays up to date...
Need way to tell if services go down / haven't received update for long time
global service level would not allow for detection
source_driver level would allow for detection (
EventServiceBase._internal_timeout_thread
will need tweaking for multiple timeouts. i.e. normal poll loop and point re-publish loop)This will create unnecessary histories unless unless handled for (might be hacking and over complicated to handle)
Beta Was this translation helpful? Give feedback.
All reactions