Date: Fri, 29 Mar 2024 06:46:59 +0000 (UTC) Message-ID: <336164492.5641.1711694819696@ip-10-0-1-161.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_5640_1464495846.1711694819693" ------=_Part_5640_1464495846.1711694819693 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The directions in the subsequent sections assume you are installing Upti= me Infrastructure Monitor for the first time. If you are updating an ex= isting Uptime Infrastructure Monitor installation, there are other ste= ps to consider.
Upgr= ading the Uptime Monitoring Station will overwrite the changes to httpd.con= f, so when the upgrade is complete, be sure to update the httpd.conf file a= gain.
You = can only upgrade directly to Uptime Infrastructure Monitor 7.7 if your= current installed version is version 7.6.x or 7.5. Users on version = 7.1 must upgrade to version 7.3, then 7.5 before upgrading to 7.7. Us= ers on version 7.2 or 7.3 must upgrade to 7.5 before upgrading to 7.7.
User= s who are running version 6.0 or 6.0.1 must upgrade to 7.0 > 7.1 > 7.= 3 > 7.5 before upgrading to 7.7. Users who are running version 5.5 or ea= rlier must upgrade to 6.0 or 6.0.1 as a starting point. (Refer to the Uptim= e Infrastructure Monitor Knowledge Base for specific version upgrade paths.= ). If you are eligible for a direct upgrade path, you can upgrade usi= ng the installer for your Monitoring Station=E2=80=99s operating system.&nb= sp; The upgrade process installs new features, and does not modify or delet= e your existing data.
Refer to one of the following topi= cs if your current version is older than the version required for a direct = upgrade:
The Uptime Infrastructure Monitor Monitoring Station is a system running= the Data Collector (also referred to as the Uptime Core), and a Web server= .
The DataStore is where all historical performance and availability data = are stored. Uptime Infrastructure Monitor includes a MySQL database impleme= ntation, but it can also use either an Oracle or MS SQL Server database as = its DataStore. If you plan to use either of these databases, refer to Running Uptime Infrastructure Monitor with an Oracle database or Running Uptime Infrastructure Monitor with an MS SQL Server datab= ase in our Knowledge Base for additional information.
Although agentless monitoring is supported, you can also use Uptime Infr= astructure Monitor Agents to retrieve detailed performance metrics (such as= CPU, memory, process, disk, and network usage) from systems that you are m= onitoring. Uptime Infrastructure Monitor Agents can also securely and remot= ely execute programs; for example, the Windows Agent can start and stop ser= vices, and reboot the system. Install an Uptime Infrastructure Monitor Agen= t on each monitored system whose metrics are not collected by some agentles= s method. Agents support a variety of operating systems. For more informati= on about supported platforms for an agent, see Supported Agent Platforms. For more information about= supported platforms when using agentless monitoring, see Supported Platforms via Age= ntless Monitoring.
The Uptime Controller provides access to the API, which gives Uptime Inf= rastructure Monitor users access to inventories of monitored objects at var= ious organizational levels, as well as their respective statuses. This type= of information can be used to, for example, build custom dashboards.
The Uptime Infrastructure Monitor installation file includes three of th= ese components (the Monitoring Station, DataStore, and Controller), and thu= s contains everything you need to begin monitoring your IT infrastructure. = If you further require Uptime Infrastructure Monitor Agents as part of your= monitoring deployment, you can download and install them individually, bas= ed on operating system and platform, from the Support Portal Downloads page.
All communication between Monitoring Station and Uptime Infrastructure M= onitor Agents originates from the former, and is performed over TCP using p= ort 9998. (This port can be changed during the installation process.) When = a monitored system is outside a firewall, you only need to configure outbou= nd port access.
The following privilege-related information should be considered if you = are planning to use Uptime Infrastructure Monitor Agents:
uptime
user ID on th=
e Monitoring Station. This uptime
user should also exist on al=
l systems that have an Uptime Infrastructure Monitor Agent; using this ID o=
n monitored systems minimizes any security risks by not running the Agents =
as a privileged process.root
account to run the =
Monitoring Station or Uptime Infrastructure Monitor Agents.nobody<=
/code>, bin
, or adm
; however, using these account=
s may pose security risks depending on other system processes that run unde=
r these accounts.
nobody
user ID.Administrator
privileges. If it is not, th=
e Uptime Infrastructure Monitor Agent cannot access the system performance =
counters.When reviewing Uptime Infrastructure Monitor resource requirements, it i= s important to note that sizing varies based on the number of monitors per = element, the type of objects monitored, and the method used to gather perfo= rmance data. Uptime Infrastructure Monitor recommendations are based on an = average of 2 or 3 monitors per element. For more information regarding reso= urce requirements, see Uptime Infrastructure Monitor Sizing Examples.
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.
The following are the minimum hardware requirements for an Uptime Infras= tructure Monitor deployment.
The hardware configurations for a Monitoring Station can change dependin= g on the number of Uptime Infrastructure Monitor Agents you plan to monitor= , the reports that you want to generate, and the amount of historical data = that you wish to retain in the DataStore. For sizing examples, see Uptime Inf= rastructure Monitor Sizing Examples.
The amount of storage space for the Uptime Infrastructure Monitor DataSt= ore is dependent on the number of systems monitored. As a guide, use the Uptime Infrastructure Monitor DataStore Sizing= Calculator.
Uptime Infrastructure Monitor Agents are lightweight applications that r= equire minimal space and processing cycles to run; their impact is negligib= le, and do not require advanced planning.
Uptime Infrastructure Monitor only runs on 64-bit platforms. You cannot = install Uptime Infrastructure Monitor on a 32-bit operating system running = on 32-bit architecture.
See the following topics for the most up-to-date information regarding:<= /p>
Before proceeding with the installation sections, ensure you complete th= e following tasks:
uptime-<version>-linux.bin
uptime-<version>-windows.exe