-
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
Use more self-explanatory wording during deployment / project creation on Elastic Cloud - Hosted (ESS) or Serverless #198881
Comments
Pinging @elastic/kibana-core (Team:Core) |
@elastic/appex-sharedux Tagging you as even though we own this code, it feels like the concern here is more about UX and related to your recent work #186609 |
@kunisen @rudolf @alisonelizabeth - I'm not sure how this state was even reachable. I've never seen Cloud UI give access to an instance that was not ready. @kunisen - can you give steps to reproduce? Yes, the messaging isn't great and we are already working on making that better, but this should "never happen." |
These are very simple steps to reproduce.
|
It sounds like this issue could happen if the user clicks the "Okay" button really fast. @elastic/cloud-ui is this issue under your domain? |
@alisonelizabeth - Is this something that the Cloud UI crew would cover or is this more of a control plane issue? We could change the wording of this message, but ideally this just wouldn't ever happen and not be reproducible. |
Description
During deployment / project creation on Elastic Cloud - Hosted (ESS) or Serverless, Kibana shows below when underlying ES is not ready.
However, since Elastic hosts the VMs, users should just be a bit more patient and wait for a few minutes.
It would be great if we could have a more self-explanatory message like - i.e. be patient, instances are soon to be launched, your env will be ready soon, etc.
Also since during other situation, i.e. ES can't be ready due to whatever reason, it shows the same message, then it might be better to differentiate the situation between the creation and later.
@Dariaus999
The text was updated successfully, but these errors were encountered: