Skip to content
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

Open
kunisen opened this issue Nov 5, 2024 · 6 comments
Labels
Feature:Logs UI Logs UI feature feedback_needed Team:Cloud Team:SharedUX Team label for AppEx-SharedUX (formerly Global Experience)

Comments

@kunisen
Copy link
Contributor

kunisen commented Nov 5, 2024

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

@kunisen kunisen added the Feature:Logs UI Logs UI feature label Nov 5, 2024
@botelastic botelastic bot added the needs-team Issues missing a team label label Nov 5, 2024
@kunisen kunisen added the Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc label Nov 5, 2024
@elasticmachine
Copy link
Contributor

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

@botelastic botelastic bot removed the needs-team Issues missing a team label label Nov 5, 2024
@rudolf
Copy link
Contributor

rudolf commented Nov 5, 2024

@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

@rudolf rudolf added the Team:SharedUX Team label for AppEx-SharedUX (formerly Global Experience) label Nov 5, 2024
@petrklapka
Copy link
Member

@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
Copy link

@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
Copy link
Member

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
Copy link
Member

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

@rudolf rudolf removed the Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc label Nov 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Logs UI Logs UI feature feedback_needed Team:Cloud Team:SharedUX Team label for AppEx-SharedUX (formerly Global Experience)
Projects
None yet
Development

No branches or pull requests

6 participants