[Stack Monitoring][Angular removal] Migrate kibana views

[estermv]

Migrate views under views/kibana

• overview [Stack Monitoring] React migration kibana overview #113604
• instances [Stack Monitoring ] Migrate kibana instances page to react #113874
• instance [Stack Monitoring] kibana instance react #113962

[elasticmachine]

Pinging @elastic/logs-metrics-ui (Team:logs-metrics-ui)

[klacabane]

I'll get started with the Overview page following the steps defined here.

[klacabane]

While testing the graphs in the overview page it looks like we have a regression on the zoom-out action which seems to be a no-op atm. Steps to reproduce:

• Pick a period on a graph to trigger the zoom-in action. Action behaves properly with the timepicker being updated to be in-sync with the url query.
• Click 'Zoom out' on a graph. Url query is updated to reflect to n-1 timeframe but the timepicker doesn't change, graph is not updated as well. After ~10sec the graph is updated to be in-sync with the active timeframe, probably a background interval that causes a repaint ?

Same behavior on firefox and chrome

[jasonrhodes]

@klacabane do you mean there is a regression in the existing code or only in the migrated code? And on which page do you see this?

[klacabane]

Happens in the migrated code, behavior is as expected in the Angular code. Happens on both Elasticsearch overview and Kibana overview, but I suppose any migrated page that use the similar components is impacted.

Issue is already tracked in #112063 so I'll move on :)

[matschaffer]

@klacabane good you found that one :) yeah right now any zoom/brush/zoomout can trigger this. I think it's okay to move on and we can address it later. Maybe even after angular removal.

[klacabane]

Will do the Instances page next. Planning to use the docker setup to have n kibana instances in order to enable and test pagination.

[klacabane]

Instances page merged, following up with #113873 before moving to the Instance page.