Skip to content
This repository has been archived by the owner on Apr 24, 2023. It is now read-only.

feat: add instrumentation to sig server #114

Closed
wants to merge 1 commit into from

Conversation

daviddias
Copy link
Member

No description provided.

@daviddias daviddias added the status/in-progress In progress label Jul 3, 2017
@daviddias daviddias mentioned this pull request Jul 3, 2017
@daviddias daviddias requested a review from a user July 3, 2017 19:52
@daviddias
Copy link
Member Author

Does this -- https://github.com/roylines/node-epimetheus#instrumentation -- satisfy your requests, @lgierth ? :)

@victorb
Copy link
Member

victorb commented Jul 3, 2017

Would be wonderful to be able to get metrics about how many peers have ever been online and are currently online as well. Might want to add as a task for the future though.

@ghost
Copy link

ghost commented Jul 3, 2017

how many peers have ever been online

That (logging) is a use case outside of Prometheus scope, but we'll eventually have infrastructure for that too :) (spoiler: the new gateway will have logstash)

are currently online

That'd work

@victorb
Copy link
Member

victorb commented Jul 3, 2017

That (logging) is a use case outside of Prometheus scope, but we'll eventually have infrastructure for that too :) (spoiler: the new gateway will have logstash)

Hm, I was thinking of something in webrtc-star that would just increment a counter every time a peer joins and then expose that counter via the debug endpoint. Wouldn't that work? Similar as the online counter.

@ghost
Copy link

ghost commented Jul 3, 2017

Hm, I was thinking of something in webrtc-star that would just increment a counter every time a peer joins and then expose that counter via the debug endpoint. Wouldn't that work? Similar as the online counter.

And then you need to persist the counter somewhere :)

@daviddias
Copy link
Member Author

Hey @victorbjelkholm @lgierth, could you give me what more clear instructions of what you want to get this merged and deployed?

@ghost
Copy link

ghost commented Aug 29, 2017

Yes I think this looks good -- but I wonder whether you want to actually count something? The generic stats of the http endpoint are useful, but number of nodes connected, possibly by transport, might also be useful. It's a bit hard to tell what exactly webrtc-star does, there's probably a few more interesting metrics.

@daviddias
Copy link
Member Author

The Signalling Server keeps track of:

  • Number of nodes connected to it
  • Ids of those nodes

I could also add counters for:

  • Number of handshakes
  • What are the handshakes happening (src -> dst)

Would this be useful, @lgierth ?

@ghost
Copy link

ghost commented Aug 29, 2017

  • Number of nodes connected to it
  • Ids of those nodes
    Yeah I've heard that before, but the repo (same for webrtc-direct) still lacks an exact explanation of what is does, and how it ties together with the /libp2p-webrtc-star/ip4/tcp/ws style addresses.

@ghost
Copy link

ghost commented Aug 29, 2017

Would this be useful, @lgierth ?

Sure these sound good

@daviddias
Copy link
Member Author

@victorbjelkholm is finishing this PR something you would like to do?

@victorb victorb self-assigned this Sep 4, 2017
@victorb
Copy link
Member

victorb commented Sep 4, 2017

@diasdavid sure thing!

@daviddias
Copy link
Member Author

@mkg20001 just added metrics! #127

@mkg20001
Copy link
Member

@diasdavid Can this be closed? #127 is already merged...

@daviddias daviddias closed this Feb 20, 2018
@daviddias daviddias deleted the feat/instrumentation branch February 20, 2018 10:03
@ghost ghost removed the status/in-progress In progress label Feb 20, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants