waku-org / metrics.waku.org

1 stars 2 forks source link

Metrics discovery node data #4

Open chair28980 opened 1 year ago

chair28980 commented 1 year ago

To support metrics which cannot be fetched via Grafana, deploy a metrics discovery node.

MVP metric data:

Begin work following completion of: https://github.com/waku-org/metrics/issues/1 https://github.com/waku-org/metrics/issues/2 https://github.com/waku-org/metrics/issues/3

alrevuelta commented 1 year ago

can we aim for:

the networkmonitor tool has already al these metrics.

fryorcraken commented 11 months ago

Regarding https://grafana.infra.status.im/d/b819dbfe-acb6-4086-8736-578ca148d7cd/waku-networkmonitor-v2?orgId=1&refresh=5s

Some feedback:

Not sure about the "successfully connected peers" here. why is 54 false and 28 true?

Protocol by identity: maybe filter out only waku protocol. also, I assume this is for connected peers? so maybe change title to "Connected peers' protocols"

How is the latency measured?

fryorcraken commented 11 months ago

Also from https://github.com/waku-org/metrics.waku.org/issues/3

What's the bandwidth usage? could we do average on past hour and past day (And past month) for example?

Avg message size: what is the time frame? Hour/day/etc

message rate would be good!

content topic seen would be great too.

fryorcraken commented 10 months ago

I only see "store" among the protocols at the moment. are the other protocol not mounted in the monitoring node?