[Infra UI] Add AWS metrics to node detail page

[skh]

Summary

Implements #39281 and #39282.

This adds the following AWS metrics to the node detail page:

• Overview
• CPU Utilization
• Network Traffic
• Network Packets
• Disk I/O Operations
• Disk I/O Bytes.

Because of #42687 we might have to disable Network Traffic and both Disk I/O sections for now. They are still contained in this PR, they can be commented out quickly if necessary.

To test this, use an ES instance with metricbeat data for at least one AWS instance as described in https://github.com/elastic/kibana/blob/master/x-pack/legacy/plugins/infra/docs/test_setups/infra_metricbeat_aws.md . The Observability 8.x.x shared cluster has this data. (Please note that the instance that reports to this cluster doesn't have any storage attached, so the Disk I/O metrics are zero overall.)

View the node detail page for an AWS instance and verify that AWS metrics are shown:

In GraphiQL, you can view the data that is returned for each model with a query like this:

{
  source(id: "default") {
    metrics(nodeIds: {nodeId: "ip-172-31-47-9.us-east-2.compute.internal", cloudId: "i-011454f72559c510b"},
      nodeType:host, timerange: {from: 1564758416480, interval: ">=1m", to: 1564762016480},
      metrics: [awsNetworkPackets]) {
      id
      series {
        id
        data {
          value
          timestamp
        }
      }
    }
  }
}

The available metrics that have been added are

• awsOverview
• awsCpuUtilization
• awsNetworkBytes
• awsNetworkPackets
• awsDiskioBytes
• awsDiskioOps

[elasticmachine]

💔 Build Failed

• continuous-integration/kibana-ci/pull-request

[elasticmachine]

💔 Build Failed

• continuous-integration/kibana-ci/pull-request

[elasticmachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request

[elasticmachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request

[elasticmachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request

[elasticmachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request

[elasticmachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request

[elasticmachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request

[elasticmachine]

Pinging @elastic/infra-logs-ui

[elasticmachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request

[simianhacker]

requires at the top level can be removed, only the section requires arrays are read (see comment above).

[simianhacker]

@sorantis @kaiyan-sheng Is the network packets value a rate? I know the values from Metricbeat (system.network.out.packets) are monotonically increasing numbers which we usually end up display as a per second value. The only reason I ask is because there isn't a suffix label on the data and I'm not sure what label would be appropriate? Also if it's a rate then we should probably divide by 300 as well.

[simianhacker]

@sorantis @kaiyan-sheng Looks like I answered my own question: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/viewing_metrics_with_cloudwatch.html

Looks like it's just the number of packets transferred.

[simianhacker]

Good Job! Everything looks good. Just remove the requires key from the AWS layout and change the layout generator's function signature as noted. Once that's done, everything should be good to go.

[elasticmachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request

[skh]

@simianhacker Thanks for the review! This is ready for another look.

[elasticmachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request

[skh]

@simianhacker this is ready for another look.

[simianhacker]

Good work!

.____     ________________________   
|    |   /  _____/\__    ___/     \  
|    |  /   \  ___  |    | /  \ /  \ 
|    |__\    \_\  \ |    |/    Y    \
|_______ \______  / |____|\____|__  /
        \/      \/                \/