Project

General

Profile

Actions

Feature #24009

closed

System health status self monitoring

Added by Ingo Renner about 14 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Category:
Reports
Target version:
-
Start date:
2010-11-10
Due date:
% Done:

0%

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

Description

In an attempt to bring self-monitoring to TYPO3 this is the first step to achive this.
When opening the status report the highest severity of all status checks is determined and stored in TYPO3's registry.

When an admin logs in the registry is checked and if a severity higher than OK is found the warning box is enabled reporting that issues have been found, linking to the status report for more details.

By clicking the link the report is shown and the highest severity is recorded again. Now the user has seen what issues have been found and will go to fix them. Once fixed, he comes back to confirm the fix with the status report, again recording the highest severity.

Once all issues are fixed the recorded highest severity is equal or below the threshold triggering the warning box, making it disappear.

(issue imported from #M16337)


Files

16337.diff (7.52 KB) 16337.diff Administrator Admin, 2010-11-10 20:48

Related issues 3 (0 open3 closed)

Related to TYPO3 Core - Feature #24010: Scheduler task to regularly execute the status report checksClosedIngo Renner2010-11-10

Actions
Related to TYPO3 Core - Feature #24011: Overwrite the "start in module" setting of admin users when system health issues have been detectedClosed2010-11-10

Actions
Related to TYPO3 Core - Feature #24572: Notification Emails for system status updatesClosedIngo Renner2011-01-14

Actions
Actions #1

Updated by Ingo Renner about 14 years ago

committed to trunk (4.5) in r9356

Actions #2

Updated by Benni Mack about 6 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF