TL;DR a readily comprehended system snapshot on an everyday browser page

MonDeSi has been around since 2008.  Perhaps it's time to draw some more
attention to it.  This article should be read in conjunction with the
attached images.  Rather than just point in the direction of the READMORE
page (which does provide detailed usage plus installation plus configuration
detail) this intends be more descriptive and leave the detail to the
aforementioned document.

There are a small number of system performance/visualisation/behaviour tools
available for VMS.  Sophisticated, big-iron tools such as T4 and VMSSPI.

T4 (Total Time Tracking Tool)
-----------------------------

  "Pulling from several independent yet cooperating sources, T4 lets you
   create a relatively compact composite timeline view of the day-to-day
   performance of each important OpenVMS node. The statistics are collected
   by leveraging different collectors ... such as MONITOR and FC_MON, are
   packaged into a ZIP file ... [and] interpreted using analyzers."

  https://vmssoftware.com/products/t4/

VMSSPI
------

  "VSI VMSSPI for VSI OpenVMS collects information on OpenVMS system events,
   sends alerts to email or Slack, and provides interfaces to popular
   enterprise monitoring and alerting services such as DataDog, Splunk,
   and Dynatrace. You can also install action scripts that are run
   automatically when a particular event occurs."

  https://vmssoftware.com/products/vmsspi/
  https://vmssoftware.com/docs/VMSSPI-User-Guide-V9.0-9.pdf

Along with the more arcane but supplied with the (non-X86) distribution ...

TDC (The Performance Data Collector)
------------------------------------

  "The Performance Data Collector (TDC) for OpenVMS provides a C and
   C++ API for managing collection and processing of performance-related
   metrics ... both file-oriented and live processing of collected data."

  https://vmssoftware.com/products/tdc-rt/
  $ DIRECTORY SYS$COMMON:[TDC]

As well as the probably long obsolete HP ECP (Enterprise Capacity Planner).

I HAVE NO EXPERIENCE with the above tools and so can offer no opinion on the
management or capability.  VMSSPI looks particularly impressive.

Then there is the venerable, less sophisticated, in-built Monitor utility.

MONITOR
-------

  "The Monitor utility (MONITOR) is a system management tool used to obtain
   information about operating system performance. MONITOR allows you to
   monitor classes of systemwide performance data (such as system I/O
   statistics, page management statistics, and time spent in each of the
   processor modes) at specifiable intervals ... MONITOR collects system
   performance data ... produces the following three forms of ... output:
     o  A disk recording file in binary format
     o  Statistical terminal displays
     o  A disk file containing statistical summary information in ASCII"

  https://wiki.vmssoftware.com/MONITOR
  https://wasd.vsm.com.au/help?key=MONITOR&title=VMS%20Help&referer=none

The author had the late '80s experience of employing Monitor to collect
ongoing binary data for a large team project's VAX systems, generating weekly
utilisation statistics (and from those, crude homebrew ASCII timeline graphs)
for a contractor monitoring that project systems expectations and
requirements were being achieved (i.e. everything was not always maxed-out).

Using the basic utilisation data provided by the underlying system service
employed by Monitor, along with additional data accumulated using other
approaches, brings us (finally) to MonDeSi***

MONDESI
-------

  "MonDeSi (pronounced "mon-deh-sih") is a browser-based VMS system
   monitor with a sufficiently small resource footprint** to not impact
   system performance ... [**YMMV with platform and selected items but
   on an AlphaServer DS20E and HP rx2660 significantly less than 0.001
   of a CPU] ... MonDeSi is intended as a general tool for system
   observation. It is not a troubleshooting tool as such ..."

The need MonDeSi attempts to address is a simply and RAPIDLY COMPREHENDED,
yet COMPREHENSIVE VIEW of current and immediately past RESOURCE UTILISATION.
A SYSTEM SNAPSHOT if you will, rolling much of the disparate data offered by
the Monitor utility (plus some) into a single glance.

  o  system CPU, memory, I/O, locking, network, cluster and disk activity
  o  5 or 15 minute line graph history of the above data
  o  top five processes consuming CPU, page faults and I/O
  o  comprehensive data for a selected process
  o  5 or 15 minute history of that process' CPU, memory usage and I/O
  o  OPCOM message count with most recent timestamp, recent messages log

The attachment MonDeSi.png provides a comprehensive overview of the display;
MonDeSi_modes.png provides an [X]x2 view expanding on the CPU modes display;
MonDeSi_15mins.png shows a portion of the display with [X]15 Minutes checked.
All images have been generated from an X86 VMS system with WASD being
exercised using OWASP ZAP from a separate system over a 1Gbps LAN.

A live demonstration (limited functionality) courtesy of DECUServe

  https://eisner.decuserve.org/cgiplus-bin/mondesi

The current release overview

  https://wasd.vsm.com.au/wasd_root/src/mondesi/readmore.html

And may be downloaded

  https://wasd.vsm.com.au/wasd/

*** MonDeSi was built on top of core concepts employed in the mid-'90s
HyperSPI application (lots were "Hyper.." in those heady days :-)
Developed to provide the user community with a similar system/cluster
utilisation overview to that described by the MONITOR anecdote.  Still part
of the WASD distribution, though perhaps is (well past) time to be retired.

  https://wasd.vsm.com.au/wasd_root/src/hyperspi/readmore.html

This item is one of a collection at
https://wasd.vsm.com.au/other/#occasional