📓 Summary

We want to provide the most insightful highlights on the Log detail flyout.

This work should research and define the sections and fields which we consider important and that we want to show to the users.

🎨 Design

🖌️ Figma file

✔️ Acceptance Criteria

Each section should show 3 entries (ordered by priority) and the +more button if more are available, but each row should only render the 3 most important fields.

Top-level fields

Basically, the same as we have now, but having the dataset on top as another badge would give immediate value to knowing the source of the log entry.

• @timestamp
• log.level
• message or result of virtual column content
• data_stream.dataset

Highlights

Service & Infrastructure

• service.name
• host.name
• trace.id
• • orchestrator.cluster.name, orchestrator.resource.id

Cloud

• cloud.provider
• cloud.region
• cloud.project.id
• • cloud.availability_zone, cloud.instance.id

Other

• log.file.path
• data_stream.namespace
• agent.name
• labels
• tags

I also thought, in case the fields are present, we could render conditionally two other sections to start for Kubernetes and Web details:

Kubernetes

• kubernetes.pod.name
• kubernetes.container.name
• kubernetes.node.hostname
• • kubernetes.pod.ip, kubernetes.pod.uid, kubernetes.namespace

Web

• url.path + url.query
• http.request.id
• http.response.status_code

This should guarantee 3 core sections (Service & Infrastructure, Cloud, Other) and additional ad-hoc fields based on the log purpose and source.