search

OT-Hub / OTHub

OT Hub is a community-made project for live insights into the OriginTrail Decentralized Network.
https://othub.origin-trail.network/
MIT License
5 stars 2 forks source link

Add DH IDs in jobs export output #102

Open botnumberseven opened 3 years ago

botnumberseven commented 3 years ago

Currently Jobs Export functionality here is good way to visualize jobs flow in external tools, as the output table is quite machine-friendly. One key missing component in the dataset - Node IDs of DHs who won the job. Adding Node IDs of DHs who won the job would allow to create custom visualization / nodes monitoring tools.

lukeskinner commented 3 years ago

I'll add this in one of my next updates. thanks for the idea!

botnumberseven commented 3 years ago

I've changed a bit the way I use API since then. So while it's still would be a good improvement, I use API a bit different now.

I start with a list of NodeIDs for my node. Then for every NodeID I run two calls: 1) "https://v5api.othub.info/api/nodes/DataHolder/"&nodeid - to get details for the node 2) "https://v5api.othub.info/api/nodes/DataHolder/"&nodeid&"/jobs?_limit=0&_page=0" - to get list of all jobs for my node

These 2 calls gives me pretty good dataset for my nodes. I might missing litigation activity here, not sure, I haven't though about litigations yet.

The open question I have is about overall summarized network data, so I can compare my nodes performance to an average node one. E.g. summarized data per day for a number of active nodes and number of new jobs per chain would be great. As pulling all nodes all jobs data for that seems to be an overkill.

lukeskinner commented 3 years ago

The last comment is similar to #103 which i think would be good to have at some point.