Last revision: 12/20/2023
This readme document contains important information about the AVEVA System Monitor 1.5 application. Refer this document for general system requirements, installation procedure, known issues, resolved issues, and System Monitor documentation included in the release.
What's New?
Sentinel System Monitor is now AVEVA System Monitor.
Before you install System Monitor, please review the information in this section.
Important! If you have a Sentinel 1.1 or Sentinel 1.1 SP1 installation, please refer to Tech Alert 423 in the Global Customer Support (GCS) website. It may be necessary to restore ArchestrA Service Bus services, which should be done prior to upgrading to System Monitor 1.5.
Also, if you want to uninstall Sentinel 1.1 SP1, please refer to Tech Alert 415 in the Global Customer Support (GCS) website. Install the Hotfix 7721 on the system prior to uninstalling System Monitor.
AVEVA System Monitor monitors and manages the performance and availability of your AVEVA System Platform system, including the core software, the engineered software application(s), license server and the related hardware and network infrastructure.
System Monitor detects and reports on system performance issues/errors/trends, monitors key system attributes and then generates alerts when those attributes exceed defined tolerance ranges.
When an attribute is out of tolerance, the customer support team (internal or systems integrator) is notified of the upset condition, and can respond quickly in order to prevent production interruption or downtime. The goal is to ensure that your solutions' performance meets and/or exceeds your expectations.
System Monitor 1.5 is an "on-premises" application, installed on a designated server-level computer. The following prerequisites are required for implementing System Monitoring:
System Monitor Manager (Production System)
Hardware Requirements
Size |
Level |
Cores |
RAM |
HDD Space |
Small System (1-20 Machines)
|
Minimum |
4 |
2 GB |
300 GB |
Recommended |
6 |
4 GB |
400 GB |
|
Medium System (21-50 Machines)
|
Minimum |
6 |
8 GB |
400 GB |
Recommended |
12 |
12 GB |
600 GB |
|
Large System (50+ Machines)
|
Minimum |
12 |
16 GB |
800 GB |
Recommended |
16 |
24 GB |
1 TB |
Installation requires the logged-in user installing System Monitor Manager software to be an administrator on the machine. Preferable to have sysadmin privileges in SQL server.
Software
AVEVA System Monitor is compatible with the latest software prerequisites for SP 2020R2. For more information about OS and MS SQL requirements, refer to the AVEVA System Platform 2020 R2 Readme.
Monitored Machines
See the GCS Technology Matrix for complete information about the supported operating systems.
Port List
Important! System Monitor uses the following listed ports by default. Ensure that no other applications are using the listed ports.
The FULL/Licensed mode of System Monitor 1.5 requires an activated license. You can install the License Manager and License Server on the System Monitor Management server or configure the system to point to a remote License Server.
Note:
- You must install System Monitor as a Standard account user. You cannot install System Monitor if you are a Service account user, because it will not have write permission to the Program Data folder.
- Before you reinstall System Monitor Manager on a machine, ensure that the pre-existing System Monitor Manager is uninstalled and System Monitor Database is deleted from the machine.
System Monitor Installation
Use the AVEVA System Platform common installer to install System Monitor for monitoring any AVEVA System Platform system of versions 2017 U3 or later.
On selecting the System Monitor Manager, the System Monitor Agent Install Manager is also selected and installed.
If not already present, .NET Framework 4.8 is installed as a prerequisite. This install requires a reboot of the machine.
Also, if a compatible version of Microsoft SQL Server is not present on the system, Microsoft SQL Express is installed as a prerequisite.
Note:
- Microsoft SQL Express is only recommended for small systems of 20 machines or less.
- System Monitor SSRS reports are unavailable for System Monitor installations using Microsoft SQL Express.
When you install SQL server express edition, the SQL server agent will not run and the following tasks of the AVEVA System Monitor Application will not work.
- psms_job_sendalertsforheartbeatmissing
- psms_job_forcegalaxydiscovery
- On demand job to Archive the Average time to resolve/accept alerts.
If not already present, .NET Framework 4.8 is installed as a prerequisite. This install requires a reboot of the machine.
Note:
- During an upgrade, there may be a delay up to 30 minutes before the agents on the remote machines get updates and reflect the new build ID.
- If an install is interrupted by system reboot or power failure, the installation gets corrupted and there is no option to resume, repair, or remove the partial installation. Therefore, it is recommended that you configure a restore point before installing System Monitor, as with the installation of other software.
After the installation, configure the application by running the Configurator. You can configure the following:
Refer to the AVEVA System Monitor User Guide for more information on configuration, launching the System Monitor Manager Console from a browser, and step by step instructions to manage system monitoring.
This section describes known issues in this release.
CR/Defect Number/Case Number |
Description |
Workaround |
202854
|
Manually specifying a proxy server in the Local Area Network (LAN) Settings configuration dialog results in inability to access the Sentinel Manager login screen. |
Use an automatic configuration script (provided by your IT department) to configure a proxy server. |
2885666 |
[Machine rename] Agent machine name in monitored machines screen is still showing old machine name. |
N/A |
2901078 |
40-Node: [SP2023R2]: During GR upgrade from WSP2017U3SP1P01 to SP2023R2, observed exceptions for adpHostSrv and LmxProxy components. |
N/A |
2630532 |
40-Node: [SP2023R2]: During GR upgrade from WSP2017U3SP1P01 to SP2023R2, observed EntityCommandExecution exceptions for psmsConsoleSrv component. |
N/A |
2885046 |
[SP2023R2][Case-Sensitive SQL Server] Logger errors occurred during the configuration of the configurator through silent installation. |
N/A |
2905394 |
[Domain Controller] Sentinel Service does not start on system startup. Missing Domain Controller. |
N/A |
This section describes the resolved issues in AVEVA System Monitor.
CR/Defect Number |
Service Request ID/ Case Number |
Description |
201646 |
N/A
|
On a fresh install, the Rule Overview page showed a Current Manifest Version value other than 1. The Manifest version listed on the Rules grid was supposed to show the value 1 because the out-of-the-box manifest was immediately published. However, the UI showed that the manifest had already been published more than once. |
201649 |
N/A |
Machines were added to the Monitored Machines list with an inaccurate date/time value under the Discovered Date column. |
202853 |
N/A |
Users could create multiple rules with the same name. |
202877
|
N/A |
On creating a rule to monitor a file or folder with a path longer than 100 characters, the rule was partially stored in the database and was not published in the agent manifest. |
202878 |
N/A |
On undeploying a platform that was being monitored, the Runtime Provider was stopped. Upon redeploying the platform, the Runtime Provider did not resume until the Galaxy was rediscovered |
202898 |
N/A |
"I'm Alive" emails were not sent consistently until 24 hours after enabling the notification. |
202906
|
N/A |
On reports with date parameters, the data returned was not inclusive of the end-date. |
608555 |
N/A |
Distorted UI occurred when downsizing the browser window or viewing the UI in a resolution less than 1440x900. |
623127 |
N/A |
Start Menu with the option to open AVEVA System Monitor Manager is installed on non-Manager nodes.
|
623129
|
N/A |
On uninstallation, System Monitor start menu options were not removed. |
1881074 |
N/A |
Multiple instances of the warning “Unable to add item ‘.ItemErrorCntAlarm.AlarmInhibit’ with access path‘’ were logged in the Logger when adding an item to a DASEngine. |
1436554 |
N/A |
It took up to five minutes for the Galaxy Diagram to reflect Alert changes to the Galaxy shape in Sentinel Manager. |
1655571 |
960134072 |
Resolved the alerts generated when the client could not connect to the license server or when the license server did not have an activated license. |
Web Help - Browser-based User Assistance
Web help components have been delivered in this release. Web help opens in the default browser on your local computer. Help displayed in a browser allows more dynamic and searchable user assistance including standard web browser navigation.
Typically, help content is installed on your local machine as part of the documentation library, and displays in your browser without requiring an Internet connection. To open the help, use one of the following methods (depending on the editor/UI you are using):
C:\ProgramData\AVEVA\Product Documentation\AVEVA System Monitor
Browser Permissions for Displaying Web Help
Each browser and Windows operating system combination has its own security permissions. Using Internet Explorer (version 8, 10, or 11) as an example, you may see a dialog requesting you to "Allow blocked content" each time you invoke the web help. This dialog is triggered by the presence in the help system of JavaScript components that control internal navigation and topic display elements such as pop-up or in-place-expanding display blocks that contain text and graphical images. The text and image content is itself non-active.
You can accept each occurrence of this dialog, or you can set the following option in Internet Explorer, depending on your IT security requirements: In Internet Options, click the Advanced tab, then navigate to the Security section. Enable the Allow active content to run in files on My Computer Permissions and security settings will vary depending on your specific browser.
The AVEVA System Monitor 1.5 application includes the following documentation set:
You can access the Help from the System Monitor Console User Interface.
The web help opens in a browser window.
To view PDF files, you need Adobe Reader installed on your computer. You can download the latest version of Adobe Reader from the Adobe Corporation web site:
After installing Adobe Reader, double-click on a PDF file to view the book with Adobe Reader. You can also open a PDF book with the Adobe Reader Open command from the File menu.
These documents are also available from the product installation files and the System Monitor download page.
The AVEVA System Monitor 1.5 Readme and the AVEVA System Monitor User Guide PDF are also available in the Documentation folder available in the path C:\ProgramData\AVEVA\Product Documentation\AVEVA System Monitor
|
© 2015-2023 AVEVA Group Limited and its subsidiaries. All rights reserved. | Contact Us |