Skip to content

Review events being collect by DMS

Description

Click to expand

Who

  1. @deependra.singh2 -- developer
  2. @dagiopia -- reviewer
  3. @dagiopia @kabir.kbr @janaina.senna -- architectural definitions

What

  1. Review what events are being collected on DMS and sent to statsdb.
  2. Re-implement events that could be removed during refactoring for nunet-adapter.
  3. Update telemetry API if we need to reflect changes on it (https://nunet.gitlab.io/open-api/telemetry-api-spec/develop/).

How

  1. Send an event information to StatsDB communicating with the gRPC server.

image

  1. The available events are defined here: https://gitlab.com/nunet/architecture/-/wikis/Events-Status
  2. List all events that are already been collected by the DMS and sent to the StatDB.
  3. List events that should be implemented/re-implemented if any.
  4. Implement events listed on above item.

Why

  1. 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

  1. No technical dependencies.

Acceptance Criteria

Click to expand
  1. Code review
  2. Demo to the dev team
  3. 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