Documentation
Monitoring & Logs
How to read the activity log, monitor provider health, and enable deeper debug logging.
Activity Log
Ingestics maintains a fetch log for every provider run. Access it at Ingestics → Logs (or Ingestics → Activity Log). Run summaries include reconciliation metrics (fetched, created/published, filtered, duplicates, errors, and unaccounted counts).
| Column | Description |
|---|---|
| Time | When the fetch ran. |
| Provider | Which provider triggered the fetch. |
| Status | Success, Partial, or Failed. |
| Items Fetched | Number of items returned by the source. |
| Items Published | Number of items that became posts. |
| Items Skipped | Duplicates or filtered items. |
| Error | HTTP status code or error message if the fetch failed. |
Each log entry also shows event type (fetch / publish / error / license check) and a detail message. Use the log to diagnose why items were skipped (duplicate, filter rejection, no image), why a fetch failed (auth error, timeout, 429), or to confirm the schedule is running.
Click Clear Log to remove all entries (this is the only destructive action — it cannot be undone). On Business, click Export Log to download the full log as a CSV file; Business tier also supports audit export in JSON, CSV, and NDJSON formats.
Provider Health Monitoring Lite+
- Go to Ingestics → Dashboard or Providers tab. The Health Monitor panel shows a table of all providers.
- For each provider you can see: last fetch timestamp, last fetch status (success / warning / error), response latency (ms), total items fetched, total items published, and consecutive failure count.
- A provider flagged with a red status has failed its last fetch. Check the Activity Log for the specific error message.
- Use the health data to identify providers that are consistently slow (high latency) or unreliable (high failure count) and adjust their settings or disable them accordingly.
Debug & Logs
For deeper debugging, enable WP_DEBUG and WP_DEBUG_LOG in wp-config.php. Ingestics writes detailed error traces to the WordPress debug log.