Skip to content

For voltage park infrastructure and model engineering teams

Voltage Park Kubernetes: pod restart, input failure or GPU event?

Compare pod lifecycle with the first application exception and existing telemetry. Add a workload handoff alongside the platform monitoring already in place.

Replay one resolved incidentTry 30 days free

Free 30-day Team evaluation. No card or automatic subscription. Work email verification required.

Live diagnosis, no signup

Replay a resolved Voltage Park workflow incident

Upload your log file. Review the selected evidence and masking, then run diagnosis. Keep the original log for any follow-up questions.

Before uploading, review cloud data handling and local options.

training_logs.txt
No log to hand? Try one:

Upload your log file. Large files are processed in your browser. Only selected evidence is submitted when you run diagnosis.

3 free diagnoses/day

Try Denpex for 30 days. FREE.

No credit card. No automatic subscription. See whether Denpex helps with an incident you already understand.

Start your free 30-day Team evaluation

Up to 50 diagnoses a day for 30 days. Verify your work email to activate an eligible company evaluation, then replay a resolved incident and compare the evidence and next steps with your team's confirmed cause.

Use your company email (e.g. alex@yourcompany.com). Eligible company domains can activate a free 30-day Team evaluation (up to 50 diagnoses/day) after email and domain checks, regardless of mail host. Uncertain domains can request review from support@denpex.com. Free local diagnoses remain available without an account.

What a useful evaluation should establish

Compare one incident your team has already resolved with the first failure, quoted evidence and remaining questions. Begin with this question: What ended the affected container? Only assign a process, device or recovery state when the submitted evidence establishes it.

What ended the affected container?

Evidence to compare: Pod termination reason, restart sequence and retained worker output.

A restarted pod can hide an earlier process error. Review the first failed attempt and its resource context before treating a fresh container as a new incident.

Did the data path precede the collective failure?

Evidence to compare: Input-reader exceptions, storage events and timestamped worker progress.

Use the actual mount and storage evidence. A known storage product alone does not prove a storage fault or justify changing the whole platform.

What did platform recovery actually restore?

Evidence to compare: Control-plane recovery events and separately verified workload artifacts.

Restoring cluster state and recovering training progress are different operations. Check model artifacts and job state independently before recommending resume.

Use Denpex alongside your existing telemetry tools to investigate submitted incident evidence. With monitoring configured on a supported plan, detected failures can trigger alerts and an automatic diagnosis from the captured evidence.

Inside Denpex

See the evidence, not just the claim

Follow the causal chain, inspect the quoted evidence and prepare the next handoff. These actual product captures use founder-account examples and the VS Code extension, with the source identified under each image. Open a capture to inspect it at full size.

Follow the failure through the cascade

Denpex founder-account example: a causal graph connects an Xid 48 ECC event to a rank exit and downstream collective failures, with quoted evidence for each stage.
Live founder-account capture from the bundled NCCL/ECC example. Follow the hardware event, rank exit and downstream symptoms with a supporting log quote at each stage.Inspect original image

Prepare the hardware escalation

Denpex hardware handoff summary asks the operator to capture diagnostic evidence and verify RMA eligibility with the vendor.
Actual hardware handoff summary from the same founder-account example. Capture diagnostic evidence before an approved reset, then confirm RMA eligibility with the vendor.Inspect original image

Ask for the evidence that is missing

Denpex historical example says a collective timeout does not establish the initiating rank, cause or failure domain and requests distinguishing evidence before a remedy.
Founder-account example restored from history. The original timeout remains unattributed, and the UI keeps the missing-evidence assessment visible.Inspect original image

Keep the investigation in the editor

Denpex VS Code extension displaying a bundled OOM-before-NCCL example, matched log evidence, verification guidance and an investigation handoff.
Actual VS Code extension capture of the bundled OOM-before-NCCL example. Review matched log evidence, verification guidance and the investigation handoff without leaving the editor.Inspect original image