hertzbeat icon indicating copy to clipboard operation
hertzbeat copied to clipboard

[Question] Collector Cluster Configuration in Multi-Isolated Network Environments: Load Balancing and Failover Support Inquiry

Open bruceplus opened this issue 9 months ago • 1 comments

Question

In a multi-isolated network environment, how should the collector cluster mode be configured when deploying as an installation package?

From the documentation, I see that the only configuration related to cloud-edge collaboration is setting model=private to mark it as private. Is that sufficient?

According to the architecture diagram, there appears to be only one collector per isolated environment. However, the expected scenario is that each isolated network environment can freely configure multiple collectors, with support for failover and load balancing.

Example:

Subnet A has collectors 1 and 2

Subnet B has collectors 1, 2, and 3

Subnet C has collectors 1 and 2

In each subnet, all collectors monitor the same data sources (e.g., A1 and A2 monitor the same sources)

Scenario 1: Can monitoring requests be load balanced between A1 and A2, but only within the same isolated environment (i.e., not cross-subnet)? Can B1, B2, B3 be load balanced similarly? Is this scenario supported?

Scenario 2: If A1 fails, can the system automatically fail over to A2? Is this kind of failover supported?

I couldn't find any relevant information in the documentation.

bruceplus avatar May 21 '25 02:05 bruceplus

Do have any plans to support cluster deployment across multiple isolated environments, including failover and load balancing capabilities?

bruceplus avatar May 22 '25 08:05 bruceplus