-
Notifications
You must be signed in to change notification settings - Fork 151
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
Implement mackerel-plugin-twemproxy #283
Implement mackerel-plugin-twemproxy #283
Conversation
ping. (because it passed 13 days) |
Thanks for the pull-request and sorry for the late reply. |
Thanks for the reply 😌 |
I took a look at the code and noticed you decided to skip |
Yes, I skip fragments and server_ejected_at.
Yes.
I couldn't image the graph to point those timestamp data(= タイムスタンプ値をグラフで表現するわかりやすい方法が思い浮かばなかったので、今回の実装から除外しました). Summarizing the above, I decided to skip these parameters because other users should just implement to add these when users needed appear. |
@yoheimuta
I see, that makes sense. Perhaps write a note about fragments and server_ejected_at in the README.md might be great if you don't mind. Other than that, great work! |
1ef5d02
to
11beca9
Compare
@stefafafan Thanks for the review. I wrote a note in the README.md 11beca9. |
@yoheimuta |
Thanks! |
We plan to use this plugin in production. After our test trial in production, we are sure that it's helpful for operators monitoring twemproxy(s).
In my opinion, twemproxy is a somewhat defacto standard proxy for redis and memcached, so I'm posting this PR.