Sync upstream/integration (a1fa3b8) -> release/5 2026-06-08#422
Open
ffaraone wants to merge 8 commits into
Open
Sync upstream/integration (a1fa3b8) -> release/5 2026-06-08#422ffaraone wants to merge 8 commits into
ffaraone wants to merge 8 commits into
Conversation
…to warning in events-log.
…mance ## Description Region expenses, traffic expenses, available filters performance ## Related issue number OSN-1451 ## Special notes <!-- Please provide additional information if required. --> ## Checklist * [ ] The pull request title is a good summary of the changes * [ ] Unit tests for the changes exist * [ ] New and existing unit tests pass locally
## Description Fixed primary key issue for clickhouse expenses query ## Related issue number OSN-1481 ## Special notes <!-- Please provide additional information if required. --> ## Checklist * [ ] The pull request title is a good summary of the changes * [ ] Unit tests for the changes exist * [ ] New and existing unit tests pass locally
…sibility (hystax#882) ## Description ### Problem When a tenant has multiple cloud accounts (e.g. several Azure subscriptions under the same tenant), their billing imports run in parallel and share the same cloud-provider API rate-limit quota. Under load, this causes cascading HTTP 429 errors that exhaust all retry attempts, leaving imports in a failed state and surfacing an ERROR event in the organisation's event log, even though the failure is transient and automatically retried. ### What changed - Parallel imports per tenant are now bounded. Accounts that share a rate-limit quota (identified by a common parent account) are imported with a configurable maximum concurrency instead of all at once. This significantly reduces the chance of hitting provider rate limits in the first place. The limit is tunable via the /diworker/max_tenant_import_workers configuration key (default: 1). - Rate-limit failures are no longer reported as errors. When an import fails solely because the cloud provider throttled the requests, the event log now records a WARNING ("was throttled by the cloud provider") rather than an ERROR ("failed"). Genuine billing API failures are unchanged and still appear as errors. ## Related issue number - ## Special notes - ## Checklist * [X] The pull request title is a good summary of the changes * [ ] Unit tests for the changes exist * [ ] New and existing unit tests pass locally
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
5 participants
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.
This PR syncs the latest changes from upstream to release branch.