[eem] top_value metadata aggregation

[klacabane]

Metadata fields currently supports terms aggregation only to retrieve a list of values.
This change updates the metadata schema so one can define different aggregations and also implements a top_value agg that returns a single value according to a sort criteria.

The top_value aggregation is limited to the single top value since transforms do not support multi values for top_metrics

Usage:

{
  ...
  metadata: [
    { source: 'host.name', aggregation: { type: 'top_value', lookbackPeriod: '24h', sort: { '@timestamp': 'desc' } } }
  ]
  ...
}

[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!)

[klacabane]

/ci

[klacabane]

/ci

[klacabane]

@jaredburgettelastic @machadoum I've added a lookbackPeriod parameter to the aggregation - I'll merge now lmk if there's any follow up you'd like to add

[kibana-ci]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: a6e4646
• Storybooks Preview
• Kibana Serverless Image: docker.elastic.co/kibana-ci/kibana-serverless:pr-188243-a6e46468e1db

Failed CI Steps

Metrics [docs]

Public APIs missing comments

Total count of every public API that lacks a comment. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats comments for more detailed information.

id	before	after	diff
@kbn/entities-schema	42	44	+2

Unknown metric groups

API count

id	before	after	diff
@kbn/entities-schema	42	44	+2

History

• 💚 Build #233939 succeeded b4b2d73
• 💔 Build #233919 failed a330f53
• 💚 Build #233908 succeeded 517f221
• 💚 Build #233701 succeeded f643ea6
• 💛 Build #233455 was flaky 809b9be

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

cc @klacabane

[jbudz]

@klacabane can you check if this need to be backported to 8.x?

[kibanamachine]

💔 Some backports could not be created

Status	Branch	Result
❌	8.15	Backport failed because of merge conflicts
✅	8.x

Note: Successful backport PRs will be merged automatically after passing CI.

Manual backport

To create the backport manually run:

node scripts/backport --pr 188243

Questions ?

Please refer to the Backport tool documentation

[kibanamachine]

💚 All backports created successfully

Status	Branch	Result
✅	8.x

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation