-
Notifications
You must be signed in to change notification settings - Fork 8.4k
chore(slo): Refactor create, update and reset SLO operations #221206
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
base: main
Are you sure you want to change the base?
Conversation
Pinging @elastic/obs-ux-management-team (Team:obs-ux-management) |
rollbackOperations.push(() => this.transformManager.stop(rollupTransformId)); | ||
rollbackOperations.push(() => this.summaryTransformManager.stop(summaryTransformId)); | ||
|
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.
stopping the transform is not necessary anymore since uninstalling will proceed regardless of the transform state
@kdelemme can you please post the APM instrumented view for these routes for before/after comparisons. |
I'll try to find the time later this week. it will be very similar to the similar changes that happened in the create service awhile back |
… of original SLO resources
58aa6c8
to
92fc92d
Compare
⏳ Build in-progress, with failures
Failed CI StepsTest Failures
History
|
Summary
resolves #221205
This PR does 3 things:
Comparison