The document describes Monitoring Performance History (MPH), a voluntary system monitoring tool that is part of Digital's Digital Product Performance (DPP) Program.
Purpose: MPH aims to improve the reliability and availability of Digital systems by collecting performance data from participating customer and Digital sites.
How it Works:
- MPH resides on participant systems with negligible impact on performance or security.
- It collects error log entries, crash dump summaries, and configuration information.
- This data is automatically sent weekly to the DPP group via mechanisms like DSNLink or Internet mail.
- DPP analyzes the information and generates reports for Digital's engineering, manufacturing, and services teams to improve system reliability.
- All collected data is classified as Digital Confidential and used for internal purposes only.
- The process is fully automated, runs as a background task, and requires approximately 300 blocks of disk space.
Key Features/Updates in Version 1.4:
- Offers upgrades to existing installations.
- Allows error log data collection on a weekly or daily basis.
- Includes improved space management to prevent impact from large error logs.
- Provides safeguards and warning messages, notifying system managers about DSNLink problems or large error log changes.
- Enables adding or deleting monitored nodes in a cluster post-installation.
- On field-test OpenVMS systems, it may also install Remote Performance Monitoring Software (RPM) to gather performance trend data related to reliability.
Management: MPH can be installed, stopped, and deinstalled using specific system commands. Participation is voluntary and requires no special maintenance agreement.