-
Notifications
You must be signed in to change notification settings - Fork 107
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
Does it work with "mcrouter"? #113
Comments
I have the same problem. In my log is:
|
Do you know which stats commands are supported by mcrouter? I haven't been using it for years, if it only requires simple changes to be supported I'm happy to provide some guidance on making these changes. |
It should be simple enough to support, some details are on the mcrouter wiki: |
I did some digging, it looks like mcrouter doesn't support |
In order to support mcrouter, add a flag to disable the collection of "STATS SETTINGS". Fixes: #113 Signed-off-by: SuperQ <[email protected]>
It also turns out that mcrouter doesn't support |
In order to support mcrouter, add a flag to disable the collection of "STATS SETTINGS". Fixes: #113 Signed-off-by: SuperQ <[email protected]>
Presumably you would still want metrics from the individual memcached instances. Is there a way for the exporter to tell whether it's talking to mcrouter or memcached proper? How would you tell from metrics? A simple thing I can imagine would be "router mode" for the exporter ( |
What is the use case for using the memached exporter via mcrouter? There is a mcrouter exporter that can be used https://github.com/Dev25/mcrouter_exporter or you can run the memcached exporter on each memcached server and connect directly rather than going through mcrouter. |
The idea is that we could have one exporter that does both. I looked at the mcrouter_exporter, it has a bit of a manual implementation of the protocol. |
Does "memcached_exporter" work with "mcrouter"?
I am using the following config to mcrouter:
Metric
memcached_up
is always 0The text was updated successfully, but these errors were encountered: