Docker-deployed operations monitoring

Automation Scheduling & Execution

ASE lets you declare expected automation schedules, receive real execution events through an API, and spot missing, late, failed, or unmatched runs from a clear operations timeline.

Install with Docker Compose View Docker Hub

ASE EasyAdmin timeline showing planned versus actual executions, filters, health cards, history, and configuration panels.

Mobile view of the ASE timeline with status cards, filters, legend, and execution history.

Scheduled jobs fail quietly more often than they should.

Cron and automation platforms usually know when they started something, but not always whether the business process completed. Teams often discover missing jobs from downstream failures after the useful response window has already closed.

ASE focuses on the operational question: did the expected run happen on time, and if it happened, did it succeed?

Operating model

Declare what should happen. Ingest what did happen.

1Task definition describes the automation.

2Task schedule describes when it is expected.

3Scheduler worker creates planned occurrences.

4External systems send execution events.

5ASE links executions to planned occurrences.

6Operators see late, missing, failed, running, and successful runs.

Capabilities

Built for recurring operational work

Capability Operational behavior Status model

Planned vs actual timeline

Compare expected planned occurrences with real executions, grouped by task, host, environment, or category.

planned / success / failed

Cron and one-shot schedules

Monitor recurring cron plans and punctual expected runs, with a timezone on every task schedule.

schedule CRUD

Missing and late detection

Use grace periods and deadlines to separate acceptable delay from incidents that need attention.

warning / missed

Execution event API

Scripts, jobs, CI pipelines, and external systems report started, succeeded, and failed execution events.

API logs

Notifications

Email and Mattermost deliveries move through pending, sent, failed, and retry states.

pending / sent / failed

Scheduler worker

A dedicated container generates future planned occurrences and processes detection in the background.

healthcheck

API clients and permissions

Issue API keys and restrict clients to the exact task keys they are allowed to report.

restricted keys

Installation timezone

ASE stores and calculates in UTC, then displays in the administrator-selected installation timezone.

UTC + display

Docker-first deployment

Run the published clinuxfr/ase-ops image with app, web, scheduler, and MariaDB services.

compose stack

Business architecture

Expected automation meets real execution

External jobs
cron, scripts, CI

Execution events API

ASE web app
timeline and admin UI

Persist state

MariaDB
config, schedules, events

Scheduler worker
plan, detect, notify

Email / Mattermost

Operators
late, missing, failed runs

Docker deployment

Static docs for a containerized operations tool

Browser

HTTP

web
nginx

PHP

app
PHP-FPM

scheduler
worker

MariaDB
database_data

public_assets
shared public files

execution_logs
logs and heartbeat

web serves public assets through nginx and forwards PHP requests.

app runs the Symfony/PHP-FPM application.

scheduler plans occurrences, detects late or missed runs, and dispatches notifications.

database persists configuration, planned occurrences, and execution events in MariaDB.

Install preview

Deploy ASE with Docker Compose

mkdir ase && cd ase
curl -O https://example.com/docker-compose.yml
curl -O https://example.com/.env.example
cp .env.example .env
docker compose up -d

Production deployments should set APP_SECRET, database passwords, PUBLIC_SCHEME, and DEFAULT_URI. Docker image: clinuxfr/ase-ops.

Installation guide Docker Hub Settings reference