DV Forge User Guide¶
DV Forge turns your nightly regressions into a short, shared list of distinct problems. Every failing simulation is fingerprinted and grouped into a signature, project-wide and across every run. Your team then triages signatures, not thousands of individual failures, and lets rules and the root-cause agent take the repetitive work.
flowchart LR
CI["CI / regression runner"] -->|dvforge upload| DP["Data plane<br/>(optional, in your network)"]
CI -.->|or directly| CP
DP -->|results, no raw logs| CP["DV Forge"]
CP --> SIG["Signatures"]
SIG --> TRI["Triage + rules"]
TRI --> AG["Root-cause agent"]
-
Get started
The ideas behind DV Forge, and your first regression to your first triaged signature in ten steps.
-
Send results
Push JUnit results and simulation logs from any CI with the
dvforgeCLI. -
Read signatures
How failures are bucketed, and how to merge, split and tune them.
-
Triage with your team
The triage lifecycle, the queue, comments, attachments and alerts.
-
Automate with rules
Trigger, scope, match, act: assign, classify, label and reopen without lifting a finger.
-
Keep logs in your network
Run a data plane next to your simulators; raw logs never leave.
Where to find things¶
| You want to… | Go to |
|---|---|
| Upload a regression from CI | The dvforge CLI, CI integration |
| See what failed last night | Regressions and failures |
| Understand why two failures share a signature | Signatures |
| Work through the open signatures | The triage queue |
| Assign, comment on or close one signature | Working a signature |
| Automate routine triage | Triage rules |
| Ask the agent for a root cause | Runs and hypotheses |
| Give someone access, or a token to CI | Projects, roles and tokens |
| Look up a filter field or an API endpoint | Reference |
Signing in
The web app lives at https://app.daruur.cloud. Access is by invitation: ask your organization's DV Forge administrator to invite you.