Assignment event tracking needs revision
Description
is related to
Activity
BrandenB November 10, 2009 at 11:16 AM
Thanks Stephen, I'll reverse the affect/s versions on this for the filters and create a new ticket for this request.
Stephen Marquard November 9, 2009 at 12:47 PM
i.t.o. JIRA etiquette, if the resolution addressed the original issue, then it's better to leave it as-is (especially if it relates to already-released versions). If you want new or different behaviour, create a new JIRA and link it.
JIRAs should only be reopened where the changes associated with the JIRA do not correctly address the stated issue.
BrandenB November 9, 2009 at 12:24 PM
I would like this solution to be reconsidered. I think we can include an asn.read.assignment event on the ui layer that wouldn't bombard the events table..
What are your thoughts on event logging in AssignmentAction?
Filter Maintainer August 8, 2008 at 6:03 AM
2.5.0 QA has been completed. Unfortunately, there were not resources available to specifically test this issue. If you find this to still be a problem in the latest release (at this point 2.5.2), please reopen the JIRA and add the latest affects version.
Zhen Qian September 10, 2007 at 9:32 AM
Further fix to remove the asn.read log from the Assignment tool is checked in as r34841 for trunk, r34847 for 2-4-x and r34849 for post-2-4.
Thanks,
Zhen
Details
Details
Priority
Critical
Assignments is currently logging too many events of "asn.read.assignment" (EVENT_ACCESS_ASSIGNMENT).
When an Instructor or TA views the list of submissions for an assignment, all the assignments submissions are read, and one event is logged for every submission. For large sites, this can lead to huge numbers of events being logged.
Our production stats show that asn.read.assignment is the 3rd-most frequent event (42021 events in 24 hours).
OTOH EVENT_ACCESS_ASSIGNMENT_SUBMISSION which you'd expect to see logged if a TA/Instructor clicks through to a specific assignment is not logged at all.
Assignment event logging needs to be reviewed urgently, as this is a performance issue for large sites.
The QA for this should involve carrying out a number of typical operations as a student, TA and lecturer in a course site with existing assignments with submissions (say an assignment with 100 submissions) and examining the event log records in SAKAI_EVENT that result.