Last modified: 2014-11-06 00:18:13 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 T74642, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 72642 - Story: Identify and direct the purging of Event logging raw logs older than 90 days in stat1002
Story: Identify and direct the purging of Event logging raw logs older than ...
Status: RESOLVED FIXED
Product: Analytics
Classification: Unclassified
EventLogging (Other open bugs)
unspecified
All All
: High enhancement
: ---
Assigned To: Kevin Leduc
u=AnalyticsEng c=EventLogging p=0 s=2...
:
: 72742 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-10-28 19:45 UTC by nuria
Modified: 2014-11-06 00:18 UTC (History)
9 users (show)

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


Attachments

Description nuria 2014-10-28 19:45:55 UTC
Story: Identify and direct the purging of  Event logging raw logs older than 90 days in stat1002.
Comment 1 nuria 2014-10-28 19:46:39 UTC
This is tracket as part of RT ticket: #8760
Comment 2 nuria 2014-10-30 17:12:12 UTC
*** Bug 72742 has been marked as a duplicate of this bug. ***
Comment 3 Toby Negrin 2014-11-04 20:41:11 UTC
From Aaron H:

Sorry for the late response, but I'm still not sure what lives in /a/eventlogging/archive/*

Will deleting from there affect what logs we have stored in the DB?  Is this an intermediate log storage place, a canonical one, etc.?

What will we no longer be able to do after it is pruned?
Comment 4 nuria 2014-11-05 18:51:57 UTC
>Will deleting from there affect what logs we have stored in the DB? 
No it does not.
 
>Is this an intermediate log storage place, a canonical one, etc.?
Neither, these are operational logs. They also store events that do not validate and thus did not made it to the DB. Those log entries are used to troubleshoot operational issues and we should not need them around for longer than 90 days.
Comment 5 Kevin Leduc 2014-11-06 00:18:13 UTC
Andrew's comment in RT:
This is done for eventlogging:

https://gerrit.wikimedia.org/r/#/c/171329/

I ran the job manually. I will wait a day or two to make sure the cron runs as expected, and then apply this for all other logs.

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


Navigation
Links