Date: Thu, 28 Mar 2024 15:18:06 +0000 (UTC) Message-ID: <240857611.5399.1711639086657@ip-10-0-1-161.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_5398_445865597.1711639086653" ------=_Part_5398_445865597.1711639086653 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
If you plan on using the up.time Controller by integrating API functions= with the Uptime Infrastructure Monitor Web interface, consider doing the f= ollowing to prevent several common browser-related warnings when navigating= secure and non-secure pages within the same web page:
As part of the Uptime Infrastructure Monitor installation process, a pro=
xy is configured in the <uptimeDirectory>\apache\conf\httpd.con=
f
file. This provides ease of use with the up.time Controller, as it=
simplifies many API programming tasks, and helps to ensure the Controller =
remains secure.
By default the proxy section should look like the following:
# prox= y settings LoadModule proxy_module modules/mod_proxy.so LoadModule proxy_http_module modules/mod_proxy_http.so=20 ProxyRequests Off <Proxy *> Order deny,allow Allow from all </Proxy> ProxyPass /uptime http://<uptimeHost>:9996/uptime retry=3D0 ProxyPassReverse /uptime http://<uptimeHost>:9996/uptime ProxyPass /gadgets/service http://<uptimeHost>:9996/gadgets/service r= etry=3D0 ProxyPassReverse /gadgets/service http://<uptimeHost>:9996/gadgets/se= rvice ProxyPass /gadgets/instances http://<uptimeHost>:9996/gadgets/instanc= es retry=3D0 ProxyPassReverse /gadgets/instances http://<uptimeHost>:9996/gadgets/= instances # ssl proxy settings LoadModule ssl_module modules/mod_ssl.so SSLProxyEngine on ProxyPass /api https://<controllerHost>:9997/api retry=3D0 ProxyPassReverse /api https://<controllerHost>:9997/api
The proxy is configured to work using the default options and configurat= ion choices made when Uptime Infrastructure Monitor is installed:
<uptimeHost>
above) and up.t=
ime Controller (<controllerHost>
above) are part of the =
same installation (i.e., they have the same value), and assumed to be on th=
e same host9997
If there are changes to the way Uptime Infrastructure Monitor is deploye= d on the network, you need to modify the Apache Web server configuration fi= le, accordingly:
Deployment Change | Affected Proxy Setting |
---|---|
change the API hostname or move the API to anoth= er server | <controllerHost> |
change the API port | 9997 |
when on running on different servers, the Monito= ring Station's network location is changed |
|
After making any change, restart the up.time Web Server
ser=
vice (on the correct Uptime Infrastructure Monitor instance, if applicable)=
to apply these changes. Then verify that you correctly configured the prox=
y by browsing to https://<uptimeMonitoringStation>/api
. =
The behavior should be identical to browsing to the up.time Controller at <=
code>https://<uptimeController>/api.
The following list details several common up.time Controller configurati= on tasks.
Task | Setting | Configuration Location in <uptimeDirect=
ory>\controller\ |
Notes |
---|---|---|---|
change Controller port | up.time Contoller port | \etc\jetty-ssl.xml |
To change the port, find this line within =
jetty-ssl.xml : <Set name=3D"Port"><Property name= =3D"jetty.port" default=3D"9997"/></Set> Update the |
change Controller DataStore target | database connection settings | \resources\uptime-controller.conf =
td>
| Example connection fields and options are pro= vided for all supported DataStore back-end platforms. By default, the up.ti= me Controller uses a standard MySQL DataStore connection (unless you update= d these values during installation). dbType=3DMYSQL To change the connection= details, update these fields with your database platform information. Ther= e are example entries in the configuration file. After you have updat= ed your settings, restart the up.time Controller service. |
indicate where PHP sessions are stored | PHP session directory | \resources\uptime-controller.conf =
td>
| By default, the
|
change Controller logging level |
logging level | \resources\uptime-controller.conf =
td>
| The Controller automatically logs events in t=
he
By default, the logging level is Aft= er you have updated your settings, restart the up.time Controller service.<= /span> |
install new Controller SSL certificate | SSL communication |
|
To install a new key, follow steps 3 and 4 from = the How to Co= nfigure SSL Page, and then restart the up.time Controller service. |