search

elastic / kibana

Your window into the Elastic Stack
https://www.elastic.co/products/kibana
Other
19.69k stars 8.24k forks source link

Use more self-explanatory wording during deployment / project creation on Elastic Cloud - Hosted (ESS) or Serverless #198881

Open kunisen opened 3 weeks ago

kunisen commented 3 weeks ago

Description

During deployment / project creation on Elastic Cloud - Hosted (ESS) or Serverless, Kibana shows below when underlying ES is not ready. Image

Elastic did not load properly
Please reload this page. If the issue persists, check the browser console and server logs.

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

elasticmachine commented 3 weeks ago

Pinging @elastic/kibana-core (Team:Core)

rudolf commented 3 weeks ago

@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 https://github.com/elastic/kibana/pull/186609

petrklapka commented 2 weeks ago

@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."

Dariaus999 commented 2 weeks ago

@petrklapka -

These are very simple steps to reproduce.

  1. log in to https://cloud.elastic.co/d
  2. create a new ESS deployment (not serverless)
  3. choose any nodes I tested with AWS/GCP/Azure for minimum and click okay to start the process.
  4. Once it is finished process, it shows completed to urge click okay
  5. then change the window with the Elastic logo in the middle to wait for the new deployment to come up
  6. After all, I see the timeout in AWS and Azure seeing time out, but not GCP for the same issue.

Image

tsullivan commented 1 week ago

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?

petrklapka commented 6 days ago

@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.