OpAMP

Collectors connected to Bindplane communicate using the OpAMP Protocol over a WebSocket connection.

Bindplane acts as the OpAMP server and the collector is the OpAMP client. Both sides manage and monitor the WebSocket connection.

OpAMP Configuration Overview

• Heartbeats - Client heartbeats require Bindplane v1.75.0+ and BDOT v1.70.0+, while server heartbeats are used for older versions or unsupported collectors. Server heartbeats send empty messages to maintain WebSocket connections, with a 70-second interval for removing inactive collectors.

• Connection Retries - The OpAMP client employs an exponential backoff strategy for connection retries after failed attempts.

• Connection States - The collector process in Bindplane can be in various states such as Connected, Disconnected, Error, Configuring, Pending, Incompatible, and Upgrading.