Date: Thu, 28 Mar 2024 08:34:04 +0000 (UTC) Message-ID: <215101797.5297.1711614844299@ip-10-0-1-161.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_5296_827211704.1711614844293" ------=_Part_5296_827211704.1711614844293 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The Monitoring Station server should ideally be a physical syste= m that is dedicated to Uptime Infrastructure Monitor. If a dedicated physic= al server is not available and a Virtual instance is deployed, the VM must = be provisioned with at least 4 vCPUs and hard (reservation) minimum resourc= e settings should be configured to match the hardware requirements describe= d below.
The minimum required hardware configuration varies depending on the numb= er of systems being monitored, the number of service monitors and various o= ther operational factors such as reporting load and database configuration = (e.g. bundled DB or remote server).
As a general rule of thumb when planning the allocated disk space, you s= hould plan on allocating about 4 GB per monitored element. Note that per el= ement usages are per year, unless you archive using old data.
Please contact uptime Support at uptime-support@idera.com = for more information or assistance on sizing your Monitoring Station server= .
The following minimum hardware configurations are recommended for deploy= ments that are monitoring up to 50 systems:
Windows & Linux Systems
Solaris Systems (Uptime Infrastructure Monitor 7.1 or earlier ve= rsions only)
Please refer to the Supported Monitoring Station Platfor= ms in Uptime Infrastructure Monitor for further details.
DataStore
The amount of disk storage space for the up.time DataStore will depend o= n the number of systems being monitored, the monitoring interval, and the t= ype of data being collected. Please refer to the Uptime Infrastructure Monitor DataStore Sizing Calculator for guid= ance.