Ask Vörr about your system
With the Vörr connector in place, ask questions in plain English from Claude or ChatGPT, inspect the evidence behind each answer, and distinguish a verified result from a coverage gap.
Start with a specific question
Name the service, resource, repository or environment whenever possible.
- What is the checkout service exposed to and what does it depend on?
- If this database goes down, what breaks?
- Where in the code is the payment timeout configured?
- Is checkout erroring? Show me the last 15 minutes.
- Why did the latest payments deployment fail?
Let Vörr choose the relevant sources
Vörr determines which connected systems can answer the question and queries them. A source that does not support the requested capability is not used.
Review provenance
Before relying on the answer, check:
- Which source produced each fact
- Whether the service match was explicit, inferred or unmapped
- Whether the relevant repository, cloud account or live-signal source was connected
- Whether scan or monitoring coverage was complete
Distinguish absence from missing data
“No resources found” is meaningful only when Vörr successfully scanned the relevant area.
If a source is unavailable, unconnected, unsupported or only partially scanned, Vörr reports the limitation instead of turning it into a false zero.
Continue the investigation
Use follow-up questions to move from a high-level answer to the underlying evidence:
- Which dependency creates the largest blast radius?
- Show the resource configuration behind that conclusion.
- Which recent deployment overlaps with the error increase?
- Which repository and file define this behaviour?
- Where did each result come from?
Unsaved conversations expire after seven days. Save a conversation when you need to retain it.