Repository navigation
fix(fetcher): Retry transient Datadog query failures - #83
Merged
Merged
Conversation
Co-Authored-By: Bojan Oro <bojan.oro@sentry.io>
BojanOro
approved these changes
Nov 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The hourly cronjob fails its first pod attempt across regions when the Datadog query API returns a transient error. Most recently, the US run at 2026-11-05 04:00 UTC failed with
HTTP Error 503: Service Unavailablefromurlopen. Kubernetes retries the pod and the retry succeeds. However, each failed attempt still trips the[Kubernetes] Usage Accountant Job failedmonitor.query_datadognow retries 429s, 5xx responses, and network or timeout errors, up to 5 attempts in total. The delay between attempts uses exponential backoff with jitter: 2s, 4s, 8s, 16s, plus up to 100% jitter. Other 4xx errors still fail right away. Each request also has a 30s timeout, so a hung connection can't block the job. That matters because the CronJob usesconcurrencyPolicy: Forbid.Refs PRODENG-3141
via bojan.
--
View Session [Sentry]