Project

General

Profile

Actions

Feature #65119

closed

syslog flood

Added by DMK E-BUSINESS GmbH about 9 years ago. Updated over 8 years ago.

Status:
Rejected
Priority:
Should have
Assignee:
-
Category:
Logging
Target version:
-
Start date:
2015-02-17
Due date:
% Done:

0%

Estimated time:
PHP Version:
Tags:
Complexity:
easy
Sprint Focus:

Description

When a database error or something similar occurs, the syslog is possibly flooded. If you send fatal errors for example via mail then this could easily overfill the mailbox given you have a website with several cronjobs running and many visitors per minute.

I thing there should be some kind of locking so syslog logs the same error only once a minute (could be configurable) or so.

If you consider this feature also as valuable, then we would be glad to contribute a solution.

Actions #1

Updated by Markus Klein about 9 years ago

Hi!

Feel free to push a solution/draft to our reviewing system Gerrit.

http://wiki.typo3.org/CWT

Thanks.

Actions #2

Updated by Gerrit Code Review about 9 years ago

  • Status changed from New to Under Review

Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/37944

Actions #3

Updated by Gerrit Code Review over 8 years ago

Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/37944

Actions #4

Updated by Markus Klein over 8 years ago

  • Status changed from Under Review to Rejected

Filtering of log messages is not job of the log generating entity but of the log manager.

Actions

Also available in: Atom PDF