-
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
[Elastic Synthetics Integration] Deprecate Legacy Synthetics Integration Add Monitor Flow #137501
Comments
Pinging @elastic/uptime (Team:uptime) |
It might be a bit confusing for existing users of Elastic Synthetics Integration if they were immediately redirected to Uptime or Synthetics, unless we added some type of callout to the top of the page when redirected from the Integration explaining the context. |
Agree @dominiqueclarke we should add some explanation for why we've directed them over. Also, we should carefully consider where we direct them to. Ideally there'd be enough of the Synthetics UI flow available to direct them there (I’m not particularly keen on directing them to Uptime, which is not the desired end flow for this). |
As mentioned here it would be better to direct them to the proper flow in Synthetics UI than the temporary Uptime flow (which will then need to be changed again). |
@paulb-elastic If we redirect to Synthetics UI, it'll be best to wait till 8.6 or GA, whenever we enable the app by default. The reason is that users who do not have the advanced options switch for synthetics on will get an app not found error. |
Thanks @dominiqueclarke, good point Keen to hear from @hbharding and @drewpost too, we'll just need to make sure to track these for changing flows when Synthetics UI is available for everyone. |
…6369) Co-authored-by: florent-leborgne <[email protected]> Fixes #137501
…stic#146369) Co-authored-by: florent-leborgne <[email protected]> Fixes elastic#137501 (cherry picked from commit d136668)
#146369) (#146629) # Backport This will backport the following commits from `main` to `8.6`: - [[Synthetics] Deprecate adding synthetics integrations from fleet (#146369)](#146369) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Shahzad","email":"[email protected]"},"sourceCommit":{"committedDate":"2022-11-29T20:29:26Z","message":"[Synthetics] Deprecate adding synthetics integrations from fleet (#146369)\n\nCo-authored-by: florent-leborgne <[email protected]>\r\nFixes https://github.com/elastic/kibana/issues/137501","sha":"d13666885469c354bdb55c7bb84f127d23b1b83f","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:uptime","release_note:skip","Team:Fleet","v8.6.0","v8.7.0"],"number":146369,"url":"https://github.com/elastic/kibana/pull/146369","mergeCommit":{"message":"[Synthetics] Deprecate adding synthetics integrations from fleet (#146369)\n\nCo-authored-by: florent-leborgne <[email protected]>\r\nFixes https://github.com/elastic/kibana/issues/137501","sha":"d13666885469c354bdb55c7bb84f127d23b1b83f"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/146369","number":146369,"mergeCommit":{"message":"[Synthetics] Deprecate adding synthetics integrations from fleet (#146369)\n\nCo-authored-by: florent-leborgne <[email protected]>\r\nFixes https://github.com/elastic/kibana/issues/137501","sha":"d13666885469c354bdb55c7bb84f127d23b1b83f"}}]}] BACKPORT--> Co-authored-by: Shahzad <[email protected]>
POST FF Testing, tested on cloud, and it works as expected !! |
Disable the ability to Add new Elastic Synthetics integrations outside Uptime/Synthetics monitor management, by redirecting users to Uptime to create monitors and private locations.
This can be done either through a button directing users to Uptime or Synthetics, or by immediately redirecting users to Uptime.
The text was updated successfully, but these errors were encountered: