Gregius Data – Logs

Overview

Gregius Data captures operational records from every component — RAG, Search, Sync, Vectors, Connections, Models, Cron, and System — into a single centralized log. Each entry carries a severity level, a component classification, and a timestamp, with sensitive data masked automatically before storage. Site administrators can view, filter, export, and manage these logs through a dedicated dashboard interface with configurable retention.

Prerequisites

• WordPress 6.9+ with Gregius Data plugin installed and activated

---

Understanding Logs

Every Gregius Data component — RAG, Search, Sync, Vectors, Connections, Models, Cron, and System — writes operational records to a central log table. Each entry captures severity, source, timestamp, and optional contextual data.

Log levels and components

Logs are categorized by severity level and by component:

Level	Meaning
Debug	Detailed diagnostic information (only shown when debug mode is active)
Info	Normal operational events
Warning	Unexpected but non-critical conditions
Error	Failures that affect a specific operation
Critical	Failures that require immediate attention

Component	Source
RAG, Search, Sync, Vectors	Core pipeline components
Connection, Model	Data connection and AI model operations
Cron	Scheduled task execution
System	Plugin lifecycle and administrative events

Sensitive data protection

When components include contextual data with their log entries, the system automatically masks sensitive information such as API keys, passwords, secrets, tokens, and authorization headers before storing. Usage metrics (token counts) are preserved for operational insight.

---

How to: View and Export Logs

The Logs dashboard provides a central interface for browsing and exporting operational records with full filtering and pagination.

View logs

You can browse logs with these filters:

• Level – Filter by severity (debug, info, warning, error, critical)
• Component – Filter by source (RAG, Search, Sync, etc.)
• Connection – Filter by specific data connection
• Date range – Narrow by start and end date
• Search – Find matching messages

Results are paginated and sortable by timestamp, level, or component. Each log entry shows the severity level, component badge, timestamp, message, and optional context that can be expanded for detail.

Export logs

You can export filtered log data as CSV or JSON. The export respects all active filters — only the matching records are included. This is useful for sharing with support teams, importing into external analysis tools, or creating operational reports.

Tips

• Use level and component filters together to quickly isolate specific issues
• Debug-level logs are written only when debug mode is active — enable it temporarily during troubleshooting
• Exported files include the same data visible in the dashboard with your current filters applied

---

How to: Manage Log Retention

Log data accumulates over time. The system provides both manual and automatic retention controls to manage storage.

Manual purge

You can delete log entries older than a specified number of days. Enter a day threshold and confirm — records older than that threshold are removed from the current site’s log table. Interaction records are never affected by log purge operations.

Automatic retention

A daily scheduled task automatically removes logs older than your configured retention period. This ensures logs do not grow indefinitely without requiring manual intervention. Each site in a multisite network manages its own retention schedule independently.

Tips

• Set retention to match your operational review cadence — 30 days is a reasonable starting point
• Manual purge applies immediately; automatic retention runs once per day
• Log purge only affects the log table — interaction history and usage records are preserved

---

How to: Configure Log Settings

Control how logging behaves through the settings panel.

Configure settings

Setting	What it does
Logging enabled	Turns all log writes on or off
Minimum log level	Only messages at this level or higher are recorded
Retention days	How long to keep log entries before automatic purge

Changes take effect immediately. Adjust the minimum level higher during normal operation and lower during troubleshooting.

Tips

• Disable logging only if you are certain you do not need operational records — leave it enabled for routine maintenance visibility
• Raise the minimum level to “warning” during normal operation to reduce volume; lower to “debug” when investigating issues
• Retention settings apply to both manual and automatic purge operations

---

Permissions

Area	Route	Who can use it
View logs	Dashboard logs page, REST list, CLI list	Administrators only
Export logs	REST export, CLI export	Administrators only
Purge logs	REST purge, CLI purge	Administrators only
Configure settings	REST settings view and update	Administrators only

---