[Infra UI] Remove configurable fields from settings.

[simianhacker]

Currently in the Infra & Logging UI users can configure the fields we use for host, pod, and containers. This seemed like a good idea at the beginning of the project before ECS was fully implemented. As soon as we realized that the we needed to use kubernetes.pod.uid for the identifier and kubernetes.pod.name for the display name, the configurable fields became problematic. Do we make every field we use configurable? Or should the user massage their data to conform to ECS at ingestion?

The purpose of ECS was to create a schema that enables cross linking and making intelligent decisions about how fields relate to each other. Once we start changing fields then we have to come up with a schema of identifiers on top of ECS; this increases the complexity in favor of configurability and erodes the value of ECS.

I purpose we remove the ability to configure the aforementioned fields and solely rely on ECS. This would be a breaking change and the earliest we could do this is for 8.0, the next major release.

@tbragin @elastic/infra-logs-ui

Related Issues

• [Infra UI] Make the displayed node title configurable [Infra UI] Make the displayed node title configurable #41449

[weltenwort]

This also applies to the Logs UI, I would say.

[jasonrhodes]

At the very least I'd prefer to make this kind of thing a deeper setting that only advanced users are told how to do, rather than leading people into doing it more frequently because we made it so easy. I agree that ECS feels like a really good target to build toward/optimize our curated UI experiences for, provided we don't break the experience for other users.