Resolve Intermittent Ingestion Drop for Google SecOps HTTPS Endpoints
How to resolve dropped ingestion volume when exporting to Google SecOps via HTTPS.
Overview
On February 24, 2026, we identified an issue affecting Google SecOps customers using Bindplane collectors with HTTPS endpoints. The Chronicle HTTP exporter treated certain server responses (429, 502, 504) as permanent failures instead of retrying, causing logs to be dropped during transient errors.
This issue was resolved in collector version v1.94.2. Customers running earlier versions should upgrade to restore correct retry behavior.
Affected status codes:
429— Rate limit exceeded502— Bad gateway504— Gateway timeout
Fix: Upgrade collectors to v1.94.2 or later.
Who is affected?
Collectors using the Google SecOps (Chronicle) destination configured with the HTTPS export method. Collectors using the gRPC export method are not affected.
How to check if you were affected
You can monitor impact by checking Traffic by response code in your GCP project's Chronicle APIs ImportLogs methods for 429 errors. If you see 429 responses during the incident window, your collectors were likely dropping data.
How to upgrade
Before updating, review your organization's update methodology and versioning guidelines. Catching up on collector versions before a Bindplane update is generally recommended. Please reference documentation on Updating the Bindplane Distro for OpenTelemetry Collector.
Option 1: Bindplane UI
Navigate to the Collectors page
To upgrade a single collector, click the upgrade link next to the collector's version number
To upgrade multiple collectors, select the outdated collectors and click the bulk upgrade button
Option 2: Bindplane CLI
List connected collectors to identify those that need upgrading:
Then update each collector:
Option 3: Re-run the install script
For in-place upgrades, re-run the collector install script. This approach is not recommended for most environments but may fit certain versioning strategies.
The install script is also accessible from the Collectors page via the Install Collector button.
How to verify
After upgrading, confirm collector versions from the Collectors page in the UI, or via the CLI:
Verify the version shows v1.94.2 or later for all affected collectors.
References
Last updated
Was this helpful?