A compliance or remediation worker opens an agentless session, runs the profile, and writes the parsed result. Transports are SSH, WinRM, Ansible, Python over SSH, and Netmiko for a network device.
04
Execution layer
WorkersCheck and remediation workers talk to hosts. The AAG worker talks only to the selected provider.
Celery workers run checks, remediation, discovery, and schedules. The AAG worker calls the selected model and does not open a session that changes a host.
Where it sits in the stack
- 01 Access layer
- 02 Control plane
- 03 Data and messaging
- 04Execution layer Focus
- 05 Managed targets
CelerySSHWinRMNetmikoAAG
How requests move
- 01
A worker claims a task from its queue
- 02
A check worker connects to the target, or the AAG worker calls the provider
- 03
Logs stream back while the task runs
- 04
The result is written. An AAG reply stays an advisory record
What this layer does
-
Checks and remediation over SSH, WinRM, Ansible, Python, and Netmiko
-
Discovery with nmap and SNMP, plus an AD or LDAP import
-
An AAG worker that does not change a host or a check result
-
Live logs during the run, and a sweeper for a stalled run
The inventory queue runs nmap and SNMP discovery, and AuditFlow matching. An AD or LDAP import lands in the same host list. Celery Beat starts scheduled jobs. A sweeper marks a run that stopped updating.
The AAG worker handles explain and generate on the aag queue. It redacts the text before the call. The API key is not placed in the task. The reply does not become a check result. A failed AAG task can be queued again. A call can wait up to 120 minutes, and a timeout is not retried.