Agents (Beta)

Agents enable seamless integration of AI capabilities into existing event flows without complex coding to perform specific tasks or provide domain-specific knowledge. Agents connect to PubSub+ event broker services for reliable and secure processing of events.

Agent are not enabled by default. To enable Agents in your account, please contact Solace.

Agents are lightweight modules that use artificial intelligence—such as large language models (LLMs) and retrieval-augmented generation (RAG)—to perform specific tasks. Agents subscribe to specific queues or topics on event broker services, perform processing tasks on the events they receive, and then publish those processed events back to the event mesh.

Using Agents in PubSub+ Cloud

You can create and manage Agents in the PubSub+ Cloud Console.

Agents are supported in Public Regions, Dedicated Regions, and Customer-Controlled Regions.

Using Agents in the PubSub+ Cloud Console

When you work with Agents in the PubSub+ Cloud Console you go through the following stages:

Decide and Discover: You find the right Agent and decide to create a source or target Agent. See Discovering Agents in PubSub+ Cloud.
Design: You create and configure the Agent to supply information about your external system, such as the connection name or address, authentication detail, queue names, and so on. These details are necessary to allow the Agent to connect to the external system as either a source or target. For more information, see Designing Agents.
Deploy and Observe: You deploy and observe your Agent to ensure that it fulfills your requirements. Unlike PubSub+ Self-Managed Connectors, Cloud-Managed Micro-Integrations provide a way to visualize the state of the Agent so you can focus on the details of the data flows between the external system and your PubSub+ event broker service. For more information, see Deploying an Agent.
Update and Evolve: You can iterate and modify the configuration settings as required. Before making modifications, you must undeploy the Agent. After you make updates to the Agent, you can redeploy it. If the created Agent doesn't perform as expected, you can also delete it and restart the design. For more information, see Managing Agents
Upgrade: Solace automatically upgrades your Agents. For more information, see Upgrading Agents.

Agent States

An Agent has a particular state depending on where it is in the creation and management workflow:

Not Deployed: When you undeploy an Agent, it transitions from Running to Undeploying, and then to Not Deployed state. an Agent starts in the Not Deployed state when it's first created. In the Not Deployed state, data does not flow between your external system and the PubSub+ event broker service.
Deploying: A transient state that indicates the Agent is in the process of being deployed. If successful, data will start to flow between the external system and the PubSub+ event broker service.
Running: When you deploy an Agent, it transitions from it's current state to Deploying, and then the Running state. In the Running state, data flows between your external system and the PubSub+ event broker service.
Undeploying: A transient state that indicates that the Agent is the process of being undeployed, and the flow of data is stopping between your external system and the PubSub+ event broker service.
Unable to Deploy: If an error condition occurs during the deployment of the Agent and the Agent cannot be deployed, the state transitions from the Deploying state to the Unable to Deploy state. When you view the Agent, the reasons for the errors are displayed in the error text.
Down: If an error condition occurs with an Agent and recovery is not possible, the Agent moves to the Down state. When you view the Agent, the reasons for the errors are displayed in the error text.

Using Agents with Environments

Agents support environments. Environments are useful when you want to separate instances from each other. For example, in situations where you have production, staging, and developer environments.

For more information about using environments, see Creating and Managing Environments.

When you use environments with Agents, be aware of the following considerations:

an Agent cannot connect to an event broker service in a different environment. Event broker services and Agents must be in the same environment.
If you have an Agent configured to connect to an event broker service that is no longer available in the same environment, the Agent is automatically undeployed, and the Agent shows the Unable to Deploy state. The error condition indicates that the event broker service is not accessible to the Agent.
You cannot clone an Agent from one environment to another. You must manually re-create the Agent in a different environment.

Provide feedback