s4e-trigger is the scan orchestration entry point. It receives scan initiation requests and publishes them to the RabbitMQ message queue for downstream processing.


Overview

Property Value
Container s4e-trigger-1
Internal port 8000
Role Scan triggering and queue publishing

How It Works

  1. s4e-core calls s4e-trigger when a user starts a scan (via API or UI).
  2. s4e-trigger validates the request and publishes a scan job to RabbitMQ.
  3. s4e-dispatcher picks up the job and routes it to the appropriate worker queue.

s4e-trigger also handles:

  • Webhook-triggered scans — external systems can trigger scans via the trigger API.
  • Scheduled scan execution — the scheduler calls trigger for time-based scan jobs.

Viewing Logs

docker logs s4e-trigger-1 -f

Restarting

cd /opt/s4e/setup
docker compose up -d --no-deps trigger