-
Notifications
You must be signed in to change notification settings - Fork 3
Relationships
Felix Bole edited this page Mar 20, 2025
·
1 revision
- Description: How monitoring and reporting entities interact.
-
Details:
-
MonitoringAgentcreatesReportingAgentinstances. -
ReportingAgentemits signals to updateMonitoringAgent’s workflow.
-
- Description: How nodes are managed within the library.
-
Details:
-
NodeSupervisorcreates and managesNodes. -
NodeStatusManagerupdates node statuses based on signals.
-
- Description: How data flows through pipelines.
-
Details:
-
NodeusesPipelineProcessorto process data. - Data moves from one node to the next in a chain.
-
NodeSupervisor
↓ manages
Node
↔ ReportingAgent (for status reporting)
contains →
NodeStatusManager (manages signals and execution state)
[Pipeline 1 || Pipeline n] (concurrent execution)
executes →
[PipelineProcessor 1, PipelineProcessor n] (serial processes)
interacts with → External Service
↓ can deploy
Child Chains (serial or parallel execution)
↑ monitored by
MonitoringAgent
- NodeSupervisor: Manages the overall node operations.
-
Node:
- Interacts bidirectionally with the ReportingAgent for status updates.
- Contains the NodeStatusManager to handle signals and manage execution state.
- Executes one or more pipelines concurrently.
- Supports the integration of child chains for nested workflows.
- PipelineProcessors: Execute processes in serial order, interacting with external services as needed.
- MonitoringAgent: Aggregates status updates and broadcasts chain statuses externally.