Project

General

Profile

Task #6777

Story #6775: Implement COUNTER compliance for the Event Index

Implement multiple visit check for Event Index

Added by Peter Slaughter almost 7 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Category:
-
Start date:
2015-01-26
Due date:
% Done:

100%

Story Points:
Sprint:

Description

Log Aggregation processing will be updated to check if multiple requests occurred from the sample IP address
within a short interval, and "duplicate" Event Index records will be flagged accordingly.

See "Counter Compliance":http://jenkins-1.dataone.org/jenkins/job/API%20Documentation%20-%20trunk/ws/api-documentation/build/html/design/UsageStatistics.html#counter-compliance for details

Associated revisions

Revision 15145
Added by Peter Slaughter almost 7 years ago

Add config property for COUNTER log filtering. refs #6777

Revision 15192
Added by Peter Slaughter almost 7 years ago

Event index COUNTER related fields are now: repeatVisits, robotsLoose, robotsStrict. refs #6776, #6777

Revision 15192
Added by Peter Slaughter almost 7 years ago

Event index COUNTER related fields are now: repeatVisits, robotsLoose, robotsStrict. refs #6776, #6777

History

#1 Updated by Peter Slaughter almost 7 years ago

  • Parent task set to #6775

Added to story #6775

#2 Updated by Peter Slaughter almost 7 years ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 30

#3 Updated by Peter Slaughter almost 7 years ago

  • % Done changed from 30 to 50
  • Status changed from In Progress to Testing

#4 Updated by Peter Slaughter over 6 years ago

  • Status changed from Testing to Closed
  • translation missing: en.field_remaining_hours set to 0.0
  • % Done changed from 50 to 100

Tested in sandbox environment.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)