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
Is your feature request related to a problem? Please describe.
Currently most monitoring message processing happens in the monitoring database process. There's a monitoring router process, but the functionality it has now is to receive messages on what I'd now phrase radio receivers: one ZMQ, one UDP.
Prototype #3315 is moving towards different radio methods being configurable, at least on the sending side, and it makes sense as part of that to split UDP and ZMQ receiving, and make at least the UDP loop optional.
The main loop of the monitoring router could probably be made less awkwardly polling of both protocols if it was implemented as two separately executing loops, one per protocol, as happens with the existing filesystem radio receiver.
Additional context
There is increasing desire to hook into monitoring messages in different ways: none of the existing ways are perfect and so this area is ripe for research.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Currently most monitoring message processing happens in the monitoring database process. There's a monitoring router process, but the functionality it has now is to receive messages on what I'd now phrase radio receivers: one ZMQ, one UDP.
Prototype #3315 is moving towards different radio methods being configurable, at least on the sending side, and it makes sense as part of that to split UDP and ZMQ receiving, and make at least the UDP loop optional.
The main loop of the monitoring router could probably be made less awkwardly polling of both protocols if it was implemented as two separately executing loops, one per protocol, as happens with the existing filesystem radio receiver.
Additional context
There is increasing desire to hook into monitoring messages in different ways: none of the existing ways are perfect and so this area is ripe for research.
The text was updated successfully, but these errors were encountered: