Preview Tool

Cisco Bug: CSCuq35895 - percent growth aggration time ranges should be restricted

Last Modified

Oct 16, 2017

Products (1)

  • Cisco MATE Live

Known Affected Releases


Description (partial)

percent growth aggration time ranges should be restricted

See screenshot.  This picture shows a typical example of how numbers can clearly be trending upwards, while the percent growth graph shows an opposite downwards trend.  The numbers are mathematically correct, but the result is ridiculous.  The problem is that each % growth number is compromised of only two data points.  There's no way to reliably draw a trend through two data points.  We should restrict trending and % growth reports to allow for at least 4 data points for each trend line.  That is, the trending aggregation date range should be 1/4 of the overall aggregation range for % growth reports, or of the overall date range, for trending reports in general.  In the screenshots, 23hour.png has a 1-day aggregation with a 23 hour time range for % growth.  Silly graphs result.  Set the % growth time to 1 hour and the graph looks good (1hour.png.)  Used a 6.0 build with Cox data on ml4.  Ad hoc/nodes/1 week (2011-8-1 0:0:0 -> 2011-8-7 23:0:0).
Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.