內容簡介
Honeylog 是一款多檔案的 WordPress 外掛，能將前端請求批次處理並轉換為 JSON 隊列，並發送至 Honeylog。此外掛適用於自我託管及傳統的管理型 WordPress，並提供簡單的事件追蹤功能。
【主要功能】
• 追蹤前端頁面請求及 .xml、.txt 網址
• 寫入事件至本地 NDJSON 隊列檔案
• 每 60 秒自動執行排程任務，批次發送請求
外掛標籤
開發者團隊
原文外掛簡介
Honeylog WordPress Plugin
Multi-file WordPress plugin that batches frontend requests into a JSON queue and flushes to Honeylog.
This client targets self-hosted and conventional managed WordPress. It is not
the complete integration for WordPress VIP, where edge cache hits do not execute
PHP and the uploads filesystem is not a durable local queue. Use
clients/wordpress-vip-s3 for VIP.
Behavior
Tracks HTML/XHTML frontend responses regardless of the request Accept header, plus .xml and .txt URLs (excludes wp-admin pages).
Keeps frontend responses without an explicit Content-Type, including redirects.
Writes each event to a local NDJSON queue file.
Serializes queue writes and rotation using a blocking filesystem lock on local storage.
Schedules a flush every 60 seconds through WP-Cron; actual execution depends on the cron runner.
Sends queued events in batches of up to 100.
Warns administrators when automatic WP-Cron execution is disabled.
Plugin Files
honeylog-ingestion.php: bootstrap and WordPress hooks
includes/honeylog-constants.php: constants + option sanitizers
includes/honeylog-batching-utils.php: queue file lock, enqueue/snapshot/requeue/flush
includes/honeylog-request-utils.php: request capture + HTTP batch sender
includes/honeylog-settings.php: admin settings page
includes/honeylog-debug.php: persistent debug log + last status/error helpers
Settings
Go to Settings -> Honeylog:
Token
Site Domain (optional)
The ingestion endpoint is fixed to https://api.honeylog.io/events.
Debugging
Debug log is written to:
wp-content/uploads/honeylog-ingestion/debug.log when available
fallback: wp-content/honeylog-ingestion-debug.log
Reliable scheduling and cache coverage
On low-traffic or cached sites, configure a system cron to run due WordPress
cron events every minute. The 60-second schedule is not a delivery deadline.
See docs/clients/wordpress-installation.md for a WP-CLI example.
Requests served entirely by a page cache or CDN without loading the plugin
cannot be captured; use server/CDN log ingestion for those visits.
The queue requires a writable local filesystem with working flock support.
