HOPR CT node logging analytics

[QYuQianchen]

Description

Cover traffic (CT) nodes produce artificial traffic to the HOPR network. CT nodes send messages to itself through with a looped path. This path is constructed by selecting randomly a node in the network as the first hop and build the rest of the path according to nodes' "importance score". To better understand the nature of CT, please read §6 Cover traffic of our yellow paper and https://github.com/hoprnet/hoprnet/issues/2006

We need to understand how CT nodes perform through logs produced by CT nodes. CT nodes emit logs to Google Logger. Those logs can be downloaded or streamlined through an API.

Migrate to Python

• [x] #127
• [x] #129

Parse logs

• [x] Node is running and gives tick regularly. Get the Δt over time and analyze those intervals
• [x] Node restarts with setting channel strategy from

Once the PR #69 gets merged, please continue working on the cover-traffic-logs/logs.ipynb file so that

• [x] #71
• [x] #72

Fetch logs

• [x] #74
• [x] #124

Analyse information

• [x] #133
• [x] #73
• [x] #77
• [x] #78
• [x] #80
• [x] #81

[nionis]

@Eleonora0119 could you update the tasks on what was done?

[SCBuergel]

@QYuQianchen not sure if this one is related but since it's not tracked in any epic I'd add it https://github.com/hoprnet/hopr-devrel/issues/131

[SCBuergel]

The current version of the code is located here. The logs are being parsed correctly in that code but the next steps of actually processing (according to the various issues in the list) are largely pending.

At the end of Nora's internship the issue was that we had no CT node running to gather more data, so other tasks were prioritized higher.

This should be picked up again once we have a testnet with CT node running.