{"id":345027,"date":"2026-08-27T01:14:48","date_gmt":"2026-08-27T01:14:48","guid":{"rendered":"https:\/\/wordpress.org\/plugins\/liaison-site-health-monitor\/"},"modified":"2026-09-03T07:46:54","modified_gmt":"2026-09-03T07:46:54","slug":"liaison-site-health-monitor","status":"publish","type":"plugin","link":"https:\/\/wordpress.org\/plugins\/liaison-site-health-monitor\/","author":18784765,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"1.0.0","stable_tag":"1.0.0","tested":"7.0.6","requires":"6.0","requires_php":"7.4","requires_plugins":null,"header_name":"liaison site health monitor","header_author":"liason","header_description":"Developer-focused WordPress diagnostic plugin using WordPress core SAVEQUERIES for site health metrics and slow query profiling.","assets_banners_color":"","last_updated":"2026-09-03 07:46:54","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"https:\/\/github.com\/liaisontw\/liaison-site-health-monitor","header_author_uri":"https:\/\/github.com\/liaisontw\/","rating":0,"author_block_rating":0,"active_installs":0,"downloads":127,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation","changelog"],"tags":{"1.0.0":{"tag":"1.0.0","author":"liaison","date":"2026-09-03 07:46:54","revision":3679243}},"upgrade_notice":[],"ratings":[],"assets_icons":[],"assets_banners":[],"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.0"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3679243,"resolution":"1","location":"assets","locale":"","width":1163,"height":548},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3679243,"resolution":"2","location":"assets","locale":"","width":1096,"height":538}},"screenshots":{"1":"Site Health Dashboard<\/strong>","2":"Slow DB Queries (Top 10)<\/strong>"}},"plugin_section":[],"plugin_tags":[153,247,23044,151481,259861],"plugin_category":[54,59],"plugin_contributors":[200952],"plugin_business_model":[],"class_list":["post-345027","plugin","type-plugin","status-publish","hentry","plugin_tags-database","plugin_tags-performance","plugin_tags-profiling","plugin_tags-site-health","plugin_tags-slow-query","plugin_category-security-and-spam-protection","plugin_category-utilities-and-tools","plugin_contributors-liaison","plugin_committers-liaison"],"banners":[],"icons":{"svg":false,"icon":"https:\/\/s.w.org\/plugins\/geopattern-icon\/liaison-site-health-monitor.svg","icon_2x":false,"generated":true},"screenshots":[{"src":"https:\/\/ps.w.org\/liaison-site-health-monitor\/assets\/screenshot-1.png?rev=3679243","caption":"Site Health Dashboard<\/strong>"},{"src":"https:\/\/ps.w.org\/liaison-site-health-monitor\/assets\/screenshot-2.png?rev=3679243","caption":"Slow DB Queries (Top 10)<\/strong>"}],"raw_content":"\n

liaison site health monitor<\/strong> is an admin-only diagnostic tool built for developers and operators who want clear visibility into WordPress performance characteristics<\/strong> without introducing undocumented runtime behavior.<\/p>\n\n

This plugin intentionally requires SAVEQUERIES<\/code> to be enabled in wp-config.php<\/code><\/strong>, and does not attempt to bypass or reimplement WordPress core database instrumentation.<\/p>\n\n

Why this matters<\/p>\n\n

Rather than intercepting or mutating the database layer, this plugin:<\/p>\n\n

    \n
  • Respects WordPress\u2019s established debugging contract<\/li>\n
  • Uses core-supported query timing data<\/strong><\/li>\n
  • Makes performance trade-offs explicit and auditable<\/strong><\/li>\n
  • Avoids fragile hooks into internal execution paths<\/li>\n<\/ul>\n\n

    Requirements<\/h3>\n\n

    To enable slow query monitoring, the following must<\/strong> be set in wp-config.php<\/code>:<\/p>\n\n

    define( 'SAVEQUERIES', true );<\/p>\n\n

    This constant must be defined before WordPress bootstrap<\/strong>, as required by core.<\/p>\n\n

    If SAVEQUERIES<\/code> is not enabled, slow query monitoring will be automatically disabled and the plugin will operate in site health metrics\u2013only mode<\/strong>.<\/p>\n\n

    Features<\/h3>\n\n
      \n
    1. Site Health Metrics<\/li>\n<\/ol>\n\n
        \n
      • PHP memory usage<\/li>\n
      • Aggregate database query time<\/li>\n
      • REST API response latency<\/li>\n
      • Active plugin count<\/li>\n

      • WordPress version<\/p>\n\n

          \n
        1. Slow Query Monitoring (SAVEQUERIES-based)<\/li>\n<\/ol><\/li>\n

        2. Uses $wpdb->queries<\/code> as the authoritative source<\/p><\/li>\n

        3. Automatic slow query detection via time thresholds<\/li>\n
        4. Query normalization and aggregation<\/li>\n
        5. Persistent storage for historical analysis<\/li>\n

        6. Zero interference with query execution<\/p>\n\n

          Slow Query Monitoring<\/p><\/li>\n<\/ul>\n\n

            \n
          1. WordPress records query timing into $wpdb->queries<\/code> (core behavior).<\/li>\n
          2. On admin page load:<\/li>\n<\/ol>\n\n
              \n
            • Plugin inspects recorded queries<\/li>\n

            • Filters queries exceeding the configured threshold<\/p>\n\n

                \n
              1. Slow queries are:<\/li>\n<\/ol><\/li>\n

              2. Normalized (values stripped)<\/p><\/li>\n

              3. Stored in a plugin-owned table\n\n
                  \n
                1. Aggregated results are displayed in the dashboard.<\/li>\n<\/ol><\/li>\n<\/ul>\n\n

                  Why SAVEQUERIES Is Required<\/h3>\n\n

                  WordPress deliberately gates query timing behind SAVEQUERIES<\/code> to ensure developers explicitly opt into performance overhead<\/strong>.<\/p>\n\n

                  This plugin embraces that design decision:<\/p>\n\n

                    \n
                  • No attempt to override $wpdb<\/code><\/li>\n
                  • No undocumented filters or runtime mutation<\/li>\n
                  • No silent performance impact<\/li>\n<\/ul>\n\n

                    Instead, it provides:<\/p>\n\n

                      \n
                    • Transparent prerequisites<\/li>\n
                    • Predictable behavior<\/li>\n
                    • Alignment with WordPress core debugging philosophy<\/li>\n<\/ul>\n\n

                      This makes the plugin suitable for development, staging, and controlled production diagnostics<\/strong>.<\/p>\n\n

                      Security Considerations<\/h3>\n\n
                        \n

                      • Admin-only access<\/strong><\/p>\n\n

                          \n
                        • Dashboard restricted to privileged users.<\/li>\n<\/ul><\/li>\n

                        • No sensitive data exposure<\/strong><\/p>\n\n

                            \n
                          • Query values are normalized before storage.<\/li>\n<\/ul><\/li>\n

                          • No runtime mutation<\/strong><\/p>\n\n

                              \n
                            • Does not alter database execution flow.<\/li>\n<\/ul><\/li>\n

                            • Clear uninstall behavior<\/strong><\/p>\n\n

                                \n
                              • Plugin-owned tables removed on uninstall.<\/li>\n<\/ul><\/li>\n<\/ul>\n\n

                                Trade-offs \/ Limitations<\/h3>\n\n

                                Pros<\/p>\n\n

                                  \n
                                • Uses WordPress-supported debugging mechanisms<\/li>\n
                                • Easy to reason about and audit<\/li>\n
                                • No fragile DB-layer interception<\/li>\n
                                • Clear performance cost model<\/li>\n

                                • Ideal for learning and diagnosis<\/p>\n\n

                                  Cons<\/p><\/li>\n

                                • Requires SAVEQUERIES<\/code> to be enabled<\/p><\/li>\n

                                • Higher overhead than production-safe profilers<\/li>\n
                                • Not intended for always-on monitoring<\/li>\n
                                • Less suitable for high-traffic production sites<\/li>\n<\/ul>\n\n

                                  Testing<\/h3>\n\n
                                    \n
                                  • Tested with SAVEQUERIES<\/code> enabled and disabled.<\/li>\n
                                  • Verifies graceful degradation when unavailable.<\/li>\n
                                  • Manual validation of query timing accuracy.<\/li>\n
                                  • No dependency on non-core WordPress behavior.<\/li>\n<\/ul>\n\n\n
                                      \n

                                    1. Add the following to wp-config.php<\/code>:<\/p>\n\n

                                      define( 'SAVEQUERIES', true );<\/p><\/li>\n

                                    2. Upload the plugin to wp-content\/plugins\/liaison-site-health-monitor<\/code>.<\/p><\/li>\n

                                    3. Activate via WordPress admin.<\/p><\/li>\n

                                    4. Navigate to:\nTools \u2192 Site Health<\/strong><\/p><\/li>\n

                                    5. Review site metrics and slow query data.<\/p><\/li>\n<\/ol>\n\n\n

                                      1.0.0<\/h4>\n\n
                                        \n
                                      • Provides site health metrics and database slow query profiling<\/li>\n
                                      • SAVEQUERIES-based slow query analysis<\/li>\n
                                      • Introduced query normalization & aggregation<\/li>\n
                                      • Added explicit requirement documentation<\/li>\n
                                      • Refined admin dashboard<\/li>\n
                                      • Clarified architectural trade-offs<\/li>\n<\/ul>","raw_excerpt":"Developer-focused WordPress diagnostic plugin using WordPress core SAVEQUERIES for site health metrics and slow query profiling.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/345027","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=345027"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/liaison"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=345027"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=345027"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=345027"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=345027"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=345027"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=345027"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}