gerritbot added a subscriber: gerritbot.
gerritbot added a comment.
Change 253571 had a related patch set uploaded (by Addshore):
Social metrics to graphite
https://gerrit.wikimedia.org/r/253571
TASK DETAIL
https://phabricator.wikimedia.org/T117735
EMAIL PREFERENCES
gerritbot added a comment.
Change 253572 had a related patch set uploaded (by Addshore):
Convert site_stats to graphite
https://gerrit.wikimedia.org/r/253572
TASK DETAIL
https://phabricator.wikimedia.org/T117735
EMAIL PREFERENCES
gerritbot added a comment.
Change 253573 had a related patch set uploaded (by Addshore):
Convert getclaims stats to graphite
https://gerrit.wikimedia.org/r/253573
TASK DETAIL
https://phabricator.wikimedia.org/T117735
EMAIL PREFERENCES
gerritbot added a comment.
Change 253573 merged by Addshore:
Convert getclaims stats to graphite
https://gerrit.wikimedia.org/r/253573
TASK DETAIL
https://phabricator.wikimedia.org/T117735
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/
To: Addshore,
gerritbot added a comment.
Change 253571 merged by jenkins-bot:
Social metrics to graphite
https://gerrit.wikimedia.org/r/253571
TASK DETAIL
https://phabricator.wikimedia.org/T117735
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/
To: Addshore,
gerritbot added a comment.
Change 253572 merged by Addshore:
Convert site_stats to graphite
https://gerrit.wikimedia.org/r/253572
TASK DETAIL
https://phabricator.wikimedia.org/T117735
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/
To: Addshore,
fgiunchedi added a subscriber: fgiunchedi.
fgiunchedi added a comment.
thanks for expanding on that, here's my (as the person who's been looking after
our graphite stack) opinion:
- graphite isn't really data warehouse, thus I wouldn't recommend it as the
primary storage for the
Christopher added a subscriber: Christopher.
Christopher added a comment.
To expand on the use cases for a metrics storage backend here is appropriate.
I think that Wikidata content metrics favor long term retention (i.e. forever)
because their purpose is to evaluate dynamics over both short
Addshore added a comment.
> If the proposal to use Graphite can substantiate a long term ( not decaying )
> storage method, then it should work for both
Retention and resolution changes / decay are both configurable.
Simply setting the retention to 1d:100y would / should keep daily metrics