An Event Management Agent is required to discover runtime data and configure event brokers using Event Portal. Event Management Agents have the following deployment options:
Event Management Agents support connections to Solace software event brokers and appliances and Kafka clusters and Confluent schema registries.
Cloud-Based Event Management Agent for Dedicated Regions and Customer-Controlled Regions
The Solace-managed, cloud-based Event Management Agent connects all event broker services in a single datacenter to PubSub+ Cloud. For more information about configuring cloud-based Event Management Agents, see Connecting Event Broker Services to Event Portal With a PubSub+ Cloud Connection.
You must enable basic authentication with the default client username on your event broker service to enable a connection between the event broker services and Event Portal using the cloud-based Event Management Agent.
We recommend using the cloud-based Event Management Agent to connect your event broker services to Event Portal in all situations, except the following:
-
Your event broker services are in a Public Region.
-
You want to connect your Solaceappliance, or Solacesoftware event broker to Event Portal.
-
You want to audit Kafka clusters and Confluent schema registries.
-
Your organization's security policies don't allow you to connect your operational event broker services to Event Portal.
-
You want to redact sensitive data from scan files before manually uploading the data to Event Portal.
In the following architecture diagram, the red box highlights the Event Management Agent:
The security measures applied in this scenario include:
-
The Event Management Agent connects only to the event broker services in your datacenter.
-
The Event Management Agent never stores configuration details or credentials.
Event Management Agents in Offline Mode
Event Management Agents in Upload Scan File Mode
In offline mode, you install Event Management Agents within your own network. For more information, see Setting Up Event Management Agents to Upload Scanned Files.
We recommend offline mode in these use-cases:
-
Your organization's security policies don't allow you to connect your operational event brokers to Event Portal. For example, your event brokers are not connected to the internet.
-
You want to redact sensitive data from scan files before manually uploading the data to Event Portal.
Offline mode requires two Event Management Agents:
-
An Event Management Agent to communicate with Event Portal.
-
An Event Management Agent to communicate with your event brokers.
In the following architecture diagram, the red boxes highlights the Event Management Agents.
The security measures applied in this scenario include:
-
There is no direct connection between PubSub+ Cloud and your event brokers.
-
Offline mode does not allow you to send event broker configuration from Event Portal to operational event brokers.
Event Management Agents in Connected Mode
In connected mode, you install Event Management Agents within your own network. For more information, see Setting Up an Event Management Agent to Run Scans from Event Portal.
We recommend connected mode in these use-cases:
-
Your event broker services are in a Public Region.
-
You want to connect your Solaceappliance, or Solacesoftware event broker to Event Portal.
-
You want to audit Kafka clusters and Confluent schema registries.
In the following architecture diagram, the red box highlights the Event Management Agent:
The security measures applied in this scenario include:
-
The Event Management Agent must authenticate with the event brokers it connects to so it can securely exchange information.
-
Authentication credentials are retrieved on a per-connection basis, and are not stored in the Event Management Agent.
-
Communication between the Event Management Agent, Event Portal, and your event brokers occur over secured connections.