Peter Booker

PromPress tracks various website and WordPress related metrics for collection by <a href="https://prometheus.io/" rel="nofollow ugc">Prometheus</a>, which allows you to monitor your site’s performance and health. You can even setup dashboards with <a href="https://grafana.com/" rel="nofollow ugc">Grafana</a> and/or setup alerting via <a href="https://prometheus.io/docs/alerting/latest/alertmanager/" rel="nofollow ugc">Prometheus Alertmanager</a>.
(Note: Requires Object Caching via Redis to be active, so that the plugin can store metrics.)
We track a range of Website and WordPress specific metrics:
<ul>
<li>Request Count</li>
<li>Request Duration</li>
<li>Request Peak Memory Usage</li>
<li>External Request Duration</li>
<li>Query Count</li>
<li>Query Duration</li>
<li>Plugin Updates</li>
<li>Theme Updates</li>
<li>Emails Sent</li>
<li>User Count</li>
<li>Post Count</li>
<li>Option Count</li>
</ul>
This gives you the ability to monitor the performance of your website over time and get an early warning of potential problems, like your site sending a lot of emails or the post count increasing a lot.
We purposefully avoid general software and/or server level metrics which are better handled outside of the website, like detailed database metrics which is better handled via the <a href="https://github.com/prometheus/mysqld_exporter" rel="nofollow ugc">mysqld exporter</a>.

PromPress

Monitor the performance and health of your site with Prometheus.

SiMULA

Simula Security Telemetry for Wordfence exports Wordfence security telemetry in two forms:
<ul>
<li>Prometheus metrics for the node_exporter textfile collector that can be scraped by Prometheus</li>
<li>A local incident log containing blocked Wordfence requests that can be shipped with Grafana-Alloy</li>
</ul>
This plugin is intended for WordPress sites that already use Wordfence and Prometheus-based infrastructure. Instead of exposing a public metrics endpoint from WordPress, the plugin writes local files that node_exporter and log-based tooling can consume.
By default, the plugin runs a fast collector every 15 minutes and a slow collector hourly using WP-Cron. It supports:
<ul>
<li>Exporter health and plugin metadata metrics</li>
<li>Configurable cron interval</li>
<li>Separate fast and slow collector intervals</li>
<li>Per-metric-family enable or disable controls</li>
<li>Blocked event counters and recent activity windows</li>
<li>Blocked event counts by HTTP status code over the last 24 hours</li>
<li>Failed login, rate-limited, and brute-force activity windows</li>
<li>Current lockout counts for IPs and users</li>
<li>Wordfence two-factor status and protected user counts</li>
<li>Scan issue counts by severity</li>
<li>Malware, file change, and vulnerable component findings</li>
<li>Top blocked attack sources by country and normalized IP range</li>
<li>Incident log export for newly observed blocked requests</li>
<li>Incident privacy controls for IPs, URLs, referers, user agents, and internal traffic</li>
<li>Manual export and incident cursor reset from the admin UI</li>
<li>Current exporter and incident state visibility in the admin UI</li>
<li>Optional JSON Lines incident output</li>
<li>WP-CLI exports for system cron</li>
<li>Source freshness and WordPress/Wordfence posture metrics</li>
<li>A ready-to-import Grafana dashboard and sample Prometheus alert rules</li>
</ul>
Blocked events are currently identified from the Wordfence hits table where:
<ul>
<li>action matches blocked:*</li>
<li>or the HTTP status code is 403 or 503</li>
</ul>
The plugin includes an admin settings screen under Settings > Security Telemetry, where you can:
<ul>
<li>Enable or disable the exporter master switch</li>
<li>Choose the export cron interval</li>
<li>Choose the slow collector interval</li>
<li>Set the .prom output path</li>
<li>Set a custom metric prefix</li>
<li>Set a custom site label</li>
<li>Enable or disable individual metric families</li>
<li>Enable or disable incident log export</li>
<li>Set the incident log path</li>
<li>Choose text or JSON Lines incident output</li>
<li>Limit the number of incidents appended per run</li>
<li>Configure incident IP privacy and field-dropping filters</li>
<li>Add an optional retention note to emitted incident events</li>
<li>Trigger a manual export</li>
<li>Reset the incident cursor for backfill</li>
<li>Review current exporter and incident state</li>
</ul>

Simula Security Telemetry for Wordfence

Export metrics from Wordfence into a node_exporter textfile collector .prom file and append incidents detected by wordfence to a local log file.

PromPress vs Simula Security Telemetry for Wordfence