VDURA today announced VDURA Sentinel™, a proactive support capability included with the VDURA® Data Platform V12. Sentinel runs natively on the platform, watching continuously for faults and other notable events. Customers can share that health data with VDURA’s support team through the Sentinel cloud service, where it is analyzed against patterns drawn from thousands of VDURA systems in the field. When Sentinel spots an issue, it automatically opens a service request with VDURA support, complete with a proposed fix, often before anyone on site knows there’s a problem.
For operators running GPU clusters, the cost of a storage fault is measured in the hours between the fault and the fix: idle accelerators, stalled training jobs, and for a neocloud, tenant SLAs at risk. Conventional storage support adds delay at every step. Someone notices a symptom, files a ticket, gathers logs, describes the problem, and waits for a technician to work out what happened. Sentinel removes that cycle.
Sentinel continuously reads health, capacity, and alert telemetry from each system and compares it against failure patterns VDURA has resolved across thousands of systems in the field. When a pattern matches, the VDURA support team receives a plain-language summary, a trend view, and a recommended action, with the service request already open and, where needed, a parts dispatch initiated on the customer’s behalf. The first person to look at the ticket is looking at a diagnosis, not a blank page.
Sentinel is built on the same API-first foundation as the rest of the V12 platform. The collector gathers its telemetry through the platform’s published APIs, and everything Sentinel sees is equally available to the customer’s own dashboards and observability tooling. There is no privileged vendor-only view: operators get fleet-level observability into their storage as a first-class part of the platform, and VDURA support sees only the subset the customer chooses to share.
Built for security-conscious infrastructure teams
AI factories and GPU cloud providers operate under strict data-handling and tenant-isolation requirements, and many will not accept a vendor agent with write access or an opaque telemetry stream. Sentinel was designed around those constraints:
Read-only, outbound-only. The collector runs inside the customer’s environment with read-only credentials and makes only outbound HTTPS connections. There is no inbound access and no ability to change configuration or touch data.
File data never leaves the building. Sentinel does not transmit file contents, credentials, user or workload information, or logs. Only four categories of operational metadata can be shared: fleet health and capacity metrics, node inventory, alerts, and deep-dive diagnostics.
Per-category control, no support call required. Each of the four categories can be switched off independently, or all sharing can be disabled entirely, by the customer at any time. The local dashboard and the underlying storage are unaffected either way.
Inspect before it ships. A built-in payload inspector shows the exact contents of every outbound push before it is sent.
Auditable code. VDURA publishes the collector as dependency-free, readable Python so customer security teams can review exactly what it does.
Availability
Sentinel is included with the VDURA Data Platform V12 release, including the local fleet health dashboard and API access to the underlying telemetry. Proactive service requests and parts dispatch are delivered through VDURACare Premier, VDURA’s 10-year support offering that covers hardware, software, and 24×7 expert response under a single contract.
Learn more: vdura.com/vdura-sentinel-support
Related
This entry was posted on September 15, 2026 at 9:00 am and is filed under Commentary with tags VDURA. You can follow any responses to this entry through the RSS 2.0 feed.
You can leave a response, or trackback from your own site.
VDURA Launches Sentinel: Storage Support That Opens the Service Request Before the Customer Sees a Fault
VDURA today announced VDURA Sentinel™, a proactive support capability included with the VDURA® Data Platform V12. Sentinel runs natively on the platform, watching continuously for faults and other notable events. Customers can share that health data with VDURA’s support team through the Sentinel cloud service, where it is analyzed against patterns drawn from thousands of VDURA systems in the field. When Sentinel spots an issue, it automatically opens a service request with VDURA support, complete with a proposed fix, often before anyone on site knows there’s a problem.
For operators running GPU clusters, the cost of a storage fault is measured in the hours between the fault and the fix: idle accelerators, stalled training jobs, and for a neocloud, tenant SLAs at risk. Conventional storage support adds delay at every step. Someone notices a symptom, files a ticket, gathers logs, describes the problem, and waits for a technician to work out what happened. Sentinel removes that cycle.
Sentinel continuously reads health, capacity, and alert telemetry from each system and compares it against failure patterns VDURA has resolved across thousands of systems in the field. When a pattern matches, the VDURA support team receives a plain-language summary, a trend view, and a recommended action, with the service request already open and, where needed, a parts dispatch initiated on the customer’s behalf. The first person to look at the ticket is looking at a diagnosis, not a blank page.
Sentinel is built on the same API-first foundation as the rest of the V12 platform. The collector gathers its telemetry through the platform’s published APIs, and everything Sentinel sees is equally available to the customer’s own dashboards and observability tooling. There is no privileged vendor-only view: operators get fleet-level observability into their storage as a first-class part of the platform, and VDURA support sees only the subset the customer chooses to share.
Built for security-conscious infrastructure teams
AI factories and GPU cloud providers operate under strict data-handling and tenant-isolation requirements, and many will not accept a vendor agent with write access or an opaque telemetry stream. Sentinel was designed around those constraints:
Read-only, outbound-only. The collector runs inside the customer’s environment with read-only credentials and makes only outbound HTTPS connections. There is no inbound access and no ability to change configuration or touch data.
File data never leaves the building. Sentinel does not transmit file contents, credentials, user or workload information, or logs. Only four categories of operational metadata can be shared: fleet health and capacity metrics, node inventory, alerts, and deep-dive diagnostics.
Per-category control, no support call required. Each of the four categories can be switched off independently, or all sharing can be disabled entirely, by the customer at any time. The local dashboard and the underlying storage are unaffected either way.
Inspect before it ships. A built-in payload inspector shows the exact contents of every outbound push before it is sent.
Auditable code. VDURA publishes the collector as dependency-free, readable Python so customer security teams can review exactly what it does.
Availability
Sentinel is included with the VDURA Data Platform V12 release, including the local fleet health dashboard and API access to the underlying telemetry. Proactive service requests and parts dispatch are delivered through VDURACare Premier, VDURA’s 10-year support offering that covers hardware, software, and 24×7 expert response under a single contract.
Learn more: vdura.com/vdura-sentinel-support
Share this:
Like this:
Related
This entry was posted on September 15, 2026 at 9:00 am and is filed under Commentary with tags VDURA. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.