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

Monitoring: Error 404 Not Found: The cluster [undefined] was not found within the selected time range #19113

Closed
fe7ch opened this issue May 16, 2018 · 1 comment
Labels
Team:Monitoring Stack Monitoring team

Comments

@fe7ch
Copy link

fe7ch commented May 16, 2018

Kibana version:
6.2.3

Elasticsearch version:
6.2.3

Server OS version:
Linux elk2 4.4.0-116-lowlatency #140-Ubuntu SMP PREEMPT Mon Feb 12 22:41:05 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Browser version:
Google Chrome: Version 66.0.3359.139 (Official Build) (64-bit)

Browser OS version:
Windows 7 Enterprise (6.1.7601)

Original install method (e.g. download page, yum, from source, etc.):
apt repository

Describe the bug:
While trying to navigate to "Overview" of the elasticsearch's monitoring, I get a blank page with the error message mentioned in the bug's title.

Steps to reproduce:

  1. Open Monitoring -> Elasticsearch -> Indicies
  2. I've time values set as following: refresh interval: 10s, clock: last 1 hour
  3. Click open in new tab on "Overview"
  4. A new tab opens with the error message "Monitoring: Error 404 Not Found: The cluster [undefined] was not found within the selected time range."

The error appears only if you open overview in new tab/window. It won't happen if you open Overview in the same tab where you view Indicies.

Expected behavior:

Screenshots (if relevant):

Errors in browser console (if relevant):

Provide logs and/or server output (if relevant):
{"type":"response","@timestamp":"2018-05-16T10:21:12Z","tags":[],"pid":30127,"method":"post","statusCode":404,"req":{"url":"/api/monitoring/v1/clusters/undefined/elasticsearch","method":"post","headers":{"connection":"upgrade","host":"my_host","content-length":"290","accept":"application/json, text/plain, /","origin":"https://my_host","kbn-version":"6.2.3","user-agent":"Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.139 Safari/537.36","content-type":"application/json;charset=UTF-8","referer":"https://my_host/app/monitoring","accept-encoding":"gzip, deflate, br","accept-language":"ru-RU,ru;q=0.9,en-US;q=0.8,en;q=0.7"},"remoteAddress":"127.0.0.1","userAgent":"127.0.0.1","referer":"https://my_host/app/monitoring"},"res":{"statusCode":404,"responseTime":33,"contentLength":9},"message":"POST /api/monitoring/v1/clusters/undefined/elasticsearch 404 33ms - 9.0B"}

Any additional context:

@jbudz jbudz added triage_needed Team:Monitoring Stack Monitoring team labels May 16, 2018
@tsullivan
Copy link
Member

api/monitoring/v1/clusters/undefined/elasticsearch

The problem is, undefined is not a valid Cluster UUID. The browser got into a state where it doesn't have the cluster_uuid in the globalState.

The globalState is passed around from page to page through links, as it is part of the URL. For example: ?_g=(cluster_uuid:H6N-buS3TU-UpsuETW3VXA)

However, the carryover doesn't work if you try to open a link in a new tab, or do something to navigate to a deep view without a cluster_uuid.

The workaround is to reset the invalid browser state by clicking the Monitoring icon in the Kibana sidebar and starting again from the top. If a little "toaster" window pops up at the bottom with a "Retry" button, clicking Retry will do the same thing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:Monitoring Stack Monitoring team
Projects
None yet
Development

No branches or pull requests

4 participants