o11y update

[rh-tap-build-team]

Included PRs:

• fix(SPRE-4557)API Server dashboard improvement o11y#1006
• fix(SPRE-4570) Konflux namespace dashboard improvement o11y#1010

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: rh-tap-build-team[bot]
Once this PR has been reviewed and has the lgtm label, please assign ifireball for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• components/monitoring/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[github-actions]

🤖 Gemini AI Assistant Available

Hi @rh-tap-build-team[bot]! I'm here to help with your pull request. You can interact with me using the following commands:

Available Commands

• @gemini-cli /review - Request a comprehensive code review

  • Example: @gemini-cli /review Please focus on security and performance

• @gemini-cli <your question> - Ask me anything about the codebase

  • Example: @gemini-cli How can I improve this function?
  • Example: @gemini-cli What are the best practices for error handling here?

How to Use

1. Simply type one of the commands above in a comment on this PR
2. I'll analyze your code and provide detailed feedback
3. You can track my progress in the workflow logs

Permissions

Only OWNER, MEMBER, or COLLABORATOR users can trigger my responses. This ensures secure and appropriate usage.

---

This message was automatically added to help you get started with the Gemini AI assistant. Feel free to delete this comment if you don't need assistance.

[github-actions]

🤖 Hi @rh-tap-build-team[bot], I've received your request, and I'm working on it now! You can track my progress in the logs for more details.

[konflux-ci-qe-bot]

🤖 Pipeline Failure Analysis

Category: Infrastructure

The pipeline failed because the e2e test step was unable to retrieve pull request information from the GitHub API, encountering a 502 Bad Gateway error.

📋 Technical Details

Immediate Cause

The appstudio-e2e-tests/redhat-appstudio-e2e step failed to execute because it received a 502 Bad Gateway status code from the GitHub API when attempting to access the pull request URL https://api.github.com/repos/redhat-appstudio/infra-deployments/pulls/10635.

Contributing Factors

The 502 Bad Gateway error suggests an issue external to the test execution itself, potentially related to the GitHub API service, an intermediate proxy/gateway, or network connectivity between the CI environment and GitHub. No internal cluster or service issues were identified in the additional_context as contributing factors.

Impact

This error directly prevented the e2e test execution from starting or continuing, as critical information required for the test run (pull request details) could not be retrieved, leading to an immediate failure of the redhat-appstudio-e2e step and the overall pipeline.

🔍 Evidence

appstudio-e2e-tests/redhat-appstudio-e2e

Category: infrastructure
Root Cause: The process failed to retrieve pull request information from the GitHub API due to a 502 Bad Gateway error. This error indicates a problem with the GitHub API service, a proxy/gateway, or network connectivity between the CI environment and GitHub.

Logs:

artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/build-log.txt

Error: cannot get remote name and branch name for PR URL "https://api.github.com/repos/redhat-appstudio/infra-deployments/pulls/10635": unexpected status code: 502, response body: bad gateway

---

Analysis powered by prow-failure-analysis | Build: 2025953755236667392

[openshift-ci]

@rh-tap-build-team[bot]: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/appstudio-e2e-tests	d8fa31d	link	true	/test appstudio-e2e-tests

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.