README

Active pull collector and CMS admin interface for the SilverStripe 6 monitoring system.
It periodically pulls data from passive client endpoints.

Installation

composer require kalakotra/silverstripe-monitoring-admin
vendor/bin/sake dev/build flush=1

Set Up a New Client

1. On the client site, install kalakotra/silverstripe-monitoring-client
2. Set MONITORING_SECRET_KEY in the client's .env
3. On the admin site, open /admin/monitoring → Add Project
4. Enter:
   • Title – the client name
   • Endpoint URL – https://client.example/
   • Secret Key – the MONITORING_SECRET_KEY value from the client's .env
5. Save, then run a manual pull or wait for cron

Crontab Configuration (on the admin site)

Option A - run sake directly (recommended if you have SSH)

# Every hour - pulls data from all projects
0 * * * * /usr/bin/php /var/www/html/vendor/bin/sake dev/tasks/MonitoringPullTask >> /var/log/monitoring-pull.log 2>&1

Option B - curl the sake task URL

0 * * * * curl -s "https://admin-page.com/dev/tasks/MonitoringPullTask" > /dev/null 2>&1

Option C - cPanel Cron Jobs

Note: dev/tasks is available by default only from 127.0.0.1 or for admins.
For a curl request from an external IP, add that IP to the DevAdmin.allowed_ips YAML configuration.

Manual Pull (for testing)

vendor/bin/sake dev/tasks/MonitoringPullTask

Status Logic

Errors are counted in ConsecutiveErrors and shown next to the status badge as (Nx).

Collected Data

Struktura

src/
├── Admin/
│   └── MonitoringAdmin.php           # ModelAdmin – /admin/monitoring
├── Model/
│   └── Project.php                   # DataObject + status/disk badge
├── Service/
│   └── ProjectPullService.php        # Guzzle pull logika
└── Task/
    └── MonitoringPullTask.php        # BuildTask for cron
_config/
└── routes.yml