WordPress Features
30+ signal types, multiple dashboards, 17+ alert rules, Insights - all from a lightweight plugin with no code changes.
What the plugin captures
The Logystera WordPress plugin hooks into core events and ships structured JSON. No code changes. Under 5ms overhead. Async dispatch.
HTTP
- Every request (admin + frontend)
- Response time and status code
- Route and method
- Bot vs human traffic
- Cache hit/miss
- Every wp_mail() call
- Success and failure status
- SMTP error messages
- Delivery rate as metric
Cron
- Every cron execution
- Hook names and duration
- Missed and late cron
- Execution frequency
Auth
- Login attempts (success/fail)
- Targeted usernames
- Endpoint (wp-login, xmlrpc, REST)
- Brute-force spike detection
Errors
- PHP errors by severity
- Source file and line
- Deprecation warnings
- Fatal errors caught by handler
REST API
- Requests by route
- Authentication method
- Error rates per endpoint
- Namespace usage
Config
- Plugin activate/deactivate
- Theme switches
- Option changes
- Update events
Performance
- Memory per request
- Slow request tracking
- Admin vs frontend split
- Hook execution time
How detection works
One real example. A single log pattern, the match, and the alert it produces.
1. Your logs say this
[2026-04-10 14:33] wp_mail called [email protected] subject="Contact form submission" status=true [2026-04-10 14:35] wp_mail called [email protected] subject="Password reset" status=true [2026-04-10 14:41] wp_mail called [email protected] subject="Invoice #4721" status=true ...47 calls in 24 hours
All 47 return status=true. Your code thinks email works.
2. The pattern matches this
rule: email_delivery_silent_failure when: wp_mail events > 5 in 1h and: smtp_relay_acknowledged = 0 then: silent_failure alert
Pre-built pattern. No configuration. Tuned on real WordPress failures.
3. You get this alert
⚠ Email delivery failing silently — 0 relays accepted in 24h First symptom: 2026-04-10 14:33 Affected site: blog.example.com Evidence: 47 wp_mail calls, 0 SMTP relays acknowledged Probable cause: SMTP plugin misconfigured or relay service down [View full log evidence →] [Silence for 1h]
Delivered via email, Slack, or webhook. Ships with the exact log lines that triggered it.
This is one of 30+ pre-built patterns. The same approach applies to cron stalls, auth attacks, stuck queues, PHP fatals, and config drift.
Dashboards
Overview
Requests, error rate, email delivery, cron status, auth patterns - everything at a glance.
FreePerformance
Memory by route, cache hit ratio, slow hooks, admin vs frontend response times.
PaidSecurity
Failed login attempts, brute-force patterns, targeted usernames, endpoint breakdown.
PaidCron & Email
Cron execution frequency, duration trends, email delivery rate, SMTP error tracking.
PaidPre-built WordPress alerts
Every alert below is already configured — tuned against real WordPress production failures. Every alert includes the exact log events that triggered it.
Custom detection rules tailored to your environment on paid plans.
Insights
Automated analysis that goes beyond thresholds. Pattern detection, baseline comparison, anomaly identification.
Fatal Errors Detected
Identifies new fatal errors and correlates with recent changes.
FreeLogin Failure Spike
Detects unusual spikes in failed login attempts vs baseline.
FreeXML-RPC Activity Detected
Flags unexpected XML-RPC usage that may indicate attack vectors.
FreeAuth Attempt Surge
Detects coordinated authentication attempts across endpoints.
PaidMemory Near Limit
Alerts when request memory approaches PHP memory limit.
PaidSlow Query Rate Elevated
Identifies periods where slow request percentage exceeds baseline.
PaidCapability Check Failures
Detects repeated permission check failures that may indicate privilege escalation attempts.
PaidLogin Failure Surge vs Baseline
Compares current failure rate against historical baseline to detect anomalies.
Paid