[Metrics UI][Test Scenario] Metrics Explorer – Basic Functionality

[estermv]

Summary

This set of test cases is a smoke test for Metrics Explorer

Setup

• Create a test cluster in cloud
• Download the nightly build candidate for Metricbeat
• Setup Metricbeat locally on your laptop to send data to your test cluster
• Open Kibana
• Create an index pattern for metricbeat-*
• Navigate to the Metrics UI and click on Metrics Explorer

Test Cases

Each of the following test cases assumes that you've navigated to the Metrics UI and clicked on Metrics Explorer for the first time. Since Metrics Explorer has a feature that saves where you left off, you might need to load the "Default View" to reset everything back to the defaults.

Basic Functionality

• Ensure Metrics Explorer opens with three metrics system.cpu.user.pct, kubernetes.pod.usage.node.pct, and docker.cpu.total.pct
• Since you're only shipping data for one of the metrics, ensure there is a series for system.cpu.user.pct in the chart
• Change "graph per" to host.name, ensure that there is a chart for your laptop's host name.
• Ensure that below "Current View" it says "Default view". Make sure you have no state in the URL
  for example: (https://localhost:5601/ubx/app/metrics/explorer).
• Ensure time picker set to Last 1 hour
• Click on the metric bar and delete each metric with the keyboard using the backspace button. Ensure message in chart area says "Missing Metric"
• Now that the metric bar is empty, type system.network.in. and then use the down arrow to select system.network.in.bytes. Hit the escape key to close the auto-complete
• Change the aggregation to Rate
• Set "graph per" to host.name and system.network.name, ensure there is a chart per host, per network interface.
• Click on the Elastic logo at the top of the page, you will end up on the home page. Now navigate back to Metrics Explorer and ensure the settings are reloaded.
• If you have more the 9 network interfaces, there should be a "Load More Charts" button at the bottom of the page, click it and ensure it loads 9 more unique charts.
• Click on "Action" drop down next to a network interface that has data, choose "Add Filter". Ensure the UI filters down to a single chart.
• Click on the "Action" drop down next to a chart, choose "Open in visualize". Ensure the charts render in TSVB similar to the charts in the Metrics Explorer. (See [Metrics UI] Open in visualize no longer works in Metrics Explorer #72529)

Customize Charts

• Click on "Customize" and change chart type to "Area", ensure the charts are now area charts
• Click on "Customize" change "Stack series" to "Stack", ensure series are now stacked
• Click on "Customize" change chart type to "Bar", ensure series are now bars and stacked
• Click on "Customize" toggle "Stack series" to NOT "Stack", ensure series are NOT stacked
• Click on "Customize" and change chart type back to "Line", change "Y Axis Domain" to "Automatic", ensure charts with data start the Y axis at the data bounds instead of zero.

[elasticmachine]

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

[estermv]

Some behavior can be tested by unit tests. For other use cases, there is a ticket to add functional tests #105782