Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error with log detail after upgrade to 8.14 #997

Closed
Multitudetwo opened this issue Jun 14, 2024 · 1 comment
Closed

Error with log detail after upgrade to 8.14 #997

Multitudetwo opened this issue Jun 14, 2024 · 1 comment
Labels

Comments

@Multitudetwo
Copy link

Problem description

I've been experiencing issues with my ELK stack since upgrading to version 8.14.0
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

Container logs

$ docker-compose logs

No notable, relevant, or unusual logs in docker-compose logs
@antoineco
Copy link
Collaborator

Probably a topic more suitable for https://discuss.elastic.co, since it relates exclusively to the usage of Elastic products and not to the Docker setup itself.

@Multitudetwo Multitudetwo closed this as not planned Won't fix, can't repro, duplicate, stale Jun 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants