Feature #3864
Implement filtering for log messages
| Status: | Resolved | Start date: | 2009-07-10 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assigned To: | Karsten Dambekalns | % Done: | 100% |
|
| Category: | Log | |||
| Target version: | TYPO3 Flow Base Distribution - 1.0 alpha 5 | |||
| PHP Version: | Complexity: | |||
| Has patch: |
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
[+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.
[+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 almost 6 years ago
- Target version deleted (
1.0 alpha 3)
#2 Updated by Karsten Dambekalns almost 6 years ago
- Status changed from New to Accepted
- Assigned To set to Karsten Dambekalns
- Target version set to 1.0 alpha 5
#3 Updated by Karsten Dambekalns almost 6 years ago
- Status changed from Accepted to Resolved
- % Done changed from 0 to 100
Applied in changeset r3239.