Project

General

Profile

Bug #7505

Trends are not aggregrated

Added by Ohad Levy over 8 years ago. Updated almost 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Trends
Target version:
Difficulty:
Triaged:
Bugzilla link:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Trend counters are not aggregated atm, we should reduce the data points over time.


Related issues

Related to Foreman - Refactor #10439: Reduce task should be idempotentClosed2015-05-10
Related to Foreman - Refactor #10438: Remove unnecessary rake tasks from trendsClosed2015-05-10
Has duplicate Foreman - Bug #4114: Trends don't scale well and become very slowDuplicate2014-01-17

Associated revisions

Revision 8e567e22 (diff)
Added by Shimon Shtein about 8 years ago

Fixes #7505 - Changed the way trends are stored in the DB. Now they are stored as intervals

History

#1 Updated by The Foreman Bot over 8 years ago

  • 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

  • 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

#5 Updated by Dominic Cleal about 8 years ago

  • Legacy Backlogs Release (now unused) set to 35

#6 Updated by Dominic Cleal about 8 years ago

#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

  • 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

Also available in: Atom PDF