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

storage: only fetch metrics for managed clusters/hosts #17240

Conversation

aljoscha
Copy link
Contributor

Motivation

Fixes #17187

Checklist

  • This PR has adequate test coverage / QA involvement has been duly considered.

  • This PR evolves an existing $T ⇔ Proto$T mapping (possibly in a backwards-incompatible way) and therefore is tagged with a T-proto label.

  • If this PR will require changes to cloud orchestration, there is a
    companion cloud PR to account for those changes that is tagged with
    the release-blocker label (example).

  • This PR includes the following user-facing behavior changes:

@aljoscha aljoscha requested a review from guswynn January 20, 2023 14:37
@aljoscha aljoscha requested a review from a team as a code owner January 20, 2023 14:37
Copy link
Contributor

@guswynn guswynn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good! thanks for fixing this!

@aljoscha
Copy link
Contributor Author

With recent changes during the "cluster unification" work this code changed and we now do the correct thing:

let metrics_task = mz_ore::task::spawn(|| format!("replica-metrics-{replica_id}"), {

@aljoscha aljoscha closed this Jan 23, 2023
@aljoscha aljoscha deleted the storage-fix-metrics-for-remote-clusters branch January 23, 2023 13:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

regression: Logs fill up with "error fetching metrics for u3: unknown service u3"
2 participants