Requirements and necessary settings
There are some requirements for hardware and network, and necessary network settings. The requirements are based on common scenarios and if you are in doubt about what you need, please check with Uptrends' Support. Make sure to adhere to the requirements and have the settings in place before you start installing the private checkpoint.
Your private checkpoints are used only for your monitors. The required capacity depends on the sort of monitoring running on the private checkpoint.
Non-browser-based monitoring, like HTTPS, connect, ping, and Multi-step API mainly have an impact on the available network capacity. Browser-based monitors mainly have an impact on server capacity (CPU, memory, disk I/O).
The typical capacity for a recommended private checkpoint setup is:
- 20 transactions at 5-minute intervals,
- 20 Full Page Checks at 5-minute intervals, and
- 100 basic monitors at 1-minute intervals.
Please note that this leaves room for:
- Confirming unconfirmed errors
- Maintenance of the Docker host and the containers
Check the following hardware specifications for adding a private checkpoint. For the best combination of performance and reliability we recommend using three instances, each with specifications as defined below. The hardware requirements are based on what other customers are using. However, what is needed in your situation is strongly related to the expected use which may differ from what the average customer needs.
|CPU||2 cores||4 cores|
|RAM||4 GB||8 GB|
|Storage||60 GB||60 GB on fast storage (SSD)|
|OS||Windows Server 2019 LTSC Standard||Windows Server 2022 LTSC Standard|
You will need to meet the following network requirements.
IPv4 — Fixed IPv4 address for each checkpoint server
IPv6 — Optional, depending on whether you use IPv6 in the monitored infrastructure.
Network — Although we recommend 1 Gbps, the actual usage of this connection is much lower (usually 1 to 10 Mbps 95%) and very constant. A connection to the internet that is well dimensioned to transfer the measurement data to the Uptrends platform.
There should not be SSL inspection on the traffic between the checkpoints and the Uptrends cloud servers. The firewall should allow long living outbound WebSocket connections.
Make sure that you do not have Group Policy Objects (GPOs) in place that will prevent Docker from creating a local firewall. For the computer running Docker, set the group policy setting Apply local firewall rules to ‘Yes’.
If the internal network is IPv6 enabled, please supply a fixed IPv6 address and gateway for each checkpoint server. The IPv6 IP Address enables us to monitor your infrastructure through IPv6 (with the proper firewall configuration). Without the fixed IPv6 address, Uptrends can only monitor through IPv4.
The private checkpoint requires a DNS server to be configured on the Docker host.
If you would like to monitor mail servers through an external route, configure reverse DNS using: firstname.lastname@example.org to resolve to the corresponding external IP address.