Date: Fri, 29 Mar 2024 10:27:23 +0000 (UTC) Message-ID: <1301606256.5703.1711708043087@ip-10-0-1-161.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_5702_979923544.1711708043085" ------=_Part_5702_979923544.1711708043085 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
For Uptime Infrastructure Monitor 7.8.5 and later, the vcruntime140.dll = must be installed prior to installing or upgrading. If the .dll is not avai= lable during the upgrade or installation process, you may receive a message= that the procedure failed.
To fix this issue:
Proceed to the appropriate section depending on your Monitoring Station = platform:
Windows Installations Only: When running the Uptime Inf= rastructure Monitor installation on Windows, an initial splash screen appea= rs and then disappears. There is an approximately 5-minute waiting period u= ntil the main installer loads. This is due to the installer unpack. You can= see two Uptime processes running in task manager. This is normal behavior.=
On Windows, the Uptime Infrastructure Monitor Monitoring Station is inst= alled using a graphical installer that guides you through the steps of the = installation process.
uptime-<version#>=
-windows.exe
C:\Program Files\uptime software\uptime
), then click&=
nbsp;Next.=
C:\Program Files\uptime software\uptime\datastore
), then click =
Next.<installDirecto=
ry>\apache\conf\httpd.conf
file, which contains configuratio=
n information for the Web server used by Uptime Infrastructure Monitor.httpd.conf file.
CN=3Dhostname,O=3DOrganization,OU=3DITS=
ervices,ST=3DCalifornia,C=3DUS
). The passphrase must be at least six=
characters long.uptime.conf
file<=
/li>
On Linux, the Uptime Infrastructure Monitor Monitoring Station installer= is a console application.
Type the following command:sh uptime-<version&g=
t;-linux.bin
It can take up to several minutes for the components of the installer to b=
e extracted from the .bin
file.
On the Introduction
page, press =
Enter to continue.
License Agreement
page, carefully read al=
l of the Uptime Infrastructure Monitor end-user license agreement. Press&nb=
sp;Enter to scroll through the agreement.DO YOU ACCEPT THE TERMS OF THIS LICENSE AGREEMENT? (Y=
/N)
prompt, type y
and =
press Enter.Choose Install Folder
: Accept the default install direc=
tory for the Monitoring Station files (/usr/local/uptime
) or e=
nter a new, absolute path, then press Enter.
This is the location of the core Uptime Infrastructure Monitor components =
(i.e., the Data Collector and Web server), as well as the Controller; the D=
ataStore location is set in the next step.
The uptime
user account must be able to access the specifie=
d directory.
Choose DataStore Path
: Accept the default install direc=
tory for the DataStore (/usr/local/uptime/datastore
) or enter =
a new, absolute path, then press Enter.
Because the DataStore can grow very large (in excess of 100 GB), you can i=
nstall the DataStore on another file system if you are monitoring a large n=
umber of systems and retaining data for extended periods.
Choose Configuration Size
: Select the installation size=
that most closely matches your monitored deployment.
Your selection determines how Uptime Infrastructure Monitor's underlying c=
onfiguration is configured (for example, the MySQL buffer pool size and ope=
n connections cap). These parameters can be changed to match a different se=
lection after installation.
DataStore Port
: Accept the default DataStore port (3=
308
) or enter a new one, the press Enter.Web Server Name
: Accept the default hostname for Uptime In=
frastructure Monitor's Web server component or enter a new one, then press&=
nbsp;Enter.Web Server Port
: Accept the default Web server port (9999
) or enter a new one, then press Enter.
This is the port through which the Web server will listen for requests. Th=
e port number is written to the httpd.conf
file.Uptime Controller Port
: Accept the default Uptime Controll=
er port (9997
) or enter a new one, then press Ent=
er.<i=
nstallDirectory>/controller/etc/jetty-ssl.xml
file.Keystore Configuration
: Provide keystore information so th=
at the install process can generate the issuer for the Controller's self-si=
gned certificate.Distinguished Name
: Accept the default distinguished name =
(the hostname of the installation system) or enter a new one, then press&nb=
sp;Enter.CN
) attribute is required, but you can =
make the name as complete as needed (e.g., CN=3Dhostname, O=3DOr=
ganization, OU=3DITServices, ST=3DCalifornia, C=3DUS
).Keystore Password
: Enter and confirm a password.Pre-Installation Summary
: Review the configured options, t=
hen press Enter.After installing the Uptime Infrastructure Monitor Monitoring Station, y= ou will need to do the following:
Once the Monitoring Station is installed, connect to it using the hostna=
me and port defined during the installation process: http://<=
hostname>:<port>
The first user to log into Uptime Infrastructure Monitor should be the s=
ystem administrator. The administrator account has the default user name&nb=
sp;admin
, and at first login, you will have to set the passwor=
d and email address for this administrator account. To set up the administr=
ator account, do the following:
http=
://<hostname>:<port>
<hostname>
is the name or IP address of=
the system that is running the Uptime Infrastructure Monitor Monitoring St=
ation. For example:See License Information= for more information.
The fastest way to begin monitoring your infrastructure is to use <= a href=3D"/display/UT/Using+the+Auto-Discovery+Wizard">Auto Discovery&n= bsp;to efficiently assemble a monitored inventory.
Afterward, you can fine-tune your monitored inventory. See Managing Your Infrastructure for more inf= ormation.
You will need to create user roles (e.g., for administration, alert inve= stigation, and report access) and assign individual users or user groups to= them. See User Management for more information.
If you have installed Uptime Infrastructure Monitor as a virtual applian=
ce, the default user ID and password used to access the virtual OS is =
root
and uptime
, respectively. This lev=
el of access is required for system-level Uptime Infrastructure Monitor tas=
ks such as custom scripting, debugging, and working with the database. For =
security purposes, it is strongly recommended that you change the default r=
oot-level password provided for the Uptime Infrastructure Monitor virtual a=
ppliance OS.
If you are planning to use the Uptime Controller, there are further step= s to consider. See Controller Securit= y for more information.