System requirements
Minimum system requirements for installing AxonOps Server and AxonOps Dashboard on a self-hosted server to monitor and manage the 3 nodes that are part of the Starter Tier.
This is not a system requirements spec for Cassandra nodes where the AxonOps Agent is installed.
AxonOps Server and AxonOps Dashboard
Section titled “AxonOps Server and AxonOps Dashboard”| Component | Requirement |
|---|---|
| Processor | 1 gigahertz (GHz) or faster with 4 or more cores on a compatible 64-bit processor |
| RAM | 8 gigabytes (GB) |
| Storage | 20 GB or larger storage device |
Elasticsearch Metrics Store
Section titled “Elasticsearch Metrics Store”| Component | Requirement |
|---|---|
| Processor | 1 gigahertz (GHz) or faster with 4, ideally 8 or more cores on a compatible 64-bit processor |
| RAM | 16 gigabytes (GB) |
| Storage | 120 GB or larger storage device |
If you need to increase the number of nodes to be monitored, get in touch with us.
Supported browsers
Section titled “Supported browsers”The AxonOps Dashboard is a web application and must be accessed with a browser built on the Chromium engine. Browsers built on other engines, such as Mozilla Firefox (Gecko) and Apple Safari (WebKit), are not supported. On an unsupported browser the Dashboard may exhibit unexpected behaviour: parts of the interface may render incorrectly, fail to load, or not respond as intended.
| Browser | Engine | Supported |
|---|---|---|
| Google Chrome | Chromium | ✅ |
| Microsoft Edge | Chromium | ✅ |
| Brave | Chromium | ✅ |
| Opera | Chromium | ✅ |
| Vivaldi | Chromium | ✅ |
| Mozilla Firefox | Gecko | ❌ |
| Apple Safari | WebKit | ❌ |
Use a current release of the chosen browser. Chromium-based browsers not listed above are expected to work but are not tested.
Scaling beyond the Starter tier
Section titled “Scaling beyond the Starter tier”A single axon-server instance is capable of monitoring well over 1,000 nodes across multiple clusters. axon-server is not designed for clustered deployment — horizontal scaling is handled by the underlying datastores (Elasticsearch or OpenSearch for logs, events, and configuration; optionally Cassandra for metrics at larger deployments).
For deployments above 8 monitored nodes, using Cassandra as the metrics store is recommended. See Using Cassandra as a Metrics Store for configuration details.
axon-server resource sizing
Section titled “axon-server resource sizing”The following formulas apply to the axon-server process itself. Datastores (OpenSearch, Elasticsearch, or Cassandra for metrics) are sized separately.
Let n = total number of monitored nodes.
Kubernetes
Section titled “Kubernetes”| Resource | Formula |
|---|---|
| CPU limit (milliCPUs) | 500 + (n × 50) |
| Memory limit (MiB) | 1024 + (n × 128) |
Example values:
| Monitored nodes | CPU limit | Memory limit |
|---|---|---|
| 20 | 1500m | 3584 MiB (~3.5 GiB) |
| 50 | 3000m | 7424 MiB (~7.25 GiB) |
| 150 | 8000m | 20224 MiB (~19.75 GiB) |
| 300 | 15500m | 39424 MiB (~38.5 GiB) |
Set resource requests to 50% of the computed limits as a starting point and adjust based on observed utilisation.
Virtual machines
Section titled “Virtual machines”Apply the same formula to size the host running axon-server, rounding up to the nearest even number of vCPUs:
| Resource | Formula |
|---|---|
| vCPU | round up to nearest even: (500 + (n × 50)) / 1000 |
| RAM (GiB) | round up to nearest even: (1024 + (n × 128)) / 1024 |
Example values:
| Monitored nodes | vCPU | RAM |
|---|---|---|
| 20 | 2 | 4 GiB |
| 50 | 4 | 8 GiB |
| 150 | 8 | 20 GiB |
| 300 | 16 | 40 GiB |
These figures cover the axon-server process only. Allow additional headroom for the operating system and any co-located components (e.g. axon-dash).