Prerequisites
The resources needed for optimal performance depend on the product configuration. Adding more hosts, services and other configuration options may increase the server and database workload. Therefore, server configuration adjustments may be necessary to optimize performance for your specific environment.
- < 5000 Services
- < 10000 Services
- < 15.000 Services
- < 20.000 Services
- < 50.000 Services
- < 100.000 Services
- > 100.000 Services
Considered architecture: Basic
- 1 i-Vertix Central server
i-Vertix Central server
| Resource | Required minimum |
|---|---|
| CPU | 4 vCPU |
| RAM | 4 GB |
| Storage | 250 GB |
When using the Remote DBMS architecture:
i-Vertix Central server
| Resource | Required minimum |
|---|---|
| CPU | 4 vCPU |
| RAM | 4 GB |
| Storage | 250 GB |
Database server
| Resource | Value |
|---|---|
| CPU | 4 vCPU |
| RAM | 4 GB |
| Storage | 250 GB |
Considered architecture: Distributed
- 1 i-Vertix Central server
- 1 i-Vertix Poller
i-Vertix Central server
| Resource | Required minimum |
|---|---|
| CPU | 4 vCPU |
| RAM | 4 GB |
| Storage | 250 GB |
i-Vertix Poller
Assumed to handle production environments (up to 7.000 services with checks every 5 minutes)
| Resource | Required minimum |
|---|---|
| CPU | 4 vCPU |
| RAM | 4 GB |
| Storage | 60 GB |
When using the Remote DBMS architecture:
i-Vertix Central server
| Resource | Required minimum |
|---|---|
| CPU | 4 vCPU |
| RAM | 4 GB |
| Storage | 250 GB |
Database server
| Resource | Value |
|---|---|
| CPU | 4 vCPU |
| RAM | 4 GB |
| Storage | 250 GB |
Considered architecture: Distributed
- 1 i-Vertix Central server
- 2 i-Vertix Poller
i-Vertix Central server
| Resource | Required minimum |
|---|---|
| CPU | 4 vCPU |
| RAM | 4 GB |
| Storage | 250 GB |
i-Vertix Poller
Assumed to handle production environments (up to 7.000 services with checks every 5 minutes)
| Resource | Required minimum |
|---|---|
| CPU | 4 vCPU |
| RAM | 4 GB |
| Storage | 60 GB |
When using the Remote DBMS architecture:
i-Vertix Central server
| Resource | Required minimum |
|---|---|
| CPU | 4 vCPU |
| RAM | 4 GB |
| Storage | 250 GB |
Database server
| Resource | Value |
|---|---|
| CPU | 4 vCPU |
| RAM | 4 GB |
| Storage | 250 GB |
Considered architecture: Distributed
- 1 i-Vertix Central server
- 3 i-Vertix Poller
i-Vertix Central server
| Resource | Required minimum |
|---|---|
| CPU | 4 vCPU |
| RAM | 4 GB |
| Storage | 350 GB |
i-Vertix Poller
Assumed to handle production environments (up to 7.000 services with checks every 5 minutes)
| Resource | Required minimum |
|---|---|
| CPU | 4 vCPU |
| RAM | 4 GB |
| Storage | 60 GB |
When using the Remote DBMS architecture:
i-Vertix Central server
| Resource | Required minimum |
|---|---|
| CPU | 4 vCPU |
| RAM | 4 GB |
| Storage | 250 GB |
Database server
| Resource | Value |
|---|---|
| CPU | 4 vCPU |
| RAM | 4 GB |
| Storage | 350 GB |
Considered architecture: Distributed
- 1 i-Vertix Central server
- 7 i-Vertix Poller
i-Vertix Central server
| Resource | Required minimum |
|---|---|
| CPU | 8 vCPU |
| RAM | 8 GB |
| Storage | 650 GB |
i-Vertix Poller
Assumed to handle production environments (up to 7.000 services with checks every 5 minutes)
| Resource | Required minimum |
|---|---|
| CPU | 4 vCPU |
| RAM | 4 GB |
| Storage | 60 GB |
When using the Remote DBMS architecture:
i-Vertix Central server
| Resource | Required minimum |
|---|---|
| CPU | 4 vCPU |
| RAM | 4 GB |
| Storage | 250 GB |
Database server
| Resource | Value |
|---|---|
| CPU | 4 vCPU |
| RAM | 4 GB |
| Storage | 550 GB |
Considered architecture: Distributed
- 1 i-Vertix Central server
- 15 i-Vertix Poller
i-Vertix Central server
| Resource | Required minimum |
|---|---|
| CPU | 8 vCPU |
| RAM | 8 GB |
| Storage | 1.25 TB |
i-Vertix Poller
Assumed to handle production environments (up to 7.000 services with checks every 5 minutes)
| Resource | Required minimum |
|---|---|
| CPU | 4 vCPU |
| RAM | 4 GB |
| Storage | 60 GB |
When using the Remote DBMS architecture:
i-Vertix Central server
| Resource | Required minimum |
|---|---|
| CPU | 4 vCPU |
| RAM | 4 GB |
| Storage | 350 GB |
Database server
| Resource | Value |
|---|---|
| CPU | 4 vCPU |
| RAM | 4 GB |
| Storage | 1 TB |
Our support team is glad to help you find the right architecture and hardware specs for your system.
Database server
The database can also be installed in a high available (cluster) configuration upon request. This effectively prevents potential data loss.
i-Vertix Poller
To effectively handle the load of monitoring, it is recommended to have a dedicated Poller for every 500 hosts or 7.000 services.
Storage consumption
The space used to store collected performance data depends on several criteria:
- Frequency of controls
- Number of controls
- Retention time
The following table provides an estimate of disk space required for your platform assuming:
- Data is collected every 5 minutes
- The retention period is 6 months
- Each performance graph has 2 curves
| Number of Services | /var/lib/mysql (in GB) | /var/lib/centreon (in GB) |
|---|---|---|
| 500 | 10 | 2,5 |
| 2.000 | 42 | 10 |
| 10.000 | 93 | 27 |
| 20.000 | 186 | 54 |
| 50.000 | 465 | 135 |
| 100.000 | 930 | 270 |