Where this offering fits
The Gigamon Deep Observability Pipeline is a network-derived telemetry architecture. Evaluate how traffic is acquired, processed and delivered to the tools that need it. The architecture should identify visibility limits and capacity at each stage instead of implying that installing a pipeline makes all traffic observable.
Architecture and rollout decisions
Map physical, virtual and cloud sources and the receiving tools. Confirm selected components, licences and supported interfaces. Pilot representative flows and compare what each consumer receives with the agreed requirement. Review filtering, masking and encrypted-traffic handling with authorised owners. Operational acceptance should include overload and unavailable-tool behaviour for the proposed design.
An evaluation scenario for this offering
An illustrative pipeline pilot can follow two approved test flows: one needed by a security consumer and another needed by a performance tool. Record the source path and expected packet or metadata content for each output. Confirm what the selected transformations deliver to the actual receiving tools, including any intentional masking or filtering. Introduce an authorised unavailable-consumer condition and observe the documented response. Retain source-to-output mapping, representative captures or records and tool-owner validation. Successful delivery of one flow should not be extrapolated to unobserved cloud, virtual or physical paths outside the pilot’s acquisition boundary.
Evidence to request for this scope
- Document traffic sources and collection gaps.
- Validate delivered packets or metadata against tool requirements.
- Confirm capacity and approved data-handling controls.