-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Synthetics] Private location better error handling #152695
Conversation
a5252ba
to
6ccf699
Compare
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.
An internal server error happens during the editing flow
<img width="798" alt="Screen Shot 2023-05-02 at 9 08 28 PM" src="https://user-images.githubusercontent.com/11356435/235816127-92f79d9e-e77c-4329-a7e7-4bf0bca79652.png">
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.
After removing the routeContext
issue with a commit I pushed, I'm seeing this issue on the edit monitor flow.
proc [kibana] [2023-05-02T21:32:15.814-04:00][ERROR][http] ResponseError: [1:360] [bool] failed to parse field [filter]: x_content_parse_exception
proc [kibana] Caused by:
proc [kibana] x_content_parse_exception: [1:360] [bool] failed to parse field [should]
proc [kibana] Root causes:
proc [kibana] parsing_exception: [terms] query does not support [namespaces]
proc [kibana] at KibanaTransport.request (/Users/dominiqueclarke/dev/kibana/node_modules/@elastic/transport/src/Transport.ts:535:17)
proc [kibana] at runMicrotasks (<anonymous>)
proc [kibana] at processTicksAndRejections (node:internal/process/task_queues:96:5)
16e2e90
to
e5da186
Compare
Pinging @elastic/fleet (Team:Fleet) |
Pinging @elastic/uptime (Team:uptime) |
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.
An error originating from public locations, for example addConfigs
in the synthetics service, does not delete the integration policy, which was already created since public and private locations happen in parallel.
This creates an orphaned integration policy.
We should ensure that the integration policy is deleted if we encounter issues in public locations.
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.
Synthetics LGTM. The previous issue has been resolved.
export type DecryptedSyntheticsMonitorSavedObject = SimpleSavedObject<SyntheticsMonitor> & { | ||
updated_at: string; | ||
}; | ||
|
||
export interface SyntheticsServiceAllowed { |
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.
Are these not in use?
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.
yeah they aren't.
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.
Fleet changes LGTM, it seems synthetics are the only using those bulk methods so it's probably okay to change those method behaviours
💛 Build succeeded, but was flaky
Failed CI StepsTest FailuresMetrics [docs]Async chunks
Unknown metric groupsESLint disabled line counts
References to deprecated APIs
Total ESLint disabled count
History
To update your PR or re-run it, just comment with: |
Co-authored-by: Dominique Clarke <dominique.clarke@elastic.co> (cherry picked from commit 1aba7df)
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
…156807) # Backport This will backport the following commits from `main` to `8.8`: - [[Synthetics] Private location better error handling (#152695)](#152695) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Shahzad","email":"shahzad31comp@gmail.com"},"sourceCommit":{"committedDate":"2023-05-05T09:31:59Z","message":"[Synthetics] Private location better error handling (#152695)\n\nCo-authored-by: Dominique Clarke <dominique.clarke@elastic.co>","sha":"1aba7df3363d25a24b35fd0f716d5f89c76c41b8","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:uptime","release_note:skip","Team:Fleet","v8.8.0","v8.9.0"],"number":152695,"url":"https://github.com/elastic/kibana/pull/152695","mergeCommit":{"message":"[Synthetics] Private location better error handling (#152695)\n\nCo-authored-by: Dominique Clarke <dominique.clarke@elastic.co>","sha":"1aba7df3363d25a24b35fd0f716d5f89c76c41b8"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"8.8","label":"v8.8.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/152695","number":152695,"mergeCommit":{"message":"[Synthetics] Private location better error handling (#152695)\n\nCo-authored-by: Dominique Clarke <dominique.clarke@elastic.co>","sha":"1aba7df3363d25a24b35fd0f716d5f89c76c41b8"}}]}] BACKPORT--> Co-authored-by: Shahzad <shahzad31comp@gmail.com> Co-authored-by: Dominique Clarke <dominique.clarke@elastic.co>
Fixes #147728
Private location better error handling, error handling has been done to make sure, if somehow creating package policy fails, it properly reflects in the UI and also for project monitors
Testing Scope
Since these PR touches lot of public/private location code paths, following test should be performed
UI Monitors
Project monitors