Skip to main content

Cribl Stream REST Collector Does Not Collect Non-2xx Response Bodies

  • Nov 19, 2026 8:36 PM UTC
  • 0 replies
  • 1 view

Jessica Bracken

Symptom

After upgrading Cribl Stream, a REST Collector that previously emitted events for non-2xx responses may stop emitting them. REST Collector reports non-2xx responses as errors rather than producing events.

Environment

  • Cribl Stream 4.19 or later
  • REST Collector

Resolution

  1. Navigate to Products > Stream > Worker Groups.
  2. Select the relevant Worker Group.
  3. Navigate to Data > Sources.
  4. Select Health Check.
  5. Click Add Collector.
  6. Configure the Health Check Collector to query the endpoint whose non-2xx responses you need to collect.

Cause

This can occur due to Cribl Stream 4.19 REST Collector behavior: 2xx responses produce events, while non-2xx responses are reported as errors and do not produce events. This explains why a previously working collection may stop emitting events after an upgrade. Configured retries are honored as usual.

Additional Information

The Health Check Collector reports non-2xx responses as error events and includes the response body in the error details, rather than emitting it as a normal event. See the Health Check Collector documentation.