Last modified: 2014-04-14 14:58:38 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T44181, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 42181 - [gdash] Add long-term history graphs for some gdash metrics
[gdash] Add long-term history graphs for some gdash metrics
Status: RESOLVED FIXED
Product: Wikimedia
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Nemo
: analytics, ops
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-11-16 08:33 UTC by Nemo
Modified: 2014-04-14 14:58 UTC (History)
4 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Nemo 2012-11-16 08:33:40 UTC
How hard is it to add additional graphs which just show the same metric for a longer period? (Where is the code?)
For instance, it would be nice to have https://gdash.wikimedia.org/dashboards/datastores/ for a year, not just a week, to plan when some DB-intensive tasks can be executed in the mid/long term.
Comment 1 Nemo 2012-11-17 16:21:01 UTC
According to description, "Statistics" is only for WikiStats.
Comment 2 Andre Klapper 2012-11-17 16:24:59 UTC
I have no idea what gdash is or who runs it.
Comment 3 Nemo 2012-11-17 16:28:37 UTC
(In reply to comment #2)
> I have no idea what gdash is or who runs it.

Ops, AFAICS. https://blog.wikimedia.org/2012/03/15/measuring-site-performance-at-the-wikimedia-foundation/
Comment 4 Asher Feldman 2012-11-19 21:13:12 UTC
There isn't currently a year of this data, but we can revisit this later.
Comment 5 Ori Livneh 2014-02-18 22:49:08 UTC
(In reply to Nemo from comment #0)
> For instance, it would be nice to have
> https://gdash.wikimedia.org/dashboards/datastores/ for a year, not just a
> week, to plan when some DB-intensive tasks can be executed in the mid/long
> term.

Nemo, since filing this report, you've managed to find your way around the gdash configuration files (in operations/puppet.git:files/gdash). Would you like to submit a patch for this? I'd be happy to review / merge.
Comment 6 Nemo 2014-02-18 22:52:46 UTC
Yes, I just was and am unsure what metrics we have enough data for how long exactly. By now however many of them have a lot of history and does something break horribly if a part of the graph is missing, anyway?
Comment 7 Ori Livneh 2014-02-19 02:31:03 UTC
(In reply to Nemo from comment #6)
> Yes, I just was and am unsure what metrics we have enough data for how long
> exactly. By now however many of them have a lot of history and does
> something break horribly if a part of the graph is missing, anyway?

No, nothing breaks. You just get an incomplete graph.
Comment 8 Gerrit Notification Bot 2014-03-05 19:18:51 UTC
Change 117020 had a related patch set uploaded by Nemo bis:
[gdash] Add some yearly graphs

https://gerrit.wikimedia.org/r/117020
Comment 9 Gerrit Notification Bot 2014-03-06 05:59:40 UTC
Change 117020 merged by Ori.livneh:
[gdash] Add some yearly graphs

https://gerrit.wikimedia.org/r/117020
Comment 10 Nemo 2014-04-14 14:58:38 UTC
Seems ok so far.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links