[wp-trac] [WordPress Trac] #65232: Abilities API: Add a fast site health summary to `core/get-environment-info`

[WordPress Trac]

#65232: Abilities API: Add a fast site health summary to `core/get-environment-
info`
--------------------------------------+-----------------------
 Reporter:  gziolo                    |       Owner:  gziolo
     Type:  enhancement               |      Status:  assigned
 Priority:  normal                    |   Milestone:  7.1
Component:  Abilities API             |     Version:  6.9
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:
--------------------------------------+-----------------------

Comment (by westonruter):

 Replying to [comment:2 karunyachavan84]:
 > While reviewing this, I noticed that the existing `health-check-site-
 status-result` transient currently only stores aggregate counts (`good`,
 `recommended`, `critical`) and does not persist the underlying issue
 details needed for the proposed `site_health.issues` response (`label`,
 `severity`, `recommendation`).
 > Since the proposal also explicitly requires that `site_health` be
 populated entirely from cached data and never trigger synchronous Site
 Health tests, it seems like we would first need to expand the Site Health
 caching mechanism itself (likely during the scheduled health check cron
 run and related persistence flows) to store normalized actionable issue
 summaries alongside the counts.
 > Just wanted to confirm whether that scope expansion is expected here, or
 if there’s another existing cached source I may be missing.

 Yes, I think we should be caching the entire Site Health results in a
 transient, not just the aggregate counts. This would be very helpful to
 implement #64066. You can see from the [https://github.com/WordPress
 /wordpress-develop/pull/10123 PR] for that ticket, it had to resort to
 adding a new transient specifically for `health_check_page_cache_detail`
 since the results as a whole aren't cached. If we had caching, then this
 wouldn't be needed.

 The transient should also store a timestamp for when the results were
 obtained, so the Ability can indicate how stale the results are. For sites
 that have broken WP-Cron and no traffic, it could be that the results
 become quite stale.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65232#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform