Skip to content

[8.15] host.name is empty we need to use host.hostname (#678)#679

Merged
salvatore-campagna merged 1 commit intoelastic:8.15from
salvatore-campagna:backport/8.15/pr-678
Sep 24, 2024
Merged

[8.15] host.name is empty we need to use host.hostname (#678)#679
salvatore-campagna merged 1 commit intoelastic:8.15from
salvatore-campagna:backport/8.15/pr-678

Conversation

@salvatore-campagna
Copy link
Contributor

Backport

This is an automatic backport to 8.15 of:

Questions ?

Please refer to the Backport tool documentation

If the `host.name` field does not exists, indices created as backing indices of a data stream
are injected with empty values of `host.name`. Sorting on `host.name` and `@timestamp`
results in sorting just on `@timestamp`. Looking at some mappings I see a `host.hostname`
exists. Also a cardinality aggregation results in hundreds of distinct values which suggests
the filed is not empty.

We would like to test using a meaningful combination of fields to sort on. Ideally we expect
better benchmark results despite being possible that other, more effective, combinations of
fields might exist. We are interested, anyway, in changes over time **given a valid set of fields
to sort on**.

(cherry picked from commit 0ca00a0)
@salvatore-campagna salvatore-campagna merged commit cf817c7 into elastic:8.15 Sep 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Comments