Project

General

Profile

Feature #84

Nightly Filter Summary E-Mail

Added by Jim Pingle over 7 years ago. Updated about 7 years ago.

Status:
New
Priority:
Low
Assignee:
Category:
Web Interface
Target version:
Start date:
09/12/2009
Due date:
% Done:

0%


Description

Scott and I talked about this earlier on IRC. Could be a package for 2.0, or worked in somehow.

A daemon of some sort could check filter logs every 5 minutes and collect summary data, then store it in an xml or serialized data file. At the end of a 24 hour period, this data could be used to generate a report on the filter activity for the day.

The report could look similar to the pie charts output by the filter log summary graphs, but those only work on whatever data is currently in the log.

It would need to keep track of the last log message it read to ensure that it isn't counting things more than once. If the entire log file wraps in under 5 minutes, it should log an error telling the admin to increase the log size (also feature that doesn't yet exist, but should be fairly easy to add.)

Associated revisions

Revision 2b2b38ce
Added by mezz almost 13 years ago

-Update to 2.1.2.

NSD 2.1.2 release notes:

FEATURES:
- NSD now fully supports unknown record types using the notation
specified in RFC3597.
- Support for the following RR types has been added: WKS, X25, ISDN,
RT, NSAP, PX, NAPTR, KX, CERT, DNAME, and APL. DNAME special
processing is not supported.

BUG FIXES:
- Bug #84: NSD now uses SIGUSR1 instead of SIGILL to report stats.
- Bug #85: Support for WKS records.
- Bug #86: The characters "#%&^[]?" can now be used without backslash
in zone file domain names.
- Plugin callback return type fixed.
- The maximum message length for IPv6 UDP packets is now limited to
the IPv6 minimum MTU (1280) unless the IPV6_USE_MIN_MTU socket
option is supported.

PR: ports/69914
Submitted by: Olafur Osvaldsson <> (maintainer)

History

#2 Updated by Jim Pingle over 7 years ago

  • Target version changed from 2.0 to 3

Change the target on this to 3.0. It might be a package for 2.0 but I doubt it would be complete and refined enough to be usable by 2.0.

#3 Updated by Chris Buechler about 7 years ago

  • Target version changed from 3 to Future
  • Affected version deleted (2.0)

Also available in: Atom PDF