Every event the WordPress plugin captures.

Raw, typed signals captured through WordPress hooks. All intelligence lives in the Logystera processor — your plugin just emits events.

What the plugin captures

24 signal types across 8 categories: HTTP & requests, authentication, cron & scheduled tasks, PHP errors, environment & state, content & uploads, performance, and 8 database error subtypes. Every one is captured automatically — no configuration.

HTTP & Requests

http.request

Once per request at shutdown — method, URI, status, execution time, peak memory, referer.

rest.request

Every REST API response with matched route and namespace.

wp.search

Frontend search queries (sanitized, truncated).

Authentication

auth.attempt

Every login attempt — success and failure. Username is HMAC-hashed, never sent in clear.

auth.logout

When a user logs out.

Cron & Scheduled Tasks

cron.run

When WordPress processes a cron batch (DOING_CRON).

wp.cron (health_check)

Full queue snapshot every 5 minutes: total, overdue, max and average delay, overdue hooks.

wp.cron (missed_schedule)

Emitted when a scheduled post fails to publish at its time, with post_id and delay.

PHP Errors

php.warning

Every PHP warning, notice, or deprecated error with file, line, and source attribution (plugin/theme/core).

php.fatal

Fatal errors detected at shutdown.

memory_near_limit

Peak PHP memory exceeds 90% of WP_MEMORY_LIMIT.

Environment & State

wp.environment

Snapshot every 15 minutes — WP version, PHP version, plugins, theme, multisite, memory limits, hosting provider.

wp.state_change

Plugin, theme, and core lifecycle events — activate, deactivate, update, switch.

wp.integrity

When wp-config.php or .htaccess hash changes (checked hourly).

Content & Uploads

upload_blocked

When WordPress blocks a file upload due to dangerous extension.

Performance

perf.hook_timing

Slow WordPress hooks (>50ms), sampled at 10% of requests, with plugin/theme attribution.

Database Errors

db_error

Generic database error fallback.

db_deadlock

InnoDB deadlock detected and rolled back.

db_lock_timeout

Query exceeded lock wait timeout.

db_connection_failed

Cannot connect to MySQL.

db_connection_limit

Too many connections.

db_table_crashed

Table is marked as crashed and needs repair.

db_disk_full

Disk full error from the database host.

db_access_denied

MySQL access denied for the configured user.

All signals are bounded: 200 events per request hard cap, per-type rate limits, 10,000-event pending buffer. The plugin never becomes an unbounded source of data. Usernames are HMAC-hashed. SQL queries are never transmitted. See the full signals reference on docs.logystera.com for payload schemas and privacy guarantees.

From signals to insight

You send events. We send you answers.

Signals are raw — a single login attempt, a single PHP warning, a single cron tick. The Logystera processor aggregates and correlates them into pre-built metrics and alerts. You do not write queries; you read alerts.

Metric

wp_auth_failed_total

From auth.attempt where success=false.

Metric

wp_cron_overdue_ratio

From the wp.cron health_check payload.

Alert

PHP fatal spike

Triggered on php.fatal rate over baseline.

Alert

Brute-force attack

From clustered auth.attempt failures by IP.

Alert

Config file tampering

From wp.integrity hash changes.

Alert

Slow plugin regression

From perf.hook_timing attributed to a single plugin.

Logystera Logystera
Monitoring for WordPress and Drupal sites. Install a plugin or module to catch silent failures — cron stalls, failed emails, login attacks, PHP errors — before users report them.
Company
Copyright © 2026 Logystera. All rights reserved.