Incident investigation on NVIDIA Nemotron
The postmortem,
with its evidence.
Hand Hindsight an incident. It reads the logs, traces, commits and config changes, names what started the outage, and writes the postmortem. Every claim carries a tag back to the evidence it came from.
- Ceiling, oracle given the answer
- –
- Best shortcut without a model
- –
- Nemotron models, one per job
- 3
- Sample incidents ready to open
- –
How it works
- TriageNemotron Nano picks each lookup: logs, traces, commits, configs.
- DiagnosisNemotron Ultra reads the evidence and names the cause and how it spread.
- ResearchSearches published guidance, with nothing internal in the query.
- PostmortemNemotron Super writes it. Facts and citations are assembled in code.
Open an incident
Sample incidents have a known answer, so the investigation is graded when it finishes. Your own bundle is investigated the same way and never graded. Bundle format
How often it finds the cause
Share of generated incidents where the root cause named was the real one. The investigator never sees the answer, and a fixed rubric does the scoring, not a model. The first rows are the shortcuts a hurried engineer reaches for.
Investigations
Nothing investigated yet. Open an incident above.