[Stack Monitoring] Confirm if all shard states are viewable on ES index overview

[matschaffer]

For good measure when testing #113660 I tried a relocate operation:

POST _cluster/reroute
{
  "commands": [
    {"move": {
      "index": "heartbeat-7.15.0-2021.10.01-000001",
      "shard": 0,
      "from_node": "node02",
      "to_node": "node03"
    }}
  ]
}

Here's a recording, it starts with the shard 0 replica on node02. You'll need to give it a few seconds to go blank then reload to show shard 0 on node03.

The UI did eventually update, but seemed like maybe it missed the relocating stage (just went blank for a cycle then came back as moved).

It's a small index, so could be the relocating stage was too short to see, but the blank load was a little surprising.

No errors in the JS console.

[neptunian]

@matschaffer I commented that is currently also happening in previous versions so not sure we need to make this an angular related issue. Perhaps you can confirm that in your test scenario.

I also created this issue that has some background information #114875.

[matschaffer]

@neptunian 👍🏻 I removed the "de-angularization" status from this issue.

[matschaffer]

Lower priority seems fine here, my guess is that this component has had this bug for a long time.

[elasticmachine]

Pinging @elastic/infra-monitoring-ui (Team:Monitoring)