8000 [Tempo] Does not return traces with error · Issue #8406 · kiali/kiali · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

[Tempo] Does not return traces with error #8406

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

Closed
josunect opened this issue May 9, 2025 · 1 comment · Fixed by #8407
Closed

[Tempo] Does not return traces with error #8406

josunect opened this issue May 9, 2025 · 1 comment · Fixed by #8407
Assignees
Labels
backport completed Issue PRs have been backported backport needed Issue PRs require backport to versions specified in comments bug Something isn't working

Comments

@josunect
Copy link
Contributor
josunect commented May 9, 2025

Describe the bug

When selecting the option "Show only traces with errors" no results are found:

Image

Image

Expected Behavior

Error traces should be returned correctly

What are the steps to reproduce this bug?

In minikube

  1. Install Kiali and Tempo (hack/istio/tempo/install-tempo-env.sh -c kubectl)
  2. Install bookinfo and create an Error rates traffic policy
  3. Go to a service with errors and select the "Show only traces with errors option"

Environment

Learn about how to determine versions here.

  • Kiali version: master
  • Istio version: 1.26
  • Kubernetes impl:
  • Kubernetes version:
  • Other notable environmental factors:
@josunect josunect added the bug Something isn't working label May 9, 2025
@josunect josunect self-assigned this May 9, 2025
@josunect josunect moved this from 📋 Backlog to 👀 In review in Kiali Sprint 25-08 | Kiali v2.11 May 9, 2025
@github-project-automation github-project-automation bot moved this from 👀 In review to ✅ Done in Kiali Sprint 25-08 | Kiali v2.11 May 9, 2025
@josunect josunect added the backport needed Issue PRs require backport to versions specified in comments label May 12, 2025
@josunect
Copy link
Contributor Author
josunect commented May 12, 2025

Backport to 2.4: #8409

@jshaughn jshaughn added the backport completed Issue PRs have been backported label May 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport completed Issue PRs have been backported backport needed Issue PRs require backport to versions specified in comments bug Something isn't working
Projects
Development

Successfully merging a pull request may close this issue.

2 participants
0