> For the complete documentation index, see [llms.txt](https://docs.bindplane.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bindplane.com/how-to-guides/partner-integrations/google-secops/resolve-intermittent-ingestion-drop-for-google-secops-https-endpoints.md).

# Resolve Intermittent Ingestion Drop for Google SecOps HTTPS Endpoints

### Overview

On February 24, 2026, we identified [an issue affecting Google SecOps customers using Bindplane collectors with HTTPS endpoints](https://status.cloud.google.com/security/incidents/K6VB74JiPnRu1gp2hYyN). 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 exceeded
* `502` — Bad gateway
* `504` — 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](https://docs.bindplane.com/configuration/bindplane-otel-collector/updating-the-bindplane-distro-for-opentelemetry-collector).

#### Option 1: Bindplane UI

1. Navigate to the **Collectors** page
2. To upgrade a single collector, click the **upgrade link** next to the collector's version number
3. 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:

```bash
bindplane get collectors
```

Then update each collector:

```bash
bindplane update collector {ID}
```

#### 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.

```bash
sudo sh -c "$(curl -fsSlL 'https://github.com/observIQ/bindplane-agent/releases/latest/download/install_unix.sh')" install_unix.sh
```

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:

```bash
bindplane get collectors
```

Verify the version shows `v1.94.2` or later for all affected collectors.

### References

* [Google Cloud Incident](https://status.cloud.google.com/security/incidents/K6VB74JiPnRu1gp2hYyN)
* [Updating the Bindplane Distro for OpenTelemetry Collector](https://docs.bindplane.com/configuration/bindplane-otel-collector/updating-the-bindplane-distro-for-opentelemetry-collector)
* [Collector Release v1.94.2](https://github.com/observIQ/bindplane-otel-collector/releases/tag/v1.94.2)
* [Fix: Retry on 429 responses](https://github.com/observIQ/bindplane-otel-collector/pull/3170)
* [Fix: Retry on 502 & 504 responses](https://github.com/observIQ/bindplane-otel-collector/pull/3176)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.bindplane.com/how-to-guides/partner-integrations/google-secops/resolve-intermittent-ingestion-drop-for-google-secops-https-endpoints.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.