# Error with details of a log entry since upgrade to 8.14

**URL:** <https://discuss.elastic.co/t/error-with-details-of-a-log-entry-since-upgrade-to-8-14/361498>\
**Category:** Kibana\
**Tags:** docker\
**Created:** [June 14, 2024, 1:10pm UTC](https://discuss.elastic.co/t/error-with-details-of-a-log-entry-since-upgrade-to-8-14/361498 "2024-06-14T13:10:56Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Anywhere](https://avatars.discourse-cdn.com/v4/letter/a/3e96dc/32.png) [@Anywhere](https://discuss.elastic.co/u/Anywhere)\
**Post date:** [June 14, 2024, 1:10pm UTC](https://discuss.elastic.co/t/error-with-details-of-a-log-entry-since-upgrade-to-8-14/361498/1 "2024-06-14T13:10:56Z")

</div>

### 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:

```auto
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

```console
$ 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

```

```console
$ docker compose version

Docker Compose version v2.27.1

```

```console
$ docker-compose logs

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

```

---

<div class="post-metadata">

**Author:** ![gabe-fr](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gabe-fr/32/135336_2.png) [@gabe-fr](https://discuss.elastic.co/u/gabe-fr)\
**Post date:** [June 17, 2024, 1:40pm UTC](https://discuss.elastic.co/t/error-with-details-of-a-log-entry-since-upgrade-to-8-14/361498/2 "2024-06-17T13:40:47Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Anywhere](https://avatars.discourse-cdn.com/v4/letter/a/3e96dc/32.png) [@Anywhere](https://discuss.elastic.co/u/Anywhere)\
**Post date:** [June 21, 2024, 12:45pm UTC](https://discuss.elastic.co/t/error-with-details-of-a-log-entry-since-upgrade-to-8-14/361498/3 "2024-06-21T12:45:05Z")

</div>

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

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/f/8/f8c57823936a8106feac31913736a5a5099a0236.png)

---

<div class="post-metadata">

**Author:** ![weltenwort](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/weltenwort/32/53885_2.png) [@weltenwort](https://discuss.elastic.co/u/weltenwort)\
**Post date:** [July 8, 2024, 3:08pm UTC](https://discuss.elastic.co/t/error-with-details-of-a-log-entry-since-upgrade-to-8-14/361498/4 "2024-07-08T15:08:37Z")

</div>

Hey everyone,

this is a known issue in 8.14. We've merged a [fix](https://github.com/elastic/kibana/pull/187303) 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.