OpenVMS

Monitoring OpenVMS Servers with Modern Tools

OpenVMS has long been a cornerstone of mission‑critical computing, powering industries from finance to manufacturing.

CW

Chris Walker

4 min read
Two people looking at an iPad

OpenVMS has long been a cornerstone of mission‑critical computing, powering industries from finance to manufacturing. Historically, monitoring options were limited — tools like T4 provided basic performance data but lacked integration with modern observability platforms.

Today, thanks to VSI’s VMSSPI layered product, OpenVMS can send alerts to a wide range of monitoring solutions, including RabbitMQ, Splunk, Dynatrace, Slack, Datadog, PagerDuty, and even MQTT brokers. This opens the door to integrating OpenVMS into enterprise monitoring stacks alongside Linux, Windows, and cloud workloads.

VMSSPI: The Bridge to Modern Monitoring

VMSSPI acts as the interface between OpenVMS and external monitoring systems. Once installed and licensed, it runs as a set of processes that generate alerts and forward them to chosen endpoints. Configuration is handled through two files:

  • VMSSPI$CONFIGURATION.DAT – defines event classes and filters.
  • MESSAGES.TXT – specifies which monitoring modules to use (RabbitMQ,
    Splunk, etc).

By editing these files, administrators can control which events are sent and how they’re routed.

RabbitMQ + Prometheus + Grafana

One popular stack uses RabbitMQ as the message broker, Prometheus to scrape metrics, and Grafana to visualise them.

  • Alerts are routed into queues by severity (critical, major, minor, etc.).
  • Prometheus scrapes RabbitMQ’s endpoint for queue statistics.
  • Grafana dashboards then display alert counts and trends.

This approach scales well for large estates, offering aggregated statistics while avoiding performance hits from per‑object queries.

Splunk Integration

Splunk provides powerful search and visualisation capabilities.

  • Administrators create an HTTP Event Collector (HEC) token in Splunk.
  • VMSSPI is configured to send alerts using that token.
  • Events appear in Splunk’s search interface, where dashboards can be built in minutes.

Splunk’s flexibility makes it ideal for ad‑hoc analysis and reporting.

Dynatrace Monitoring

Dynatrace offers deep observability with AI‑driven insights.

  • VMSSPI is configured with a Dynatrace API v2 token (with scope).
  • Events flow into Dynatrace, where dashboards and “Problems” pages highlight issues.
  • Filters can be applied to focus on specific environments or event types.

For small estates, per‑object monitoring preserves data fidelity. For larger estates, aggregated statistics reduce payload size and improve performance.

Choosing the Right Approach

The choice of monitoring stack depends on scale and requirements:

  • RabbitMQ/Prometheus → best for large estates needing performance and scalability.
  • Splunk → strong for search, reporting, and quick dashboard creation.
  • Dynatrace → ideal for enterprises already invested in Dynatrace.

All approaches benefit from VMSSPI’s flexibility, allowing OpenVMS to integrate seamlessly into modern observability ecosystems.

Conclusion

Monitoring OpenVMS servers no longer means relying on legacy tools. With VMSSPI, administrators can connect OpenVMS to RabbitMQ, Splunk, Dynatrace, and beyond. Gaining real‑time visibility, proactive alerting, and integration with enterprise monitoring strategies.

Whether you’re managing a handful of servers or a global estate, modern monitoring ensures OpenVMS continues to deliver reliability in today’s hybrid IT environments.

Leave a comment

Comments are reviewed before they appear publicly.

Comments (0)

No comments yet. Be the first to add one.