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
However, seems tightly coupled to the option -- and the ability to dump out this table would be quite valuable, without all the extra stdout and keyboard stuff. This could go with an option, dump_mesh so you can clearly see what a given microservice sees when it joins.
I've got a PR for this.... the only thing I wasn't sure on was the sort order. I'm keeping monitor_data which tracks the rem and add totals as a hash, not an array. If something isn't found it is added, so the same behaviour right now where new entries are added to the top is not retained.
The text was updated successfully, but these errors were encountered:
tswaters
pushed a commit
to tswaters/sneeze
that referenced
this issue
Mar 31, 2017
The monitoring script is really cool, +1 to that.
However, seems tightly coupled to the option -- and the ability to dump out this table would be quite valuable, without all the extra stdout and keyboard stuff. This could go with an option,
dump_mesh
so you can clearly see what a given microservice sees when it joins.I've got a PR for this.... the only thing I wasn't sure on was the sort order. I'm keeping
monitor_data
which tracks therem
andadd
totals as a hash, not an array. If something isn't found it is added, so the same behaviour right now where new entries are added to the top is not retained.The text was updated successfully, but these errors were encountered: