Managing and monitoring your agents
The Boomi Agent Control Tower (ACT) is a centralized hub that provides full visibility and control of your AI agent environment. From within Boomi Agentstudio, you can use the Control Tower to register, manage, govern, and monitor agents across different environments through a single interface. Using the Agent Control Tower you can:
-
Connect to providers: Providers on the Agent Control Tower allows you to connect to your internal (Boomi Agent Garden) or external third party agent builders/ environments (for example, Amazon Bedrock). Agent Control Tower currently supports the following providers:
- Boomi Agent Garden provider
- Amazon Bedrock provider
- Custom accounts
- Microsoft Copilot provider
- Salesforce provider
- Snowflake Cortex provider
Custom AccountsCustom Accounts are either manually registered or listed using the auto-catalog feature. Agent metadata, status, and metrics are not synced automatically. You can also register agents using the Custom Accounts GraphQL API.
Amazon Bedrock metrics (Beta)Amazon Bedrock agent metrics are currently in Beta. Not all metric types are available. To enable metrics, you must configure CloudWatch OAM access in your AWS account before data appears in the monitoring dashboard.
Microsoft Copilot, Salesforce, and Snowflake Cortex metricsMonitoring metrics are not yet available for Microsoft Copilot, Salesforce, or Snowflake Cortex providers.
For more information, refer to Agent Control Tower provider capabilities
-
AI-catalog your agents: Using the AI-catalog feature in custom providers you can add your agents using different types of files. The accepted file types include PDF, DOCX, YML, XML, JPG, and PNG. This feature makes your agent addition process quick and seamless.
-
View and manage agents: Once you connect to a provider, you can view and manage your agents all together from the agents screen or through their respective provider accounts. You can add trust levels and tags for easy filtering and organization. Some providers such as Amazon Bedrock allows you to enable and disable an agent right from the Agent Control Tower.
-
Monitor agents: Through the monitoring dashboard you can keep track of the number of times an agent is invoked, the average time for a process, spot errors, and so on.
-
Detect anomalies: The Agent Control Tower constantly checks and reports anomalies within agents. The detection uses a 30-day metric window to establish a baseline behavior and scope out deviations.
Agent Control Tower provider capabilities
ACT manages agents through two types of connections:
- Native providers
- Custom accounts
Native providers work like branded connectors. When you connect a supported provider, ACT catalogs its agents and syncs their metadata automatically, with no additional setup. The capabilities available for each native provider are listed in the first table below.
Native sync does not surface every piece of data a provider holds. Coverage varies by provider, and some capabilities, such as certain metrics, are not available through a native connection. In those cases you can onboard the same provider's agents as custom accounts instead. A custom account gives you more flexibility over the data you bring into ACT, in exchange for setting it up and maintaining it yourself. The second table lists what custom accounts support.
Native providers
When you connect a native provider, ACT syncs agent metadata automatically every 30 minutes. The capabilities below are available with no setup beyond connecting the provider.
Legend: ✓ available, ✗ not available, n/a provider does not expose this concept.
| Capability | Agent Garden | Bedrock | Copilot | Salesforce | Cortex |
|---|---|---|---|---|---|
| Agent metadata | |||||
| Agent status | ✓ | ✓ | ✓ | ✓ | ✓ |
| Agent description | ✓ | ✓ | ✓ | ✓ | ✓ |
| Version¹ | ✓ | ✓ | ✓ | ✓ | ✗ |
| Tools | ✓ | ✓ | ✓ | n/a | ✓ |
| Instructions | n/a | ✓ | ✓ | n/a | ✓ |
| Knowledge Base | ✓ | ✓ | n/a | n/a | n/a |
| Glossaries | ✓ | n/a | n/a | n/a | n/a |
| Guardrails | ✓ | ✓ | n/a | n/a | n/a |
| Management | |||||
| Enable / disable agent | ✓ | ✓ | ✗ | ✓ | ✗ |
| Auto-sync (every 30 min) | ✓ | ✓ | ✓ | ✓ | ✓ |
| Tags and trust levels | ✓ | ✓ | ✓ | ✓ | ✓ |
| Monitoring and metrics | |||||
| Invocations | ✓ | ✓ | ✗ | ✗ | ✗ |
| Average time per invocation | ✓ | ✓ | ✗ | ✗ | ✗ |
| Token usage (input / output) | ✓ | ✓ | ✗ | ✗ | ✗ |
| Errors | ✓ | ✓ | ✗ | ✗ | ✗ |
| Session logs / tracing | ✓ | ✗ | ✗ | ✗ | ✗ |
| Anomaly detection | ✓ | ✓ | ✗ | ✗ | ✗ |
| Activity logs | ✓ | ✓ | ✓ | ✓ | ✓ |
¹ ACT registers each Bedrock agent version and alias as a separate agent entry.
Custom accounts
A custom provider account lets you bring any agent into ACT, including a native provider. Unlike a native provider, a custom provider account does not sync automatically. You add and maintain the agent's metadata yourself, manually or through the API, so keeping it accurate is your responsibility.
To report metrics via our Custom Provider APIs, the provider must expose usage data at a glance so you can map to ACT's metrics endpoint. You can then push that data using the Custom Provider APIs, and ACT displays what it receives.
| Capability | Custom account |
|---|---|
| Agent metadata (status, description, version, tools, guardrails) | Supported. You add and maintain these values manually, via API, or via AI catalog. There is no live sync, so keeping them current is your responsibility. |
| Enable / disable agent | Not available |
| Auto-sync | Not available |
| Tags and trust levels | Supported |
| Metrics (invocations, average time, token usage, errors, throttles, tool usage) | Supported. You implement the metric mapping using the Custom Provider monitoring specs and push metrics via the Custom Provider APIs. ACT displays what it receives. |
| Session logs / tracing | Not available |
| Anomaly detection | Supported, calculated from the metrics you push |
| Activity logs | Supported |