Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dripline reporting of run metrics #109

Open
4 tasks
laroque opened this issue Mar 5, 2019 · 0 comments
Open
4 tasks

dripline reporting of run metrics #109

laroque opened this issue Mar 5, 2019 · 0 comments
Assignees

Comments

@laroque
Copy link
Member

laroque commented Mar 5, 2019

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:

  1. 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.

  2. 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.
@laroque laroque self-assigned this Mar 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant