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

Cluster MOVED response Prometheus metric #4749

Closed
andydunstall opened this issue Mar 11, 2025 · 1 comment · Fixed by #4786
Closed

Cluster MOVED response Prometheus metric #4749

andydunstall opened this issue Mar 11, 2025 · 1 comment · Fixed by #4786
Assignees
Milestone

Comments

@andydunstall
Copy link
Contributor

It would be useful to have a Prometheus metric for how many MOVED errors Dragonfly is returning

Not urgent but would be nice as querying INFO doesn't scale well when you have 10s of shards

@kostasrim
Copy link
Contributor

@adiholden @BorysTheDev

@adiholden adiholden added this to the v1.29 milestone Mar 12, 2025
mkaruza added a commit that referenced this issue Mar 17, 2025
Get number of MOVED reported errors and send as Prometheus metric.

Closes #4749

Signed-off-by: mkaruza <[email protected]>
mkaruza added a commit that referenced this issue Mar 17, 2025
Get number of MOVED reported errors and send as Prometheus metric.

Closes #4749

Signed-off-by: mkaruza <[email protected]>
mkaruza added a commit that referenced this issue Mar 17, 2025
Get number of MOVED reported errors and send as Prometheus metric.

Closes #4749

Signed-off-by: mkaruza <[email protected]>
romange pushed a commit that referenced this issue Mar 17, 2025
* feat(server): Cluster MOVED response Prometheus metric

Get number of MOVED reported errors and send as Prometheus metric.

Closes #4749

Signed-off-by: mkaruza <[email protected]>

* Update help string

---------

Signed-off-by: mkaruza <[email protected]>
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 a pull request may close this issue.

4 participants