-
Change Request
-
Resolution: Unresolved
-
Trivial
-
None
-
None
Hi,
I've notcied that lots of users tends to set long periods of time while watching graphs (month and more) and unfortunately in large environments displaying those graphs (espacially when there are more than one on a screen), can take lots of time.
Would it be possible to copy a mechanism of data reduction, which is being used to calculate data for trend tables from history tables, and create two more types of tables?
For example:
- MonthlyTrends - daily min,max and avg values from trend table, that data would be displayed when user wants to display graphs for more than 3-4 weeks.
- YearlyTrends - weekly min, max and avg values from MonthlyTrens table, that data would be displayed when user wants to display graphs for more than 9 months.