Configuring a capture is the cumbersome part: which workloads to attach, which port speaks which protocol, which templates and tags will turn raw calls into something a human can read. The Capture Advisor does that work from what Spider already sees.
From a namespace to a working capture
Pick a namespace. From the cluster map, with no whisperer needed, the Advisor proposes the workloads to attach, the ports to parse with the protocol each one speaks, and the configuration changes that make it so. Uncertain ports can be probed for a few minutes. Nothing is written until you confirm: a dry run shows the plan first, then an apply attaches, observes a window with content saving on, and puts the observation settings back. Cancel a run and everything it added is removed.
Make the data readable
From the captured traffic, the Advisor suggests templates and tags for every parsed protocol, each one checked with the parser’s own playground before you see it: Get order instead of GET /orders/8f3a.... Its Link ids pass finds the business id that travels across protocols and services (an order id in a URI, a header, a Redis key, a Kafka record, an SQL statement) and proposes one concept name with the rule that extracts it everywhere.
Where you use it
In the Network-View wizard, in the spider command line, and from AI agents through the MCP server and the Claude plugin skills. It runs with the rights of the person using it and never suggests credentials. The Capture Advisor is part of the TEAM tier and above.