AMD Validated Reference Architecture: Data Storage for GPU-Accelerated AI

Learn More

Velocity • Durability

Book a Briefing
Contact Sales
Book a Briefing
Book A Demo
Contact Sales
Contact Sales
Documentation

VDURA Sentinel User Guide

Download PDF

1. Introduction

1.1 What VDURA Sentinel Is

VDURA Sentinel is VDURA’s cloud-hosted fleet monitoring console. Where Vantage and PanActive Manager manage a single realm from inside that realm, VDURA Sentinel sits outside every realm and watches all of them at once: it aggregates telemetry, alerts, capacity, and support tickets across every customer site VDURA supports, and layers AI-generated analysis on top (health summaries, diagnostic report findings, and a natural-language “Ask Sentinel” question box).

VDURA Sentinel is reached at https://sentinel.vdura.dev/.

1.2 How VDURA Sentinel Relates to Vantage, PanActive Manager, and panctl

These are complementary tools operating at different scopes:

  • Vantage and PanActive Manager are per-realm consoles: you point one at a single realm’s own address and manage only that realm.
  • panctl is a per-realm command-line client, same scope as Vantage.
  • VDURA Sentinel is fleet-wide: one login shows every realm across every site VDURA monitors, without needing network access to any of them individually. Realm telemetry reaches VDURA Sentinel by the realm’s own on-site appliance pushing data to the cloud; VDURA Sentinel does not dial into a realm to pull data live.

VDURA Sentinel deep-links out to the other tools rather than replacing them: a realm’s detail page has a PanActive link that opens that realm’s own legacy UI directly, and a ticket’s ID links out to the underlying Jira Service Management issue. VDURA Sentinel’s own device view (see 10) additionally mirrors a slice of Vantage/PanActive’s own screens (dashboard, volumes, alerts, nodes) read-only, sourced from the same pushed telemetry rather than a live connection to the realm.

Push-only, by design. Each site’s on-site appliance reads its own realms and, if the customer has enabled sharing, periodically sends a summarized snapshot to VDURA Sentinel. Nothing ever connects into the customer’s network: VDURA Sentinel cannot dial into a realm, and it cannot even ask a site to send something on demand, only receive whatever the site chooses to send and however often it chooses to send it. See 8.3 for how this same posture shapes diagnostic captures.

Where the on-site agent comes from. The agent that reads each site’s realms and sends data to VDURA Sentinel is built into PanFS on V5000 systems (from PanFS 12.x), and is a standalone container on legacy hardware. See 15 for details.

1.3 Audience and Scope of This Guide

This guide is written for VDURA support and operations staff who use VDURA Sentinel to monitor the health of the fleet, investigate alerts and tickets, and get AI-assisted answers about a site’s or realm’s condition. It walks through every page, panel, and control in the UI.