Add final hop number in reports from errorCheck() routine
Current state is that errorCheck() will report the last hop of the first traceroute that is part of the anomaly worth reporting.
-
Consider whether a change in hops should be considered the end of an anomaly and the start of a new anomaly. -
Consider whether the report should also state the normal amount of hops. This would require a learning system.
Perhaps this issue can be solved together with the issues pertaining to the lengthCompare()?