Date: Fri, 29 Mar 2024 01:37:35 +0000 (UTC) Message-ID: <91213109.5579.1711676255380@ip-10-0-1-161.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_5578_880001867.1711676255369" ------=_Part_5578_880001867.1711676255369 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Prior to Uptime Infrastructure Monitor 7.3, plugin monitor= s were downloaded from the Grid an= d installed in Uptime Infrastructure Monitor with either the Plugin Manager= or the erdcloader command line tool. In Uptime Infrastructure Monito= r 7.3 and later, the integrated Extension Manager easily acquires and installs Plugins from within the UI. However, if the Upti= me Infrastructure Monitor monitoring station does not have direct access to= the Internet, the plugins will not be accessible for download. In th= is scenario, simply create a local plugin repository for the Extension Mana= ger to install from.
The Uptime Infrastr=
ucture Monitor Extension Manager feature is accessed by the Want more? Search for monitors link in the top right corne=
r of the Add Service Monitor window. The Extension Manager content is=
populated from http://the-grid.uptimesoftware.com/extension.j=
son. When a p=
lugin monitor is updated or a new one is added, the change is automatically=
reflected in the extension.json file (and the Extension Manager).
To enable the Exten= sion Manager to access the plugin monitors without Internet access, place a= copy of the plugin monitor files in a location that is accessible to the U= ptime Infrastructure Monitor Monitoring Station, and create a local extensi= on.json file where the plugin file paths point to the accessible location.<= br>
To create the new extension.json file, simply refer to the existin= g Grid file at http://the-grid.upti= mesoftware.com/extension.json.
If you need to upgrade a plugin monitor that is already installed,= download the new plugin zip file and also copy the updated info from the e= xtension.json file to update the entry in your local extension.json file.&n= bsp; You will not be able to upgrade the plugin unless the local extension.= json file is also updated.
Because you will likely use only a sm= all subset of the available plugin monitors, you can populate your local ex= tension.json file with only the plugin monitors that you are interested in.= The following example includes the File and Directory plugin and the= Enhanced Log Monitor plugin.
To c= reate your local extension.json file, you will need to cover the following = points:
This example local extension= .json file only contains the File and Directory and Enhanced Log monitor pl= ugins. You may include as many or as few as you desire.
[ { "category": "Operating System Monitors",=20 "supported_versions": [ "7.3" ],=20 "name": "File and Directory",=20 "git_file_target": "https://github.com/uptimesoftware/file-director= y-monitor/raw/develop/dist/file-directory-monitor.zip",=20 "icon_url": "http://the-grid.uptimesoftware.com/img/posts/placehold= er-logo.png",=20 "upgrade_in_place": true,=20 "requires_additional_setup": false,=20 "requires_agent_scripts": true,=20 "version": "4.0",=20 "supported_platforms": [ "windows",=20 "linux" ],=20 "grid_url_target": "http://the-grid.uptimesoftware.com/plugin/file-= directory-monitor.html",=20 "type": "plugin",=20 "description": "Monitor the number of files, largest size, and how = old the files are in a directory." },=20 { "category": "Operating System Monitors",=20 "supported_versions": [ "7.3" ],=20 "name": "Enhanced Log Monitor",=20 "git_file_target": "https://github.com/uptimesoftware/enhanced-logf= ile-monitor/raw/develop/dist/enhanced-logfile-monitor.zip",=20 "icon_url": "http://the-grid.uptimesoftware.com/img/posts/placehold= er-logo.png",=20 "upgrade_in_place": true,=20 "requires_additional_setup": false,=20 "requires_agent_scripts": true,=20 "version": "3.0",=20 "supported_platforms": [ "windows",=20 "linux" ],=20 "grid_url_target": "http://the-grid.uptimesoftware.com/plugin/enhan= ced-logfile-monitor.html",=20 "type": "plugin",=20 "description": "This monitor is designed for use with the Uptime mo= nitoring station and Windows, Linux, Solaris or AIX agents. It scans for ce= rtain log files on the agent system and searches the files for a specified = string (regex compatible). It will scan only new lines in files and not gen= erate alerts for older issues. It keeps track of this by using a bookmark (= in a temp file) so each time it runs it will simply go to the last position= in the file and continue scanning. It is designed to scan large (multi-GB)= as well as many files within a second." } ]
After creating your local= extension.json file, place it in the <uptime_dir>\GUI directory (or = another web location that the Uptime Infrastructure Monitor Monitoring Stat= ion server can access). If using <uptime_dir>\GUI, be sure that= no other files are modified; otherwise, the Uptime Infrastructure Monitor = web UI may not work properly. The web location of <uptime_dir>\= GUI\extension.json will be http://uptimehost:9999/extension.json.&= nbsp;
To have the Extension Manger use your local extension.json file, t= he following line needs to be added to the bottom of the <uptime_dir>= \uptime.conf file and the up.time Data Collector service needs to be restar= ted (uptime_core on Linux):
extension.browsing.url=3Dhttp://uptimehome:9999/extension.j= son
You should now be able to install Uptime Infrastructure Monitor pl= ugins without the Monitoring Station requiring direct access to the I= nternet (remember to occasionally check the Grid for plugin updates).
Note