Luke Elmers

In Kibana's logging system, we use TypeScript to prevent situations like this (we have a set of [typedefs for ECS](https://github.com/elastic/kibana/blob/12b245c4e50555c227d569bc54bc64118bd15558/packages/kbn-logging/src/ecs/index.ts) exposed from core). TS will prevent folks from providing any...

We should look into a few things: - Would upstream hapi consider this a bug that could be fixed? - How are these errors not getting properly surfaced? - Can...

> can we patch this on our side sooner than later? @dgieselaar I'm hoping to have this addressed in the next 3 weeks -- we are meeting on Tuesday to...

Lowering the impact on this issue as the short term solution in https://github.com/elastic/kibana/pull/141350 has unblocked the dev experience for now.

> (TIL we already have a serverless.yaml config file on main, but anyway) Yeah, added in https://github.com/elastic/kibana/pull/149878 > what are the upsides of having such serverless-specific 'basic' (understand: also usable...

As I was thinking about this, one downside that does come to mind is that this would be a less optimal DX for folks running Kibana from source. Devs using...

> @lukeelmers, do you know if this is a requirement for Serverless or Docker images in general? I don't think this is a requirement for serverless right now. We are...

Seeing that: - there don't seem to be plans to change anything on the ES side; - it is acknowledged that defaulting to pattern layout in stdout is a better...

Okay, I will go ahead and close this for now then and we can reopen if we have reason to change our minds later.

I just wanted to jump in with a naive question before we merge this - I'm guessing that the main reason for these `xpack.features` yml configs being "aware" of the...