[BUG] - Nodes/Shards/Indices tabs showing no (or reduced) data

[anthony-malkoun]

READ BEFORE OPENING AN ISSUE
Before you submit an issue please try to reset elasticvue and see if you can reproduce the problem.
To reset please click Disconnect and reset in the footer, this will reset all your saved filters and you have to reconnect to your cluster.
Proceed and open an issue if your problem persists.

Description
We have an Opensearch cluster and I'm connecting to it using aws-es-proxy which manages login and I'm logged in with cluster admin rights, so I can connect to http://localhost:9200/ and get the Opensearch JSON message. The home page shows statistics, e.g. nodes/shards/indices but clicking on the tabs doesn't show any data. The "Search" tab shows data from every index and the index selector is empty. This happens both on the extension and standalone app.

Steps To Reproduce
List the steps to reproduce your problem:

1. Open elasticvue
2. Home page shows valid stats. The numbers are correct, e.g. number of indices is the correct number.
3. Click on one of the tabs, no data shows.
4. Click on search tab, results from all indices are shown, selector for index is empty

Screenshots
If applicable, add screenshots to help explain your problem.

• Home page with correct data

• Indices tab with no data

Environment (please include the following information):

• Elasticsearch version: Opensearch 2.19.0
• Operating system: Windows
• Browser + version: Edge Version 140.0.3485.94 (Official build) (64-bit)
• Elasticvue version: Elasticvue 1.8.0-stable
• How are you running elasticvue? Extension and App

Additional context
Anything else?

[cars10]

Sounds like the _cat APIs are not available - please check if you can access _cat/indices and _cat/nodes on your cluster

FYI: elasticvue also supports aws signing so you should be able to directly connect to your cluster in aws without the proxy

[anthony-malkoun]

Thank you for the feedback. I don't have the stack up at the moment, but I'm pretty sure at least _cat/indices worked via, say the REST tab in Elasticvue.

I think for Elasticvue connecting directly, the support of IAM Roles might be a blocker? I still get 403 if I use the AWS IAM option when I add an elasticsearch cluster.

[anthony-malkoun]

http://localhost:9200/_cat/indices and http://localhost:9200/_cat/nodes both work, including directly via the browser and also via the REST tab in Elasticvue.

[cars10]

Dear @anthony-malkoun , thanks for the update. I just noticed that you are using opensearch. While it does work in most cases, there are differences to elasticsearch. I personally do not use opensearch and don't have any experience with it so i am not sure if i am able to fix this, elasticvue officially only supports opensearch. I tried it with a barebone opensearch setup with 2 nodes (version 2.19) and have lots of issues in the browser version, but the desktop version of elasticvue works fine as far as i can tell.

[anthony-malkoun]

Hi @cars10, thanks for the update. Feel free to close as won't fix. I thought it might be issues with Opensearch.