[OnWeek][ObsUX] Add fields to hosts in synthtrace to improve data generation

[MiriamAparicio]

Summary

After improving the synthtrace data creation for containers we were able to add more specific tests for container view, the aim of this spacetime is to add some improvements to hosts so we can in the future use synthtrace for testing

What was done

First I thought that adding event.dataset was needed to get the metadata, or make the request work, as I did for containers, but in containers was needed not because of the metadata query itself but the integration check to know if we need to display k8s or docker metrics.
I simplified the scenarios and data generation in the tests, adding the metadata fields we need in the synthtrace clients for host and docker and k8s containers, the values of the metadata fields doesn't need to change for different scenarios, so it's ok to have them set in the client.

[elasticmachine]

Pinging @elastic/obs-ux-infra_services-team (Team:obs-ux-infra_services)

[obltmachine]

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

• /oblt-deploy : Deploy a Kibana instance using the Observability test environments.
• run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: a493e2a
• Kibana Serverless Image: docker.elastic.co/kibana-ci/kibana-serverless:pr-187147-a493e2a5a503
• Observability Deployment

Metrics [docs]

✅ unchanged

History

• 💛 Build #218432 was flaky 22a31f7

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

[jennypavlova]

LGTM 💯 (code review only)
Do we test with the existing containers scenario or do we need another one?

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 83b48b2
• Kibana Serverless Image: docker.elastic.co/kibana-ci/kibana-serverless:pr-187147-83b48b215b20
• Observability Deployment

Metrics [docs]

✅ unchanged

History

[MiriamAparicio]

Do we test with the existing containers scenario or do we need another one?

@jennypavlova not sure what do you mean here, the existing scenarios for containers and hosts should be enough for testing that the metadata fields are displayed on the summaries, I did not add all the possible metadata fields that can be shown on the metadata tab, as I don't think it's necessary for testing