See llms.txt for all machine-readable content.

Back to Templates

Monitor backup and sync logs with Google Cloud Storage, GitHub, Gmail, OpenAI, and GLPI

Created by

Created by: Paolo Ronco || paoloronco
Paolo Ronco

Last update

Last update 10 days ago

Categories

Quick overview

Monitor backup and synchronization jobs through execution logs stored in Google Cloud Storage. This n8n workflow checks expected logs against a GitHub configuration, detects missing or failed runs, analyzes log contents with OpenAI, and sends Gmail alerts when attention is needed.

How it works

  1. Runs on a daily schedule after the configured log upload window.
  2. Lists log files in a date-based Google Cloud Storage (GCS) folder.
  3. Retrieves the expected job list from a GitHub-hosted sync-jobs.json file.
  4. Checks which required logs should exist based on their configured frequency and schedule.
  5. Sends a Gmail alert when an expected log is missing.
  6. Downloads available logs and checks execution markers, return codes, errors, and warnings.
  7. Supports structured rsync/rclone logs and the specific OneDrive text format recognized by the parser.
  8. Uses OpenAI to identify additional actionable issues in log contents.
  9. Sends separate Gmail notifications for execution failures and qualifying AI findings.

Setup

  1. Import the workflow JSON into n8n and leave it inactive during configuration.
  2. Set your GCS bucket and hostname in Set_Context.
  3. Configure the bucket in both GCS nodes and connect your GCS credentials.
  4. Set your GitHub username, repository, and manifest path in GitHub: sync-jobs.json.
  5. Create or adapt sync-jobs.json to list the expected log filenames and schedules.
  6. Configure your backup scripts to generate compatible logs and upload them to the expected GCS folder.
  7. Connect Gmail credentials and replace the example recipient in all alert nodes.
  8. Connect OpenAI credentials and confirm the selected model is available.
  9. Review the schedule, timezone, and log upload cutoff for your environment.
  10. Test successful, missing, and failed logs before activating the workflow.

Requirements

  • An n8n instance with access to the required integrations.
  • A Google Cloud Storage bucket containing uploaded backup/sync execution logs.
  • A GitHub repository with a valid sync-jobs.json configuration file.
  • Backup or sync jobs that generate logs in a format supported by the workflow.
  • Google Cloud Storage, GitHub, Gmail, and OpenAI credentials.
  • A configured log upload process that completes before the monitoring schedule.

Customization

  • Change the GCS bucket, hostname, log folder structure, and monitoring schedule.
  • Add or remove monitored jobs in sync-jobs.json.
  • Configure daily, weekly, or monthly expectations according to the workflow's scheduling rules.
  • Adapt the log parser to additional backup tools or log formats.
  • Adjust the deterministic checks and AI notification thresholds.
  • Customize email recipients, subjects, and notification content.
  • Use any backup destination supported by your backup tool; GCS is used here to collect the execution logs.

Additional info

This workflow monitors backup and sync executions; it does not run the backup jobs. The included configuration expects logs in GCS and uses Gmail for notifications, including AI findings. The GitHub manifest and the log naming convention must match your environment. Weekly and monthly checks follow the workflow's implemented scheduling assumptions rather than a general-purpose cron interpreter.

Complete Setup Guide & Technical Documentation

Professional Services & Consulting

For professional consulting, tailored solutions, or collaboration opportunities, feel free to get in touch.

Email: [email protected]
Website: https://paoloronco.it