...
Load balancing events to a set of servers
| Anchor | ||||
|---|---|---|---|---|
|
This setup shows load balancing the event to publish it to all three Analytcis Analytics receivers. The load balanced publishing is done in a Round Robin manner , sending where each event is sent to each receiver in a circular order without any priority.
It also handles fail-over cases such as, if Analytcis. e.g., If Analytics Receiver-1 is is marked as downinactive, then the Data Agent will send sends the data only to Analytcisto Analytics Receiver-2 and Analytcis and Analytics Receiver-3 in in a round robin Round Robin manner. When AnalytcisWhen Analytics Receiver-1 becomes becomes active again after some time, the Data Agent automatically detects it, adds it to the operation, and again starts starts to load balance between all three receivers again. This functionality significantly reduces the loss of data and provides more concurrency.
For this functionality, include the server URL in the Data Agent as a general Analytcis Analytics receiver URL. The URL should be entered in a comma - separated format as shown below.
...
Load balancing events to sets of servers
| Anchor | ||||
|---|---|---|---|---|
|
In this setup there are two sets of servers that are referred to as set-A and set-B. You can send events to both the sets. You can also carry out load balancing for both sets as mentioned in load balancing between a set of servers. This scenario is a combination of load balancing between a set of servers and sending an event to several receivers. An event is sent to both set-A and set-B. Within set-A, it will be sent either to Analytcis ReceiverA-1 or Analytcis ReceiverA-2. Similarly within set-B, it will be sent either to Analytcis ReceiverB-1 or Analytcis ReceiverB-2. In the setup, you can have any number of sets and any number of servers as required by mentioning them accurately in the server URL.
...
Sending all the events to several receivers
| Anchor | ||||
|---|---|---|---|---|
|
This setup involves sending all the events to more than one Analytcis receiver. This approach is mainly followed when you use other servers to analyze events together with Analytcis servers. For example, you can use the same Data Agents to publish the events to WSO2 EI. You can use this functionality to publish the same event to multiple EI servers at the same time. This is useful to perform real time analytics with EI Analytics, to persist the data, and also to perform complex analysis with Analytcis in nearly real time with the same data.
...
| Info |
|---|
E.g., |
Failover configuration
When using the failover configuration in publishing events to Analytcis, events are sent to multiple Analytcis receivers in a sequential order based on priority. You can specify multiple Analytcis receivers so that events can be sent to the next server in the sequence in a situation where they were not successfully sent to the first server. In the scenario depicted in the above image, the events are first sent to Analytcis Receiver-1. If it is unavailable, then events will be sent to Analytcis Receiver-2. If Analytcis Receiver-2 is also unavailable, then the events will be sent to Analytcis Receiver-3.
...