Where this offering fits
Cribl Edge concerns collection and processing near telemetry sources. Evaluate it against supported hosts, source types and the operational cost of managing collection at scale. The deployment needs a device or host lifecycle plan as well as a working connection to a destination.
Architecture and rollout decisions
Confirm platform support, collection permissions and the selected management arrangement. Pilot representative hosts and measure collection behaviour under normal workload. Test configuration updates, interrupted connectivity and removal. Record who handles unhealthy collectors and how collected data is protected before it reaches central processing.
An evaluation scenario for this offering
Choose two representative test hosts for an Edge pilot: one with steady activity and one with an intermittent connection. Generate uniquely identifiable, harmless test records and verify which arrive at the intended destination. Apply an approved collection-setting change to one host first, checking its effect before wider rollout. Include removal or disablement under the documented procedure so support can recover a host when collection is inappropriate. Record host workload observations, source coverage, configuration state and destination evidence. The exercise should expose a collector that is installed but unhealthy, rather than counting installation alone as successful onboarding.
Evidence to request for this scope
- List supported source hosts and required permissions.
- Validate collection impact and configuration rollout.
- Test lost-connection and unhealthy-collector reporting.