Project

General

Profile

Actions
Copy link

Optimization #614

open
EL CT

Rate limiting messages

Optimization #614: Rate limiting messages

Added by Eric Leblond over 13 years ago. Updated over 2 years ago.

Status:
Assigned
Priority:
Normal
Assignee:
Community Ticket
Target version:
TBD
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 open — 0 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

VJ Updated by Victor Julien over 13 years ago Actions
Copy link
 #1

  • 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.

VJ Updated by Victor Julien over 7 years ago Actions
Copy link
 #2

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

AH Updated by Andreas Herz about 7 years ago Actions
Copy link
 #3

  • Assignee set to Community Ticket

VJ Updated by Victor Julien over 6 years ago Actions
Copy link
 #4

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

PA Updated by Philippe Antoine over 2 years ago Actions
Copy link
 #5

  • Tracker changed from Feature to Optimization
Actions
Copy link

Also available in: PDF Atom