Frequently Asked Questions

For WordPress: install the plugin, click Connect, done. Metrics appear within minutes. No server configuration, no code changes.

For Drupal: install the module via Composer, enable it, configure the API key. Same result - events start flowing immediately.

For Vault: configure audit log output to file or syslog, connect via Fluentd or file tail. Typically 30–60 minutes with our setup guide.

No. The plugin buffers events locally in a JSONL file and dispatches them asynchronously - either via WordPress cron or on the shutdown hook. It adds less than 5ms to request time. Events are sent in batches, not per-request.

The plugin has no external dependencies and does not make blocking HTTP calls during page rendering.

No. The WordPress plugin and Drupal module hook into core events automatically. You install, connect, and see metrics. No code modifications, no theme changes, no configuration files to edit.

Yes. The Starter plan is free and includes core metrics for one site with 7-day retention. No credit card required. Request access.

Logystera reads structured log events from WordPress, Drupal, and Vault. It derives metrics automatically from those events: cron runs, email delivery, PHP errors, authentication attempts, slow queries, queue depths, API errors - over 30 signal types across supported platforms.

You do not write queries. Metrics are derived from pre-built definitions that ship with the plugin.

Uptime monitors check if your site responds to HTTP requests. They say "200 OK" and declare health.

Logystera watches what the application actually does. Your site can return 200 while wp_mail() silently fails. Cron can be stopped for 422 days while the site loads normally. Uptime monitors miss all of this. Logystera does not.

APMs track performance: response times, slow queries, error rates. Useful, but not focused on failure detection.

Logystera focuses on what broke and why - especially silent failures. It uses log events as the source of truth, derives metrics from them, applies rules, and alerts with evidence. APMs tell you a site is slow. Logystera tells you that email delivery stopped working 3 days ago.

No. Logystera ships with pre-built alerts for the most common WordPress, Drupal, and Vault failures. They're active the moment you install — no configuration required. Paid plans also include custom detection rules tailored to your environment, which our team builds and maintains for you.

Alerts are auditable, hot-reloadable, and update without redeploying.

Only structured event metadata: event type, timestamp, operational context (HTTP status, response time, error severity, etc.). We do NOT collect full log bodies, user content, page content, form submissions, or any personal data from your visitors.

See the Privacy Policy for details.

All data is processed and stored in EU (Frankfurt, eu-central-1). PostgreSQL, Redis, and VictoriaMetrics all run in EU. No data leaves the region. US region available on request for enterprise plans.

Your data is retained for the duration of your retention period after cancellation. After that, it is permanently deleted from all storage. You can export your data at any time before cancellation.

WordPress 6.0 and later. PHP 7.4+. The plugin is tested on 6.0, 6.1, 6.2, 6.3, 6.4, 6.5, 6.6, 6.7.

Drupal 10 and Drupal 11. PHP 8.1+. Available via Composer.

Yes. Each site is an entity in Logystera with its own API key. You manage them all from one dashboard. The Professional plan supports up to 25 sites. Enterprise is unlimited.

WooCommerce monitoring is on our roadmap. Vote for it on the integrations page. In the meantime, the WordPress plugin captures order-related errors and email delivery issues that affect WooCommerce.