Bug #7505
Trends are not aggregrated
Description
Trend counters are not aggregated atm, we should reduce the data points over time.
Related issues
Associated revisions
History
#1
Updated by The Foreman Bot over 8 years ago
Updated by - Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/2126 added
- Pull request deleted (
)
#2
Updated by Shimon Shtein over 8 years ago
Updated by - Assignee set to Shimon Shtein
#3
Updated by Shimon Shtein over 8 years ago
- Related to Bug #4114: Trends don't scale well and become very slow added
#4
Updated by Shimon Shtein about 8 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset 8e567e22c4bd58787bfcca8f73bee18cbd9cf8b8.
#5
Updated by Dominic Cleal about 8 years ago
Updated by - Legacy Backlogs Release (now unused) set to 35
#6
Updated by Dominic Cleal about 8 years ago
- Related to Refactor #10439: Reduce task should be idempotent added
#7
Updated by Dominic Cleal about 8 years ago
- Related to Refactor #10438: Remove unnecessary rake tasks from trends added
#8
Updated by Ohad Levy almost 8 years ago
Updated by - Related to deleted (Bug #4114: Trends don't scale well and become very slow)
#9
Updated by Ohad Levy almost 8 years ago
- Has duplicate Bug #4114: Trends don't scale well and become very slow added
Fixes #7505 - Changed the way trends are stored in the DB. Now they are stored as intervals