Worker Runtime Overview

This area explains how IntegraMon keeps tenant runtime data fresh through background loops, locks, queues, and config-driven scheduling.

Chapters

• Modules
• Flows
• Operations
• Troubleshooting

Functional role

The worker runtime is the bridge between persisted tenant configuration and operational data visible in the UI. It is responsible for:

• archive jobs
• package and iFlow sync
• payload sync
• hot and cold message sync
• alert evaluation
• stats refresh

Main design properties

• config-driven scheduling via cConfigExt
• per-tenant loops over active configs
• lock-based protection against overlapping runs
• Celery task dispatch for heavier work
• runtime state persistence in jobs.*.runtime

Why this block matters

Most product behavior visible in alerting, message-popups, artifacts, packages, archives, and keystore depends on these loops having run successfully and in the right order.