BindPlane OP's resource requirements will differ based on the number of
managed agents. CPU, Memory, Disk throughput / IOPS, and network consumption
will increase as the number of managed agents increases.
Follow this table for CPU, memory, and storage capacity sizing.
BindPlane OP has two back-end options. Bolt Store (default) and PostgreSQL. Bolt store is recommended for single instance deployments of BindPlane OP. If you expect to deploy BindPlane on multiple instances, you should use PostgreSQL to avoid migrating from Bolt Store in the future.
When using the default storage back-end (
bbolt), disk throughput and operations per second
will increase linearly with the number of managed agents. Enterprise deployments that are not using
can safely ignore this section.
To prevent disk performance bottle-necking, ensure the underlying storage solution
can provide enough disk throughput and operations per second. Generally, cloud providers
will limit disk performance based on provisioned disk capacity.
|Agent Count||Read / Write Throughput||Read / Write IOPS||Storage Capacity|
BindPlane OP maintains network connections for the following:
- Agent Management
- Agent Throughput Measurements
- Command line and Web user interfaces
Maximum network throughput scales linearly with the number of connected agents. As a rule of thumb, expect to consume 4mbps for every 1,000 connected agents.
BindPlane OP can run on a local area network and behind a firewall.
BindPlane OP does not need to be reachable from the internet, however, if agents. or users outside of your WAN require access, a VPN or inbound firewall rules must be configured to allow access.
BindPlane OP listens on port
3001 by default. This port is configurable. See the configuration documentation.
The BindPlane port is used for:
- Agent command and control using the Open Agent Management Protocol (OpAMP) (Websocket)
- Agent throughput measurement requests (HTTP POST request)
- Browser and CLI users (HTTP and Websocket)
Browsers and API Clients
The firewall must allow HTTP traffic to reach BindPlane OP on the configured port.
Agents must be able to initiate connections to BindPlane OP for OpAMP (websocket) and throughput measurements (HTTP). BindPlane OP will never initiate connections to the agent. The firewall can be configured to prevent BindPlane OP from reaching the agent networks, however, agent networks must be able to reach BindPlane OP on the configured port.
BindPlane OP will reach out to github.com/observIQ/observiq-otel-collector/releases in order to detect new agent releases. This feature is optional.
You can disable Github polling by setting
0 in your BindPlane configuration.
1agentVersions: 2 syncInterval: 0