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

[8.16] [Infra] Change order of the errors shown on Infra pages (#200531) #200553

Merged
merged 1 commit into from
Nov 18, 2024

Conversation

kibanamachine
Copy link
Contributor

Backport

This will backport the following commits from main to 8.16:

Questions ?

Please refer to the Backport tool documentation

Closes elastic#200190

## Summary

This PR fixes the issue with the errors shown on the metrics explorer
page - when the metrics indices can't be fetched we should show the
error returned and if there is no fetch error and a remote cluster
configured but no connection is possible we should show the remote
cluster error:

- Example with 504 error

![image](https://github.com/user-attachments/assets/65cd8226-8c81-4c64-b043-c9db5a93d3e0)

- Example with remote cluster error

![image](https://github.com/user-attachments/assets/e024a3f8-76e0-4ad7-8aa6-e35ad5c1112a)

## Testing
Couldn't find a way to reproduce this so I "faked" the API response to
be an error and checked several cases
- API returns an error, we should show the error:

https://github.com/user-attachments/assets/c1086b22-1ff5-4333-97a5-b3d1dca16afe

- API doesn't return an error but the remote cluster connection wasn't
possible, we should show the remote cluster error:

https://github.com/user-attachments/assets/151b3ae4-5ca1-4d54-bd58-2729db202cdb

- If no remote cluster is used/or a remote cluster is connected and the
API response is not returning an error the page should load correctly:

https://github.com/user-attachments/assets/f9ef1066-3dfd-4957-8b46-878bf58d2f1c
(cherry picked from commit 46d4c84)
@kibanamachine kibanamachine requested a review from a team as a code owner November 18, 2024 12:35
@kibanamachine kibanamachine enabled auto-merge (squash) November 18, 2024 12:35
@botelastic botelastic bot added the ci:project-deploy-observability Create an Observability project label Nov 18, 2024
Copy link
Contributor

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

  • /oblt-deploy : Deploy a Kibana instance using the Observability test environments.
  • run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

@kibanamachine kibanamachine merged commit 922afd9 into elastic:8.16 Nov 18, 2024
34 checks passed
@elasticmachine
Copy link
Contributor

💛 Build succeeded, but was flaky

Failed CI Steps

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id before after diff
infra 1.7MB 1.7MB +2.2KB

cc @jennypavlova

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport ci:project-deploy-observability Create an Observability project
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants