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

What metrics to export? #304

Open
anacrolix opened this issue Mar 21, 2019 · 1 comment
Open

What metrics to export? #304

anacrolix opened this issue Mar 21, 2019 · 1 comment
Labels
kind/enhancement A net-new feature or improvement to an existing feature metrics need/community-input Needs input from the wider community topic/filecoin Topic filecoin

Comments

@anacrolix
Copy link
Contributor

anacrolix commented Mar 21, 2019

This issue will serve to discuss and collect specific metrics for export, through Prometheus, or Prometheus-compatible tooling (to keep us focused on the kinds of values), such as in #297. It is not a 1:1 list, but rather a list of things we want to and can observe. Units, and types can be figured out in implementation to avoid getting off-topic here.

Here is the list:

  • Number of k-buckets
  • Number of entries in each k-bucket
  • Outbound/inbound message sizes
  • Outbound/inbound message counts
  • Outbound request latency
  • Write latency (time between wanting to send a message, and sending it Add stream pooling #285 and DHT Request pipelining #92)
@anacrolix anacrolix changed the title Export metrics What metrics to export? Mar 21, 2019
@anacrolix
Copy link
Contributor Author

@raulk I'd like some suggestions on aspects of the dial queue to be exported.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement A net-new feature or improvement to an existing feature metrics need/community-input Needs input from the wider community topic/filecoin Topic filecoin
Projects
None yet
Development

No branches or pull requests

1 participant