Beats instance page

[matschaffer]

Summary

Got the basics going so far

Part of #111757

Still need to work out:

• Setup mode: just shows n/a right now
• Pagination test: if I add what I found in ElasticsearchNodesPage I get a server side rejection. Need to see how that part is working

Checklist

Delete any items that are not applicable to this PR.

• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios
• Any UI touched in this PR is usable by keyboard only (learn more about keyboard accessibility)
• Any UI touched in this PR does not create any new axe failures (run axe in browser: FF, Chrome)
• If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list
• This renders correctly on smaller devices using a responsive layout. (You can test this in your browser)
• This was checked for cross-browser compatibility

Risk Matrix

Delete this section if it is not applicable to this PR.

Before closing this PR, invite QA, stakeholders, and other developers to identify risks that should be tested prior to the change/feature release.

When forming the risk matrix, consider some of the following examples and how they may potentially impact the change:

Risk	Probability	Severity	Mitigation/Notes
Multiple Spaces—unexpected behavior in non-default Kibana Space.	Low	High	Integration tests will verify that all features are still supported in non-default Kibana Space and when user switches between spaces.
Multiple nodes—Elasticsearch polling might have race conditions when multiple Kibana nodes are polling for the same tasks.	High	Low	Tasks are idempotent, so executing them multiple times will not result in logical error, but will degrade performance. To test for this case we add plenty of unit tests around this logic and document manual testing procedure.
Code should gracefully handle cases when feature X or plugin Y are disabled.	Medium	High	Unit tests will verify that any feature flag or plugin combination still results in our service operational.
See more potential risk examples

For maintainers

• This was checked for breaking API changes and was labeled appropriately

[elasticmachine]

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

[matschaffer]

Looks like ES nodes also has broken setup mode behavior for react/master now, so could be we could merge with that not working correctly and fix next week.

[matschaffer]

Looks like pagination doesn't work at all yet. So will have to figure out how to make that work.

[matschaffer]

Just noting that to test this I ended up using this to generate a docker compose, metricbeat, and docker compose up snippet:

// spit out 29 entries for docker-compose.yaml
for (let i = 2; i <= 30; i++) {
  console.log(`
  mb${i.toString().padStart(2, '0')}:
    <<: *extrabeat
  `);
}

// spit out 30 entries to add to metricbeat.yml
let list = [];
for (let i = 1; i <= 30; i++) {
  list.push(`http://mb${i.toString().padStart(2, '0')}:5066`);
}
console.log(JSON.stringify(list));

// spit out a docker compose for all 30 metricbeats (can probably just use `docker compose up -d`)
let upCmd = 'docker compose up -d ';
for (let i = 1; i <= 30; i++) {
  upCmd += `mb${i.toString().padStart(2, '0')} `;
}
console.log(upCmd);

With this yaml definition in docker-compose.yml

  mb01: &extrabeat
    image: docker.elastic.co/beats/metricbeat:${ELASTIC_VERSION}
    user: root
    environment:
      ELASTICSEARCH_HOSTS: https://node01:9200
      ELASTICSEARCH_USERNAME: elastic
      ELASTICSEARCH_PASSWORD: $ELASTIC_PASSWORD
    volumes:
      - ./metricbeat-extra.yml:/usr/share/metricbeat/metricbeat.yml
    networks:
      - es-network

And this metricbeat-extra.yml

metricbeat.config.modules:
  path: ${path.config}/modules.d/*.yml
  reload.enabled: false

output.elasticsearch:
  hosts: '${ELASTICSEARCH_HOSTS:elasticsearch:9200}'
  username: '${ELASTICSEARCH_USERNAME:}'
  password: '${ELASTICSEARCH_PASSWORD:}'
  protocol: 'https'
  ssl.verification_mode: 'none'

http.enabled: true

metricbeat.modules:
  - module: system
    period: 10s
    enabled: true

and add those to the main metricbeat.yml

- module: beat
  xpack.enabled: true
  period: 10s
  hosts: ["http://127.0.0.1:5066", "http://filebeat:5067", "http://apm-server:5068", "http://heartbeat:5069", "http://mb01:5066","http://mb02:5066","http://mb03:5066","http://mb04:5066","http://mb05:5066"... (the rest of what's generated)]

This way I could get 30 "extra" metricbeat instances that do almost nothing, but show up in the monitoring UI.

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: aa5e691
• Storybooks Preview

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
monitoring	605	607	+2

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
monitoring	946.6KB	951.2KB	+4.6KB

History

• 💚 Build #155627 succeeded aa5e691
• 💔 Build #155623 failed 8fc11b5

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @matschaffer

[phillipb]

LGTM!

[matschaffer]

Will handle pagination & setup mode in follow up PRs.

[kibanamachine]

💚 Backport successful

Status	Branch	Result
✅	7.x

This backport PR will be merged automatically after passing CI.