Review events being collect by DMS
Description
Click to expand
Who
- @deependra.singh2 -- developer
- @dagiopia -- reviewer
- @dagiopia @kabir.kbr @janaina.senna -- architectural definitions
What
- Review what events are being collected on DMS and sent to statsdb.
- Re-implement events that could be removed during refactoring for nunet-adapter.
- Update telemetry API if we need to reflect changes on it (https://nunet.gitlab.io/open-api/telemetry-api-spec/develop/).
How
- Send an event information to StatsDB communicating with the gRPC server.
- The available events are defined here: https://gitlab.com/nunet/architecture/-/wikis/Events-Status
- List all events that are already been collected by the DMS and sent to the StatDB.
- List events that should be implemented/re-implemented if any.
- Implement events listed on above item.
Why
- A peer needs to update the stats db for the overall network status information. Since the NuNet platform is a decentralized p2p infrastructure, there is no way to monitor devices unless the peers to report their status.
When
- No technical dependencies.
Acceptance Criteria
Click to expand
- Code review
- Demo to the dev team
- Telemetry API update (if needed)
Work Breakdown Structure (WBS)
Task | Description | Duration | Status | Start Date | End Date | Comment |
---|---|---|---|---|---|---|
A | Review all events are being collected on DMS | 2 hrs | Done | 6 Apr | 6 Apr | |
B | Re-implement events that could be removed during refactoring for nunet-adapter | x hrs | Done | 6 Apr | 7 Apr | I split this task in B.1 and B.2 |
B.1 | Find the placeholder and implement device_resource_change event | 4-8 hrs | Done | 6 Apr | 7 Apr | |
B.2 | Implement the device_status_change event | x hrs | Not started | This task is going to do in another issue |
Edited by Deependra Singh