Documentation overview
Choose the right guide for planning, operating, administering, automating, and supporting Capuris.
Choose a starting point
Capuris documentation follows the lifecycle of packet evidence: deploy a capture point, record traffic, find the relevant packets, analyze what happened, and preserve the result. Start with the guide that matches the job in front of you.
| If you need to… | Read… |
|---|---|
| Compare physical and virtual capture options | Capture appliances |
| Rack, connect, and validate a new system | Deployment and quick start |
| Configure recording or search packet history | Capture and search |
| Manage access, networking, monitoring, or storage | Control administration |
| Automate a capture or search workflow | Control API reference |
| Explore traffic relationships and reports | Insight analytics |
| Install or maintain the analytics platform | Insight administration and deployment |
| Run distributed analytics workloads | AI workload deployment |
| Diagnose a fault or prepare a support case | Support and troubleshooting |
| Apply packet evidence to a common incident | Use cases |
| Find a short product answer | Product FAQ |
Product names used in these guides
| Name | Meaning |
|---|---|
| Capuris Capture Appliances | The physical packet-recording family |
| Capuris Capture P1 | Portable capture system |
| Capuris Capture R1 | 1U rack-mounted capture system |
| Capuris Capture R2 | 2U rack-mounted capture system |
| Capuris Capture Virtual | Software capture deployment |
| Capuris Control | Browser interface for capture and appliance administration |
| Capuris Control API | Automation interface for Capuris Control |
| Capuris Insight | Search, relationship analysis, reporting, and visualization platform |
| Capuris AI | Workload orchestration for distributed analytics |
A reliable operating pattern
- Confirm that management access, capture links, storage, and time synchronization are healthy.
- Record the smallest time window that still contains the event, while retaining the original capture when the investigation is sensitive.
- Narrow the traffic by endpoint, protocol, port, VLAN, or expression.
- Compare the result with a known-good interval or a second observation point.
- Export a focused PCAP and record the time zone, filters, capture location, and conclusion.
Before using a procedure
Interface labels and available features vary by release, appliance model, adapter, and license. Confirm disruptive operations in a maintenance window, especially capture deletion, service restarts, storage changes, mirroring, and software updates. Replace placeholders such as <HOST>, <TOKEN>, and <PORT> with values approved for your environment.