Support/MetricsDashboardPRD: Difference between revisions

Support/MetricsDashboardPRD (view source)

466 bytes added , 7 April 2009

1,623

edits

@@ Line 2: / Line 2: @@
 =Absolute must-haves=
+*Metrics should be able to be categorized so that they don't just all pile up on a single page
 *Flexible framework where new metrics can easily be added via new SQL queries
-*Metrics should be able to be categorized so that they don't just all pile up on a single page
+** Properties of an individual metrics object would include title, display format (%, number, etc), category, and period length (e.g. day, week, month)
-*Metrics may have different date ranges (e.g. last week, last month, etc.) and should be clearly labeled as such
+*Individual metrics may have different date ranges (e.g. last week, last month, etc.) and should be clearly labeled as such
-*Historic tracking of metrics -- similar to how we're saving metrics over time on the [http://spreadsheets.google.com/ccc?key=piA-a-dXCL2p7vB5pTu0HKA&hl=en Weekly Metrics spreadsheet]
+** For example, we might want to look at the traffic of the site on weekly basis, while we would want to look at CSAT trends on a monthly basis.
+*Historic storage of metrics -- similar to how we're saving metrics over time on the [http://spreadsheets.google.com/ccc?key=piA-a-dXCL2p7vB5pTu0HKA&hl=en Weekly Metrics spreadsheet]
+** The data needs to be stored in a way that allows us plot the data (piecharts, histograms) in the future. E.g. stored in the db or in xml files or similar.
 =Should be considered for inclusion=