Error with details of a log entry since upgrade to 8.14

Problem description

I've been experiencing issues with my ELK stack since upgrading to version 8.14.0 from 8.13.4
In Kibana, under Observability > Stream Logs > Stream logs, when I attempt to view the details of a log entry, I encounter the following error:

Error while searching the log entry

Failed to validate: in : undefined does not match expected type { total: number, successful: number, skipped: number, failed: number } in : undefined does not match expected type Partial<{ failures: Array<Partial<{ index: (string | null), node: (string | null), reason: Partial<{ reason: (string | null), type: (string | null) }>, shard: number }>> }> in timed_out: undefined does not match expected type boolean in took: undefined does not match expected type number in hits: undefined does not match expected type { hits: Array<({ _index: string, _id: string } & { sort: [string, number] } & Partial<{ fields: { [K in string]: JsonArray } }>)> }

Extra information

In Discover, the logs appear correctly and I can see the details.
Everything else seems to be functioning properly.

Stack configuration

Docker setup

$ docker version

Client: Docker Engine - Community
 Version:           26.1.4
 API version:       1.45
 Go version:        go1.21.11
 Git commit:        5650f9b
 Built:             Wed Jun  5 11:29:22 2024
 OS/Arch:           linux/amd64
 Context:           default

Server: Docker Engine - Community
 Engine:
  Version:          26.1.4
  API version:      1.45 (minimum version 1.24)
  Go version:       go1.21.11
  Git commit:       de5c9cf
  Built:            Wed Jun  5 11:29:22 2024
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.6.33
  GitCommit:        d2d58213f83a351ca8f528a95fbd145f5654e957
 runc:
  Version:          1.1.12
  GitCommit:        v1.1.12-0-g51d5e94
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

$ docker compose version

Docker Compose version v2.27.1

$ docker-compose logs

No notable, relevant, or unusual logs in docker-compose logs

Hello,

Same error here, but from 8.13.1 to 8.14.0
We haven't found anything to fix this problem.

We are hoping a fix from Elastic Team soon.

I suspected Logstash of being responsible.
However, I have the same issue in another environment, updating from 8.13.4 to 8.14.0 as well, except that Logstash is not used at all in this installation.

I tested downgrading and rebuilding the image, but the problem persists.
If I press 'retry' 4-5 times under the error message, the details finally appear as expected.

I'm running out of ideas for debugging

Hey everyone,

this is a known issue in 8.14. We've merged a fix for 8.15 and are trying to make it available for the next 8.14 patch release too. It's not related to Logstash, but a timing issue in the request to Elasticsearch.