|
1 | 1 | deepsee-sysmon-dashboard |
2 | 2 | ============== |
3 | 3 |
|
4 | | -A small set od DeepSee dashboards for selected system monitor metrics - data collected by %SYSMONMGR utility |
| 4 | +A small set od DeepSee dashboards for selected system monitor metrics - data collected by %SYSMONMGR utility. |
| 5 | + |
| 6 | + |
| 7 | +Installation |
| 8 | +------------ |
| 9 | + |
| 10 | + |
| 11 | +1. Download Installer.cls.xml (from cls/kutac/monitor/utils folder in repository or releases page) into Caché manager directory. |
| 12 | +2. Run in terminal (any namespace) under user with %All role: |
| 13 | + |
| 14 | + do ##class(%Installer.Installer).InstallFromCommandLine(##class(%File).ManagerDirectory()_"Installer.cls.xml","Namespace={Namespace}") |
| 15 | + |
| 16 | + where: |
| 17 | + |
| 18 | + {Namespace} is a namespace you want to install to. If it does not exist it would be created automatically. If it does exist only kutac package would be overwritten. If {Namespace} is not defined, then SYSMON namespace will be created. |
| 19 | + On this step installer would create (if needed) Namespace and corresponding database, download source code from GitHub and compile it, create required web application (named /cls/{Namespace}) if one does not exist (skipping web application creation process if one does exist), and map kutac package to %All namespace (which will be created if it does not exist). |
| 20 | + |
| 21 | + |
| 22 | +Installation without fs access to server |
| 23 | +----------- |
| 24 | +1. Download Installer.cls.xml (from MDX2JSON folder in repository or releases page) into Caché Studio (any namespace) |
| 25 | +2. Run in terminal (any namespace) under user with %All role: |
| 26 | + |
| 27 | + set pVars("Namespace")="{Namespace}" |
| 28 | + do ##class(MDX2JSON.Installer).setup(.pVars) |
| 29 | + |
| 30 | + where: |
| 31 | + |
| 32 | + {Namespace} is a namespace you want to install to. If it does not exist it would be created automatically. If it does exist only kutac package would be overwritten. If {Namespace} is not defined, then SYSMON namespace will be created. |
| 33 | + On this step installer would create (if needed) Namespace and corresponding database, download source code from GitHub and compile it, create required web application (named /cls/{Namespace}) if one does not exist (skipping web application creation process if one does exist), and map kutac package to %All namespace (which will be created if it does not exist). |
| 34 | + |
| 35 | +Offline Installation |
| 36 | +----------------- |
| 37 | + |
| 38 | +1. Download zip and unpack it. |
| 39 | +2. Run in terminal (any namespace) under user with %All role: |
| 40 | + |
| 41 | + do ##class(%Installer.Installer).InstallFromCommandLine("{SourceDir}cls\kutac\monitor\utils\Installer.cls.xml","Namespace={Namespace},SourceDir={SourceDir}") |
| 42 | + |
| 43 | +On this step installer would create (if needed) Namespace and corresponding database, import source code and compile it, create required web application (named /cls/{Namespace}) if one does not exist (skipping web application creation process if one does exist), and map kutac package to %All namespace (which will be created if it does not exist). |
| 44 | + |
| 45 | +Default Settings |
| 46 | +---------------- |
| 47 | + |
| 48 | +After mapping kutac package to %All namespace, namespaces %SYS and {Namespace} will be defined as startup namespaces for monitor. Then, the installer activates in the namespace %SYS" following monitor classes: |
| 49 | + |
| 50 | +* %Monitor.System.HistoryPerf |
| 51 | +* %Monitor.System.Diskspace |
| 52 | +* %Monitor.System.License |
| 53 | +* %Monitor.System.Processes |
| 54 | +* %Monitor.System.HistorySys |
| 55 | +* %Monitor.System.Freespace |
| 56 | +* %Monitor.System.LockTable |
| 57 | +* %Monitor.System.Routines |
| 58 | + |
| 59 | +The next step is starting monitor. Your namespace will appear in the list of accessible namespaces for DeepSee and you can see different dashboards there. However, if you open User Portal in the DeepSee immediately after installing, you will notice that all dashboards will be empty. You need to wait a little time, because the installer runs the task for rebuilding cubes in 1 minute after installing. This task will run every 3 hours for updating information for monitor dashboards. |
| 60 | + |
| 61 | + |
| 62 | + |
| 63 | + |
0 commit comments