Monitoring Kubernetes Cluster Health in a Customer-Controlled Region

While Solace monitors the health of your event broker service, and encourages you to use PubSub+ Insights to monitor the event broker services in your estate, we also support and encourage using observability tools such as Datadog, Dynatrace, Prometheus, and OpenTelemetry to monitor the overall health of the Kubernetes cluster in your Customer-Controlled Regions.

If you choose to monitor the health of your Kubernetes cluster using monitoring tools, it is important to do so in a way that doesn’t interfere with the successful operation of the services in your PubSub+ Cloud deployment.

When using an observability tool to monitor your Kubernetes cluster in a Customer-Controlled Region, you must:

• configure your Kubernetes cluster so that all PubSub+ Cloud services (event broker services, Mission Control Agent, etc.) always have access to the resources and runtime environments they require. For more information, see General Resource Requirements for Kubernetes and Default Port Configuration.

• avoid using observability tools that alter or change pods used by Solace for all PubSub+ Cloud services.

• configure the agents for your monitoring tool to deploy to the same nodes as PubSub+ Cloud services without interfering with the resource and runtime requirements of those PubSub+ Cloud services.