-
Notifications
You must be signed in to change notification settings - Fork 8.5k
[Response Ops][Reporting] Fixing error in calculating delay value between retries #245431
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
+63
−13
Conversation
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
Contributor
|
Pinging @elastic/response-ops (Team:ResponseOps) |
darnautov
approved these changes
Dec 5, 2025
Contributor
darnautov
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Contributor
💔 Build Failed
Failed CI StepsMetrics [docs]
History
cc @ymao1 |
Contributor
|
Starting backport for target branches: 9.2 |
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Dec 8, 2025
…ween retries (elastic#245431) ## Summary It was pointed out that there's an error in calculating the delay between retries for scheduled reporting tasks. (cherry picked from commit 63515d4)
Contributor
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
kibanamachine
added a commit
that referenced
this pull request
Dec 8, 2025
…ue between retries (#245431) (#245543) # Backport This will backport the following commits from `main` to `9.2`: - [[Response Ops][Reporting] Fixing error in calculating delay value between retries (#245431)](#245431) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Ying Mao","email":"[email protected]"},"sourceCommit":{"committedDate":"2025-12-08T15:28:03Z","message":"[Response Ops][Reporting] Fixing error in calculating delay value between retries (#245431)\n\n## Summary\n\nIt was pointed out that there's an error in calculating the delay\nbetween retries for scheduled reporting tasks.","sha":"63515d4420abe6f70465ec20ef3ecde9ba47876a","branchLabelMapping":{"^v9.3.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","Feature:Reporting:Framework","backport:version","v9.3.0","v9.2.3"],"title":"[Response Ops][Reporting] Fixing error in calculating delay value between retries","number":245431,"url":"https://github.com/elastic/kibana/pull/245431","mergeCommit":{"message":"[Response Ops][Reporting] Fixing error in calculating delay value between retries (#245431)\n\n## Summary\n\nIt was pointed out that there's an error in calculating the delay\nbetween retries for scheduled reporting tasks.","sha":"63515d4420abe6f70465ec20ef3ecde9ba47876a"}},"sourceBranch":"main","suggestedTargetBranches":["9.2"],"targetPullRequestStates":[{"branch":"main","label":"v9.3.0","branchLabelMappingKey":"^v9.3.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/245431","number":245431,"mergeCommit":{"message":"[Response Ops][Reporting] Fixing error in calculating delay value between retries (#245431)\n\n## Summary\n\nIt was pointed out that there's an error in calculating the delay\nbetween retries for scheduled reporting tasks.","sha":"63515d4420abe6f70465ec20ef3ecde9ba47876a"}},{"branch":"9.2","label":"v9.2.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Ying Mao <[email protected]>
mbondyra
added a commit
to mbondyra/kibana
that referenced
this pull request
Dec 8, 2025
* commit '6647f813c9fa03ac0378e3d4756246e8dc4b4c76': (33 commits) [Detection Engine] Extracts Rules/Alerts/Exceptions permission to new Rules feature privileges (elastic#239634) [Agent Builder] Add Intro Tour (elastic#245551) Add datastream lifecycle support to indices metadata (elastic#245548) [Serverless] Update preconfigured connectors (elastic#245445) [Metrics][Discover] Discover to prefer line chars for time series data (elastic#244595) Update dependency @elastic/ebt to ^1.4.1 (main) (elastic#241629) [One Workflow] fix: request bodies with oneof schemas (`kibana.SetAlertsStatus`, etc) (elastic#245344) Update dependency ai to v5 (elastic#244675) Fix Discover trace waterfall behavior with duplicate spans (elastic#244984) [FSH] Migrated fs usage to kbn/fs for sample ingest (elastic#244163) Streamlang: Unskip type coercion test (elastic#245519) [Response Ops][Reporting] Fixing error in calculating delay value between retries (elastic#245431) Add TopNavMenuBeta to navigation plugin (elastic#243578) [scout] support custom servers configuration (elastic#244306) [Fleet] Run agentless background sync without dry run (elastic#245286) Fix Change Password Flaky Test (elastic#245443) Add new gap fill status for rules (elastic#242595) [Kibana Search] Move SLOs higher up in search results (elastic#245518) feat(slo): introduce find SLO instances internal route (elastic#245333) [FSH] Dropped unnecessary `fs` persistence for synthetics project code (elastic#244338) ...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
backport:version
Backport to applied version labels
Feature:Reporting:Framework
Reporting issues pertaining to the overall framework
release_note:skip
Skip the PR/issue when compiling release notes
Team:ResponseOps
Platform ResponseOps team (formerly the Cases and Alerting teams) t//
v9.2.3
v9.3.0
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.
Summary
It was pointed out that there's an error in calculating the delay between retries for scheduled reporting tasks.