Skip to content
This repository has been archived by the owner on Sep 25, 2020. It is now read-only.

add internal event tracing capabilities #139

Open
benfleis opened this issue Aug 11, 2015 · 1 comment
Open

add internal event tracing capabilities #139

benfleis opened this issue Aug 11, 2015 · 1 comment

Comments

@benfleis
Copy link
Contributor

For diagnostics, analysis, and even when ringpop is scaffolding for other tools, it would be beneficial to have a generic mechanism for forwarding ringpop internal/protocol events.

@benfleis
Copy link
Contributor Author

benfleis commented Sep 2, 2015

Address lots of good feedback from @jwolski. Next up,

  • tests
  • timers (default expire, disallow infinite?)
  • tchannel tracer self removal on some (network level?) errors?
  • a few useful events

@jwolski, @CorgiMan: what do you think about events. These are a few off the top of my head:

  • membership update
  • mark (suspect, faulty, okay)
  • join (+ recv'd)
  • ping (+ recv'd)
  • ping req (+ recv'd)
  • admin stats snapshot

If we envisioned doing stats via event, could have an admin point to configure how often they're emitted, and then top/etc. could simply subscribe.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant