OAP servers inter communicate with each other in a cluster environment. In the cluster mode, you could run in different roles.
- Mixed(default)
- Receiver
- Aggregator
In some time, users want to deploy cluster nodes with explicit role. Then could use this.
Default role, the OAP should take responsibilities of
- Receive agent traces or metrics.
- Do L1 aggregation
- Internal communication(send/receive)
- Do L2 aggregation
- Persistence
- Alarm
The OAP should take responsibilities of
- Receive agent traces or metrics.
- Do L1 aggregation
- Internal communication(send)
The OAP should take responsibilities of
- Internal communication(receive)
- Do L2 aggregation
- Persistence
- Alarm
These roles are designed for complex deployment requirements based on security and network policy.
If you are using our native Kubernetes coordinator, the labelSelector
setting is used for Aggregator
choose rules. Choose the right OAP deployment based on your requirements.