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

Status code dashboard doesn't show internal_upstream_rq_xx #5553

Open
lahabana opened this issue Dec 23, 2022 · 5 comments
Open

Status code dashboard doesn't show internal_upstream_rq_xx #5553

lahabana opened this issue Dec 23, 2022 · 5 comments
Labels
area/observability good first issue Good for newcomers kind/bug A bug triage/accepted The issue was reviewed and is complete enough to start working on it
Milestone

Comments

@lahabana
Copy link
Contributor

What happened?

When setting up a timeout the stat that's changed is: envoy_cluster_internal_upstream_rq_xx

The status code dashboards use: envoy_cluster_external_upstream_rq_xx

So we have a weird view like:

image

We should do something better here (either sum them together or just show them differently)

@lahabana lahabana added triage/pending This issue will be looked at on the next triage meeting kind/bug A bug area/observability triage/accepted The issue was reviewed and is complete enough to start working on it and removed triage/pending This issue will be looked at on the next triage meeting labels Dec 23, 2022
@github-actions github-actions bot added the triage/pending This issue will be looked at on the next triage meeting label Dec 23, 2022
@jakubdyszkiewicz jakubdyszkiewicz removed the triage/pending This issue will be looked at on the next triage meeting label Jan 3, 2023
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Apr 4, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Apr 4, 2023

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@lahabana lahabana removed the triage/stale Inactive for some time. It will be triaged again label Apr 4, 2023
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Jul 4, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Jul 4, 2023

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@lahabana lahabana removed the triage/stale Inactive for some time. It will be triaged again label Jul 4, 2023
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Oct 3, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Oct 3, 2023

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@lahabana lahabana removed the triage/stale Inactive for some time. It will be triaged again label Oct 3, 2023
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Jan 2, 2024
Copy link
Contributor

github-actions bot commented Jan 2, 2024

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@jakubdyszkiewicz jakubdyszkiewicz added good first issue Good for newcomers and removed triage/stale Inactive for some time. It will be triaged again labels Jan 2, 2024
@lahabana lahabana added this to the backlog milestone Jan 9, 2024
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Apr 9, 2024
Copy link
Contributor

github-actions bot commented Apr 9, 2024

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@lukidzi lukidzi removed the triage/stale Inactive for some time. It will be triaged again label Apr 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/observability good first issue Good for newcomers kind/bug A bug triage/accepted The issue was reviewed and is complete enough to start working on it
Projects
None yet
Development

No branches or pull requests

3 participants