pcapillaryTry the prerelease
Use cases

Packet capture for the infrastructure your team actually supports

When an issue is intermittent, remote, or distributed across Kubernetes and native servers, Pcapillary gets packet evidence to the people investigating without the usual access and file-transfer work.

01

Troubleshoot a hard-to-reproduce application issue

Capture the next occurrence without leaving a terminal running or relying on someone to save and transfer the right file.

  • Target the application endpoints and ports
  • Set a narrow observation window
  • Search the result as soon as packets arrive
02

Support a remote site or bare-metal server

Collect evidence without a remote shell, remote desktop, or screen-share walkthrough on the affected system.

  • Start the capture from a shared dashboard
  • Avoid command-line choreography
  • Keep results available to the investigation team
03

Investigate Kubernetes service traffic

Bring node and service-aware capture into the same workflow your team uses for standalone infrastructure.

  • Connect cluster nodes with the collector DaemonSet
  • Use consistent capture scope across environments
  • Review returned evidence centrally
04

Analyze a remote interface live in Wireshark

Work in Wireshark while traffic streams from the selected collector interface—without copying a capture file first.

  • Issue temporary scoped credentials
  • Limit the session to one collector interface
  • Revoke access or let it expire when the work is done
05

Validate a suspected security event

Move from an alert or timestamp to packet evidence with a documented source and time window.

  • Capture only the relevant traffic
  • Preserve collector and session context
  • Export a focused PCAP for specialist analysis