Project

General

Profile

Actions

Optimization #614

open

Rate limiting messages

Added by Eric Leblond over 11 years ago. Updated 10 months ago.

Status:
Assigned
Priority:
Normal
Target version:
Effort:
low
Difficulty:
medium
Label:

Description

SCLog* function family should be updated to limit the number of repetitive messages. One way to do so could be to store the log messages in a hash and keeping a counter for each entry to set up the rate limiting.


Related issues 2 (2 open0 closed)

Related to Suricata - Optimization #551: Replace SCLogError by a counter for memory issue and other memcapNewOISF DevActions
Related to Suricata - Feature #1489: Log a message when memcap limit is reachedNewCommunity TicketActions
Actions #1

Updated by Victor Julien over 11 years ago

  • Status changed from New to Assigned
  • Assignee set to Eric Leblond
  • Target version set to TBD

Maybe we can have a hard limit on the number of messages per second (configurable perhaps) and also track the last X messages to suppress exact duplicates.

Actions #2

Updated by Victor Julien almost 6 years ago

  • Assignee changed from Eric Leblond to Anonymous
  • Effort set to low
  • Difficulty set to medium
Actions #3

Updated by Andreas Herz about 5 years ago

  • Assignee set to Community Ticket
Actions #4

Updated by Victor Julien over 4 years ago

  • Related to Feature #1489: Log a message when memcap limit is reached added
Actions #5

Updated by Philippe Antoine 10 months ago

  • Tracker changed from Feature to Optimization
Actions

Also available in: Atom PDF