Aggregated Messages
As part of command completion, the Task Tracker produces a human-readable message summarizing the aggregated execution outcome.
The content of this message is derived from the aggregation policy and reflects domain-specific decisions such as partial failures, degraded execution, and subsystem-specific errors. It is primarily intended for operators, logs, and diagnostic inspection.
Aggregated message semantics
In addition to structured fields such as status, result_code,
health_state and device lists, the aggregation outcome includes a
human-readable message.
The message is intended for operators, logs, and diagnostic inspection. It provides a concise summary of the task execution and, when applicable, a list of failure causes.
The message follows a conventional structure:
a single-line summary describing the overall task outcome;
optionally, a
Causes:section listing one or more failure causes, formatted as bullet points.
Example:
Task configure_pst completed in DEGRADED state: PST success 1/3.
Causes:
- pst-beam-02: timeout while configuring
- pst-beam-03: device unreachable
Important
The aggregated message is not API-stable.
Its wording, formatting, ordering of elements, and level of detail may change as the aggregation policy evolves. Consumers must not parse or depend on the exact content of the message to drive automated logic.
Clients should rely exclusively on structured fields such as
status, result_code, health_state and device lists for
programmatic decision-making.