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

Create metrics endpoint #16

Open
ghost opened this issue Jun 10, 2019 · 1 comment
Open

Create metrics endpoint #16

ghost opened this issue Jun 10, 2019 · 1 comment

Comments

@ghost
Copy link

ghost commented Jun 10, 2019

We need a metrics endpoint to help with debugging/performance testing, similar to the /status endpoint. We can use similar values to what's covered in telemetry

  • HTTP endpoint (not websockets)
  • JSON format

Values

  • Block number
  • Peers
  • Block Hash
  • Finalized Block number
  • Finalized Block Hash
  • Syncing speed (blocks per second)
  • Network speed

Related: paritytech/substrate#814

@xlc
Copy link
Contributor

xlc commented Jun 10, 2019

Is Syncing speed needed? One can calculate it from latest block number from the client side.
Do we need to implement this in the node or we can make another node.js service that use js sdk to query those information from node and convert them to proper format for Grafana consumption?
I am not against the idea of having this implemented in node, just a separate node.js server is going to be easier and faster to implement and more flexible.

cowboy-bebug pushed a commit that referenced this issue Oct 16, 2019
* Raise events when asset permissions are updated or total asset issuance is changed.

* Add unit tests to assert that appropriate events are raised when asset permissions are updated or total asset issuance is changed.

* Execute `cargo fmt`.
cowboy-bebug pushed a commit that referenced this issue Oct 16, 2019
* Raise events when asset permissions are updated or total asset issuance is changed.

* Add unit tests to assert that appropriate events are raised when asset permissions are updated or total asset issuance is changed.

* Execute `cargo fmt`.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant