Project

General

Profile

Actions

Feature #6126

closed

Add information about last filter match to reporter

Added by Jan Mach over 4 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Jan Žerdík
Category:
Development - Core
Target version:
Start date:
12/10/2019
Due date:
% Done:

100%

Estimated time:
To be discussed:
No

Description

It would be very useful to have information about last filter match timestamp. This information could be used to prune the list of all defined filters and remove those that are not matching anymore and just delay the processing.

Actions #1

Updated by Pavel Kácha over 4 years ago

Maybe we could start (or complement that) with more verbose logging? Now it seems we log just number of events:

Filters let 1 events through, 0 blocked.

If we logged names of matching rules, we could do even more interesting awk-jobs (like "how many events from this particular detector gets dropped", or "how many people drop something concerning this detector")

Actions #2

Updated by Jan Mach over 4 years ago

  • To be discussed changed from No to Yes
Actions #3

Updated by Jan Mach over 4 years ago

  • Assignee changed from Jan Mach to Jan Žerdík
Actions #4

Updated by Pavel Kácha over 4 years ago

After discussion - migration to add column to Filters table; when updating counters, update also actual timestamp.

Actions #5

Updated by Pavel Kácha over 4 years ago

  • To be discussed deleted (Yes)
Actions #6

Updated by Jan Žerdík about 4 years ago

  • To be discussed set to Yes
Actions #7

Updated by Jan Mach about 4 years ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100
  • To be discussed changed from Yes to No

Looks good.

Actions

Also available in: Atom PDF