#103600Separate Status to a specific report
Description
The reports extension allows a administrator to see a report of the system.
It allows a integrator to create a status (implement StatusProviderInterface) for a part of the system.
Each Status is picked up by the core System Status report and shows it.
A integrator can also create a own report and render a output for that.
This own report can use the same Registry as the System Report does, but can’t filter out it’s own reports.
All StatusProviderInterface implementation are shown in the default System Report.
Places to improve:
A StatusProviderInterface can be attached to a certain report (system, piwik)
The getIdentifier from ReportInterface can be used to filter by a certain report.
As `AsStatus(report: ‘piwik’)` annotation could be used and take precedence over the `StatusProviderInterface` registration.
Improve work for output of a report
- Allow for a generic way of rendering reports with status, attached to that specific report.
- Allow for overriding the generic/default rendering
Attached image shows the example of multiple reports:
!Screenshot 2024-04-11 at 10.38.27.png!
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Related issues 1
Files 1
History 4
-
Benni Mack changed target version <span data-processor="relativetime" data-value="2024-10-15T09:46:20+00:00" > 10/15/24, 09:46 </span>
-
Georg Ringer commented and changed status
NewNeeds Feedback <span data-processor="relativetime" data-value="2026-10-18T13:29:30+00:00" > 10/18/26, 13:29 </span> -
Georg Ringer changed Related to #107791 <span data-processor="relativetime" data-value="2026-10-18T13:29:35+00:00" > 10/18/26, 13:29 </span>
-
Georg Ringer commented and changed status
Needs FeedbackClosed <span data-processor="relativetime" data-value="2026-11-12T18:04:42+00:00" > 11/12/26, 18:04 </span>closing as lack of feedback. feel free to reopen if still valid for you in v14+
This issue is rather old. With #107791 (v14) the situation changed:
ReportInterfaceandRequestAwareReportInterfaceare gone, and a custom report is now a regular backend submodule registered inConfiguration/Backend/Modules.php(parentsystem_reports) with its own controller.Such a controller can run its own checks and render its own output. It does not need to use the
StatusProviderInterfaceregistry at all, so the original problem (a custom report cannot filter out its own status providers from the system report) most likely no longer applies.Is this still relevant for you? If so, please describe what cannot be solved with a custom submodule and its own controller today. Without further information this can probably be closed.
Setting the status to “Needs Feedback”.