Show network usage graphs

[majecty]

First page

1. Network Out bytes of this week(All nodes)
2. (Network Out bytes / peer count) of this week(All nodes)
3. Network Out bytes of this week(To Known Nodes, To Unknown Nodes)
   

Detail page

If you click a machine's name in the first page, you can see the detail page.

1. Network Out bytes of this week(Per network extension)
2. Network Out bytes of this week(Per to IP address)
   

[majecty]

I'm investigating chart libraries.

1. Nivo
   The explorer is using the Nivo library. It has a great document.
   Could not zoom the graph.

2. plotly.js
   Can zoom the graph.

[majecty]

We will select data needed in the graph using SQL's aggregate functions.

Table: network_usage
Column:

• id: BIGSERIAL
• time: TIMESTAMP
• network_extension: VARCHAR
• to_ip: VARCHAR
• bytes: INTEGER
• node_name: VARCHAR
• peer_count: INTEGER

[sgkim126]

We will select data needed in the graph using SQL's aggregate functions.

Table: network_usage
Column:

• id: BIGSERIAL
• time: TIMESTAMP
• network_extension: VARCHAR
• to_ip: VARCHAR

How about target_ip?

• bytes: INTEGER
• node_name: VARCHAR
• peer_count: INTEGER

And It seems that storing the peer count and traffic per peer and extension in the same table is not a good idea.

[majecty]

"target_ip" is good. I'll use the column name.

The peer_count could be changed anytime. If we save the peer_count in another table, the query would be very complicated.
Do you have a good idea?

[majecty]

Seulgi recommended the table schema below to save the peer_count. I think it is quite a good idea.

Every row in the network_usage table has a peer_count row with the same time field

Table peer_count

• id: BIGSERIAL
• time: TIMESTAMP
• node_name: VARCHAR

[majecty]

DONE at #36
However, we still have a performance issue.
We will fix it later.