Understanding Event Meshes and Mesh Manager

Mesh Manager builds event meshes by connecting your event broker services using Dynamic Message Routing (DMR). For background on event meshes and how DMR works, see Understanding Event Meshes and Dynamic Message Routing. This topic covers what is specific to event meshes in Mesh Manager.

When you're ready to start using Mesh Manager to create event meshes, see the following pages:

DMR Clusters and Links in Mesh Manager

Mesh Manager builds an event mesh from DMR clusters. For definitions of the terms used here, see DMR Terminology.

In Mesh Manager, DMR clusters and links work as follows:

  • A DMR cluster can contain one or more event broker services. For event broker services created with:

    • LTS maintenance version 10.26.0.9000-18

    • Rolling version 10.26.8.13158-17

    or later, you must enable DMR to create a cluster. For event broker services created with versions prior to those listed, DMR is enabled and each service is created with its own DMR cluster by default. You can configure multiple event broker services to be part of the same DMR cluster by setting the same cluster name.

     For more information, see:

  • Within a DMR cluster, each event broker service is referred to as a node. If you have multiple event broker services in a DMR cluster, the nodes are connected in a full mesh via DMR internal links, which are best used for event broker services in the same geographical region. You cannot configure internal DMR links in Mesh Manager. To configure them, see Configuring DMR Internal Links. For more information about horizontal scaling, see Horizontal Scaling.

  • In a DMR cluster, one event broker service (or node) is the gateway node that connects to other gateway nodes in other DMR clusters. These connections are referred to as external DMR links, which is what Mesh Manager automatically configures for you.

Considerations for Working with Event Meshes

To work with event meshes in Mesh Manager, make sure that you meet these requirements:

  • You require the following roles assigned to your user account, depending on the tasks you need to do:

    • To view and run health checks on an event mesh, you require the Mission Control Viewer role.

    • To view and run health checks, and to create, modify, or delete an event mesh, you require the Mission Control Manager role.

    • To create, modify, or delete event broker services as part of modifying or creating event meshes, you also require the Mission Control Manager role.

    If you require a role, contact your Solace Cloud Administrator. For more information about the roles, see Roles and Permissions.

  • Any event broker services that are part of an event mesh must be Enterprise services; the use of Developer services in an event mesh is not supported in production, but can be used for testing purposes.

  • You can connect one event broker service that has a private endpoint (private IP addresses) to another event broker service that is configured with a public endpoint (public internet), provided that the initiator is the service with the private endpoint.

  • You can connect two event broker services using private endpoints (private IP addresses) if the regions have IP connectivity with each other. How you connect the event broker services depends on the deployment type:

    • For Dedicated Cluster regions, see Networking Options for Dedicated Cluster Deployments for connectivity options.

    • For Customer-Controlled Cluster regions, you can do this using any configurations you require, because your organization is ultimately responsible for configuring and maintaining the infrastructure.

Be aware of these behaviors and limitations when you work with event meshes in Mesh Manager:

  • Mesh Manager always creates a full mesh of DMR external links between the event broker services in your event mesh. If, at any time, an event mesh has fewer than two event broker services, the event mesh is deleted.

  • An event broker service can be part of only one event mesh. Event broker services within an event mesh can be a mix of supported event broker versions. If you are using DMR clusters, each node in the DMR cluster can belong to only one mesh. For example, you cannot have one event broker service in the DMR cluster belong to one event mesh and a different event broker service in the DMR cluster belong to another event mesh. For best practices for configuring event meshes, see Best Practices for Designing an Event Mesh with DMR.

  • After an event broker service becomes part of an event mesh, you cannot delete the event broker service unless you remove the event broker service from the event mesh it is part of.

  • In Mesh Manager, event broker services manually configured using Broker Manager (legacy mechanism) are not visible in Mesh Manager unless you scan for them. To see them, you must discover the event meshes.

    Broker Manager is for non-typical use cases, for configuring other types of meshes, and for advanced settings, and it requires in-depth knowledge of the software event broker. Solace doesn't recommend using Broker Manager to modify event meshes created using Mesh Manager. If you require advanced configuration, contact Solace.

    For more information, see Discovering New Event Meshes.

Understanding Event Mesh Health

In Mesh Manager, you can validate the health of an event mesh using the event mesh health check. The status of the event mesh is most useful for people who are administering connectivity between multiple event broker services, because the event broker services are often located in different geographical regions. For a health check to run, the operational status of a link must be Up. The health check uses a customized, secure probe to check the integrity of the links in an event mesh. The probe is an enhanced ping that performs an in-band validation and integrity test to verify that test events and messaging can be exchanged between event broker services; if the operational status of a link is down, the health check cannot run.

A health check validates these items in an event mesh, using one secure Solace Message Format (SMF) connection on each event broker service:

Link status
To validate connectivity, health check pings each direction of the link between two event broker services, and records the time of the probe.
Event status
To verify that topics can be subscribed and published to, health check uses the request-reply pattern and a reserved topic called #insights/pinger/ping. It creates (and later deletes) a temporary client username called mesh-validation-<session-id>, where <session-id> is a string value representing the health check session.
Connectivity to the Management Port
Connectivity between the Mission Control Agent and each event broker service that has the management port enabled is validated.

An event mesh is considered unhealthy (or invalid) when at least one link is down or doesn't pass a health check. This situation can occur for several reasons, including:

  • no SMF connections were available for the test to run
  • the tests between mesh nodes in either direction failed; tests for both directions must pass for a link to be considered healthy
  • connectivity between the management port and the Mission Control Agent could not be established

After a health check completes, you can see the status when you view the details of the event mesh. For more information, see Viewing an Event Mesh.

For information about how to run a health check on an event mesh, see Verifying the Health of an Event Mesh.