You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I'm using the OpenSearch Dashboards Dev Tools Console to make requests to an OpenSearch cluster. Some of the requests work as expected, but for a number of requests, the console shows "Request failed to get to the server (status code: 200)" as the result. This happens for a number of different request, but the simplest I've discovered it with are in this form: GET <index_alias>/_doc/<doc_id>. Not all docs result in this error, but some do. So the bug seems to only present with certain data. I've also noticed the issue with some GET <index_alias>/_search requests.
These very same requests work fine if I make the HTTP request directly to the OpenSearch cluster with a tool like Postman.
I've also noticed in my browser dev tools that the request to https://<cluster_host>/_dashboards/api/console/proxy?path=<my request> succeeds and includes my document in the response, but this bug prevents it from actually being displayed on the page.
I first noticed this issue after an upgrade from OpenSearch 2.5 to 2.11.
I recognize some more info about the actual contents of the documents could be useful to you in debugging, but I'm somewhat limited in what I can share due to proprietary information being stored in the cluster.
To Reproduce
Steps to reproduce the behavior:
Go to https://<cluster_host>/_dashboards/app/dev_tools#/console
Make a request like GET <index_alias>/_doc/<doc_id> in the console (only certain docs cause the issue)
Observe in the pane on the right side of the page the error message: "Request failed to get to the server (status code: 200)"
Expected behavior
I expect to see the body on the response in the pane on the right side of the page
Describe the bug
I'm using the OpenSearch Dashboards Dev Tools Console to make requests to an OpenSearch cluster. Some of the requests work as expected, but for a number of requests, the console shows "Request failed to get to the server (status code: 200)" as the result. This happens for a number of different request, but the simplest I've discovered it with are in this form:
GET <index_alias>/_doc/<doc_id>
. Not all docs result in this error, but some do. So the bug seems to only present with certain data. I've also noticed the issue with someGET <index_alias>/_search
requests.These very same requests work fine if I make the HTTP request directly to the OpenSearch cluster with a tool like Postman.
I've also noticed in my browser dev tools that the request to
https://<cluster_host>/_dashboards/api/console/proxy?path=<my request>
succeeds and includes my document in the response, but this bug prevents it from actually being displayed on the page.I first noticed this issue after an upgrade from OpenSearch 2.5 to 2.11.
I recognize some more info about the actual contents of the documents could be useful to you in debugging, but I'm somewhat limited in what I can share due to proprietary information being stored in the cluster.
To Reproduce
Steps to reproduce the behavior:
https://<cluster_host>/_dashboards/app/dev_tools#/console
GET <index_alias>/_doc/<doc_id>
in the console (only certain docs cause the issue)Expected behavior
I expect to see the body on the response in the pane on the right side of the page
OpenSearch Version
OpenSearch 2.11
Dashboards Version
v 2.11.0
Plugins
The result of
GET _cat/plugins
is:Screenshots
If applicable, add screenshots to help explain your problem.
Host/Environment (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: