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
It would be great if we had an online way of distributing metrics related to a run at runtime (ie without needing further data processing). The suggested solution is two parts:
Modify message_relayer, adding a method for sending a data log broadcast message. This is then available to any nodes that have useful metrics which we want to log... should be a relatively simple extension of the existing slack message methods.
Modify the event_builder to count triggers:
upon receiving a midge:s_start, reset the internal trigger counter to 0
upon receiving a midge:s_stop, use the above to broadcast the current trigger count
whenever the internal state is changed to triggered, also ++ the trigger counter
add whatever configuration is required for using the above broadcast: want options for disabling and probably an option for specifying the routing key target used.
The text was updated successfully, but these errors were encountered:
It would be great if we had an online way of distributing metrics related to a run at runtime (ie without needing further data processing). The suggested solution is two parts:
Modify
message_relayer
, adding a method for sending a data log broadcast message. This is then available to any nodes that have useful metrics which we want to log... should be a relatively simple extension of the existing slack message methods.Modify the
event_builder
to count triggers:midge:s_start
, reset the internal trigger counter to 0midge:s_stop
, use the above to broadcast the current trigger count++
the trigger counterThe text was updated successfully, but these errors were encountered: