System Manager
The operational view of infrastructure, runtimes and security.
How it fits together.
System Manager combines operational visibility into activity, infrastructure, connectors and execution services. Individual areas have their own permissions. To investigate a slow or failed agent run, start with Agent Runtime, which offers Overview, Errors and Feedback. Stale monitoring data is indicated separately.
Error details can include tool, error code, time, run, runtime and whether retry is indicated. Inputs, outputs and further details help document a specific operational observation. Data Runtime adds visibility into stored and archived time-series data, recordings and active data movements.
Step by step in AIOS
Using an authorized operator account, open Account menu → System Manager.
System Manager and its operational sections require specific permissions. If a tab is missing, first check the operator account’s assigned responsibilities.
Start with Activity. System, Domains, Connectors and Security provide visibility into the relevant operational area.
Activity is the starting point for a general observation. For a specific question, choose the relevant area, such as Connectors for connections or Security for operational security events.
Model Runtime, Agent Runtime, Data Runtime, Jobs and Task Engine show execution services and their work.
Agent Runtime offers Overview, Errors and Feedback. Data Runtime shows recordings, database and archive quantities, and active data movements. Match the observation to the appropriate section.
Open a service or runtime object for details and actions allowed for your account.
Open an error or runtime and record time, run, code and tool. Check for stale-monitoring warnings before treating the displayed state as current.
AIOSAn example for your work.
Observation: An agent run ends without the expected document.
Time: [copy from error detail]
Error code / tool: [copy from the display]
Run / runtime: [displayed references]
Retry indicated: [Yes/No]
Existing output: [brief description]
Open question: Is input context missing, or is the execution connection affected?
Next step: Give the findings to the responsible operator for review.Fill in the template with the displayed error details so the operator can investigate the affected run.
Choose the operational area
| Area | Meaning in daily work |
|---|---|
| Agent Runtime | Registered runtimes, usage, errors and feedback. |
| Error detail | Tool, code, time, run, runtime and retry information. |
| Data Runtime | Time-series data, database/archive, recordings and data movements. |
| Model Runtime | Operational model execution environment according to permission. |
| Security | Operational security events and available investigation controls. |
If something does not work.
- Monitoring is marked stale: Treat the last state as an older observation and investigate the runtime connection.
- No runtime is registered: The overview distinguishes this from an existing run with an error. Record the state for the operator.
- An expected operational area is missing: Check its permission. Agent Topology is not currently exposed as a selectable tab.