[Stack Monitoring] [Test Scenario] Metricbeat monitoring

[phillipb]

Testing

• Ensure that the Stack Monitoring UI works as expected with both metricbeat-* data and .monitoring-* data ([Monitoring] Handle no mappings found for sort and collapse fields #77099). This involves using either legacy or Metricbeat-based collection in addition to using Metricbeat for non-stack monitoring data. The easiest way to do this is to setup monitoring via Metricbeat and ensure the system module is enabled.

[elasticmachine]

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

[neptunian]

@igoristic Can you provide some steps I can take to ensure that this condition is met? I have both these indices but not sure what actions I should take.

[igoristic]

Ensure that the Stack Monitoring UI works

Is a bit vague, but I think we're just making sure the SM UI still functions (as you navigate through it, eg: overview, listings, details, etc...) without throwing any errors in the frontend (chrome dev tools console) and on the backend (Kibana/ES terminal console).

The only requirement seems to be having both metricbeat* (with systems module enabled) and .monitoring* indices

[elasticmachine]

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