Network row in Hosts dashboard differs from design

[fbalak]

In specification for Hosts dashboard are defined panels:

Panel 20: Throughput Trend

• show throughput for the host over a period of time
• chart type: Line Chart / Spark

Panel 22: Dropped Packets Trend

• show dropped packets for the host over a period of time
• infotip: Dropped Packets indicates network congestion, e.g. the queue on the switchport your host is connected to is full and packets are dropped because it can’t transmit data fast enough.
• chart type: Line Chart / Spark

Panel 23: Errors Trend

• show errors for the host over a period of time
• infotip: the number of errors indicate issues that occurred while transmitting packets due to carrier errors (duplex mismatch, faulty cable), fifo errors, heartbeat errors, and window errors, CRC errors too short frames, and/or too long frames. In short, errors typically result from faulty hardware, and/or speed mismatch.
• chart type: Line Chart / Spark

Panel 24: Overruns Trend

• show overruns for the host over a period of time
• infotip: overruns indicates that the ring-buffer of the network interface is full and the network interface doesn’t seem to get any kernel time to send out the frames stuck in the ring-buffer.
• chart type: Line Chart / Spark

but panels in Metrics documentation and in the implemented ui differ:

Present panels are:

• Throughput
• Dropped Packets Per Second
• Errors Per Second

Tested with:

tendrl-api-httpd-1.5.2-20170926T110841.a9e16c0.noarch
tendrl-commons-1.5.2-20170926T081245.0fa5e25.noarch
tendrl-api-1.5.2-20170926T110841.a9e16c0.noarch
tendrl-ui-1.5.2-20170926T100141.770936f.noarch
tendrl-node-agent-1.5.2-20170926T090753.09d1818.noarch
tendrl-monitoring-integration-1.5.2-20170926T100202.2e1d15a.noarch
tendrl-grafana-plugins-1.5.2-20170926T100202.2e1d15a.noarch
tendrl-notifier-1.5.2-20170926T102449.7678c47.noarch

[cloudbehl]

@fbalak Changed as per the requirements provided by @julienlim in Issue #91.

@julienlim Please acknowledge!

Also, the "Overruns Trend" was not possible so it's not there.

[julienlim]

@fbalak @cloudbehl If "overruns trend" not possible, we can leave that off, but probably put in a RFE for it.

[r0h4n]

@cloudbehl updates?

[cloudbehl]

@r0h4n We haven't explored the possibility of adding the overruns till now.