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

Report metrics for kuberesolver #422

Open
ecordell opened this issue Feb 17, 2022 · 2 comments
Open

Report metrics for kuberesolver #422

ecordell opened this issue Feb 17, 2022 · 2 comments
Labels
area/observability Affects telemetry data good first issue hint/good first issue Someone new could handle this priority/2 medium This needs to be done

Comments

@ecordell
Copy link
Contributor

ecordell commented Feb 17, 2022

It's important for an operator to know that spicedb is continually receiving updated peer lists. Emit metrics that can be used to alert if the list is not updated expediently.

This may require a contribution to the upstream kuberesolver or forking the project.

@ecordell ecordell added priority/2 medium This needs to be done area/observability Affects telemetry data labels Feb 17, 2022
@vroldanbet vroldanbet added the hint/good first issue Someone new could handle this label Feb 24, 2023
@lalalalatt
Copy link

lalalalatt commented Jul 9, 2024

@ecordell I have made a patch for this issue to the upstream kuberesolver, PR: kuberesolver#52

@ecordell
Copy link
Contributor Author

ecordell commented Jul 9, 2024

Awesome! We'll pull it in and test it once merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/observability Affects telemetry data good first issue hint/good first issue Someone new could handle this priority/2 medium This needs to be done
Projects
None yet
Development

No branches or pull requests

4 participants