View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 5731 | Composr | errorlog | public | 2024-04-24 18:52 | 2024-04-24 22:22 |
| Reporter | PDStig | Assigned To | PDStig | ||
| Priority | normal | Severity | feature | ||
| Status | resolved | Resolution | fixed | ||
| Summary | 5731: Optimise error log syntax and UI | ||||
| Description | Optimise what we put in the error log file (where possible) with the following new syntax: [timestamp] Component: CRITICAL|ERROR|WARNING|INFO|DEBUG error message The admin UI should parse the log accordingly, adding a new column for "level". Also, colourize each row according to its level: Critical (usually causes a critical error bailing out) - BW/WB reversal according to theme Error (usually causes a fatal_exit) - Red Warning (usually causes a warn_exit or a warned attach_message) - Yellow Info (all other non-debugging logs) - Seed Debug - Green Where a level wasn't provided in the log, default to WARNING. Notice should be logged / treated as INFO. Fix error_log and cms_error_log accordingly. Perhaps add a filter box to be able to filter by log level or component, and sorting by date or log level (level column should use language strings to stick a number out in front for proper level sorting, e.g. "0 - Critical") | ||||
| Tags | Roadmap: v11 | ||||
| Attach Tags | |||||
| Time estimation (hours) | |||||
| Sponsorship open | |||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-04-24 18:52 | PDStig | New Issue | |
| 2024-04-24 18:52 | PDStig | Status | Not Assigned => Assigned |
| 2024-04-24 18:52 | PDStig | Assigned To | => user4172 |
| 2024-04-24 18:53 | PDStig | Tag Attached: Roadmap: v11 | |
| 2024-04-24 18:55 | PDStig | Note Added: 0008680 | |
| 2024-04-24 18:59 | PDStig | Description Updated | |
| 2024-04-24 22:22 | PDStig | Status | Assigned => Resolved |
| 2024-04-24 22:22 | PDStig | Resolution | open => fixed |
