Feature #3864

Implement filtering for log messages

Added by Robert Lemke over 10 years ago. Updated about 9 years ago.

Status:
Resolved
Priority:
Should have
Category:
Log
Start date:
2009-07-10
Due date:
% Done:

100%

PHP Version:
Has patch:
Complexity:

Description

Currently all severities are always logged. It should be possible to define filters per backend so only certain log entries are written.

Associated revisions

Revision 9ba1f85f (diff)
Added by Karsten Dambekalns about 10 years ago

[+FEATURE] FLOW3 (Log): The file backend now logs only messages above a given severity, resolves #3864.
[~TASK] FLOW3 (Log): Some cleanup to comments and code.
[~CONFIGURATION]: Added severityThreshold to the log backend options, in Production context only messages warnings (and above) are logged, in Development context all messages are logged.

Revision f15d0c69 (diff)
Added by Karsten Dambekalns about 10 years ago

[+FEATURE] FLOW3 (Log): The file backend now logs only messages above a given severity, resolves #3864.
[~TASK] FLOW3 (Log): Some cleanup to comments and code.
[~CONFIGURATION]: Added severityThreshold to the log backend options, in Production context only messages warnings (and above) are logged, in Development context all messages are logged.

History

#1 Updated by Robert Lemke about 10 years ago

  • Target version deleted (1.0 alpha 3)

#2 Updated by Karsten Dambekalns about 10 years ago

  • Status changed from New to Accepted
  • Assignee set to Karsten Dambekalns
  • Target version set to 1.0 alpha 5

#3 Updated by Karsten Dambekalns about 10 years ago

  • Status changed from Accepted to Resolved
  • % Done changed from 0 to 100

Applied in changeset r3239.

Also available in: Atom PDF