Add bot protection for hits + session management

Description

Suggestions by Gunnar

  • Move hits to new table content_hits (keeping it in the same table can lead to locks under high load)

  • Make a new section in Settings, call it Logging Options?

    • Text field for regex bot agent string (exclude user agents from logging)

    • enable/disable hit count

      • If hit count is disabled, do not show pie chart

    • exclude ip address ranges

  • wrap updateHits in a try/catch

    • We had some entries where the logging failed, don't know why this happend?

      • Where to log errors then?

  • We should have a setting which lowers the session time out for bots, should this be done pragmatically only? Or where should we put this setting?

Gliffy Diagrams

Activity

Show:
Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Fix versions

Components

Priority

Sentry

Created August 25, 2014 at 11:43 PM
Updated March 5, 2015 at 12:41 AM
Resolved March 5, 2015 at 12:41 AM