Include additional fields for summary column by thomheymann · Pull Request #213687 · elastic/kibana

thomheymann · 2025-03-10T09:03:59Z

Resolves #196513

Summary

Updates fields in Discover summary column.

Logic

remove

cloud.instance.id 
orchestrator.namespace

In addition we need to implement some logic to have a fallback, selecting the first field with a value in descending order:

Add fallback mechanism to container.name

kubernetes.container.name => k8s.container.name => container.name

Add fallback mechanism to host.name

kubernetes.node.name => k8s.node.name => host.name

Add fallback mechanism to cluster.name

orchestrator.cluster.name => k8s.cluster.name

Add new fields with fallbacks

kubernetes.namespace => (k8s.namespace.name)
kubernetes.pod.name => (k8s.pod.name)

// only one of these will be present in a single doc:
kubernetes.deployment.name => (k8s.deployment.name)
kubernetes.replicaset.name => (k8s.replicaset.name)
kubernetes.statefulset.name => (k8s.statefulset.name)
kubernetes.daemonset.name => (k8s.daemonset.name)
kubernetes.job.name => (k8s.job.name)
kubernetes.cronjob.name => (k8s.cronjob.name)

…include-additional-fields-for-summary-column

...-contextual-components/src/data_types/logs/components/summary_column/summary_column.test.tsx

elasticmachine · 2025-03-12T13:36:17Z

💚 Build Succeeded

Buildkite Build
Commit: 97163e4

Metrics [docs]

Async chunks

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

id	before	after	diff
`discover`	959.1KB	959.6KB	+532.0B
`unifiedDocViewer`	204.8KB	204.7KB	-82.0B
total			+450.0B

History

💚 Build #283081 succeeded 3626bd4

yngrdyn

LGTM, well tested and neat solution 🚀

akowalska622

LGTM ✅

kibanamachine · 2025-03-13T11:26:16Z

Starting backport for target branches: 9.0

https://github.com/elastic/kibana/actions/runs/13833481430

kibanamachine · 2025-03-13T11:31:42Z

💔 All backports failed

Status	Branch	Result
❌	9.0	Backport failed because of merge conflicts You might need to backport the following PRs to 9.0: - [Discover] Exclude Elasticsearch metadata fields from Display in Content Column (#213255)

Manual backport

To create the backport manually run:

node scripts/backport --pr 213687

Questions ?

Please refer to the Backport tool documentation

kibanamachine · 2025-03-14T11:48:49Z

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 213687 locally

gbamparop · 2025-03-14T14:01:42Z

@thomheymann this should just be backported to 8.19 right?

kibanamachine · 2025-03-17T12:48:44Z

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 213687 locally

kibanamachine · 2025-03-18T12:49:35Z

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 213687 locally

kibanamachine · 2025-03-19T12:53:08Z

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 213687 locally

kibanamachine · 2025-03-20T13:48:49Z

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 213687 locally

kibanamachine · 2025-03-21T13:49:01Z

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 213687 locally

Resolves elastic#196513 ## Summary Updates fields in Discover summary column. ## Logic remove ``` cloud.instance.id orchestrator.namespace ``` In addition we need to implement some logic to have a fallback, selecting the first field with a value in descending order: Add fallback mechanism to container.name ``` kubernetes.container.name => k8s.container.name => container.name ``` Add fallback mechanism to host.name ``` kubernetes.node.name => k8s.node.name => host.name ``` Add fallback mechanism to cluster.name ``` orchestrator.cluster.name => k8s.cluster.name ``` Add new fields with fallbacks ``` kubernetes.namespace => (k8s.namespace.name) kubernetes.pod.name => (k8s.pod.name) // only one of these will be present in a single doc: kubernetes.deployment.name => (k8s.deployment.name) kubernetes.replicaset.name => (k8s.replicaset.name) kubernetes.statefulset.name => (k8s.statefulset.name) kubernetes.daemonset.name => (k8s.daemonset.name) kubernetes.job.name => (k8s.job.name) kubernetes.cronjob.name => (k8s.cronjob.name) ```

kibanamachine · 2025-03-24T13:50:22Z

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 213687 locally

kibanamachine · 2025-03-25T14:49:04Z

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 213687 locally

kibanamachine · 2025-03-27T15:49:36Z

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 213687 locally

kibanamachine · 2025-03-28T16:49:10Z

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 213687 locally

Resolves elastic#196513 ## Summary Updates fields in Discover summary column. ## Logic remove ``` cloud.instance.id orchestrator.namespace ``` In addition we need to implement some logic to have a fallback, selecting the first field with a value in descending order: Add fallback mechanism to container.name ``` kubernetes.container.name => k8s.container.name => container.name ``` Add fallback mechanism to host.name ``` kubernetes.node.name => k8s.node.name => host.name ``` Add fallback mechanism to cluster.name ``` orchestrator.cluster.name => k8s.cluster.name ``` Add new fields with fallbacks ``` kubernetes.namespace => (k8s.namespace.name) kubernetes.pod.name => (k8s.pod.name) // only one of these will be present in a single doc: kubernetes.deployment.name => (k8s.deployment.name) kubernetes.replicaset.name => (k8s.replicaset.name) kubernetes.statefulset.name => (k8s.statefulset.name) kubernetes.daemonset.name => (k8s.daemonset.name) kubernetes.job.name => (k8s.job.name) kubernetes.cronjob.name => (k8s.cronjob.name) ``` (cherry picked from commit 37c88f9) # Conflicts: # src/platform/packages/shared/kbn-discover-utils/src/data_types/logs/constants.ts # src/platform/packages/shared/kbn-discover-utils/src/data_types/logs/utils/get_available_resource_fields.ts

thomheymann · 2025-03-31T15:37:34Z

💚 All backports created successfully

Status	Branch	Result
✅	9.0
✅	8.x

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

Questions ?

Please refer to the Backport tool documentation

Resolves elastic#196513 ## Summary Updates fields in Discover summary column. ## Logic remove ``` cloud.instance.id orchestrator.namespace ``` In addition we need to implement some logic to have a fallback, selecting the first field with a value in descending order: Add fallback mechanism to container.name ``` kubernetes.container.name => k8s.container.name => container.name ``` Add fallback mechanism to host.name ``` kubernetes.node.name => k8s.node.name => host.name ``` Add fallback mechanism to cluster.name ``` orchestrator.cluster.name => k8s.cluster.name ``` Add new fields with fallbacks ``` kubernetes.namespace => (k8s.namespace.name) kubernetes.pod.name => (k8s.pod.name) // only one of these will be present in a single doc: kubernetes.deployment.name => (k8s.deployment.name) kubernetes.replicaset.name => (k8s.replicaset.name) kubernetes.statefulset.name => (k8s.statefulset.name) kubernetes.daemonset.name => (k8s.daemonset.name) kubernetes.job.name => (k8s.job.name) kubernetes.cronjob.name => (k8s.cronjob.name) ``` (cherry picked from commit 37c88f9) # Conflicts: # src/platform/packages/shared/kbn-discover-utils/src/data_types/logs/constants.ts # src/platform/packages/shared/kbn-discover-utils/src/data_types/logs/utils/get_available_resource_fields.ts

kibanamachine · 2025-03-31T17:48:50Z