-
Notifications
You must be signed in to change notification settings - Fork 33
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
Support lettuce latency metrics #121
Comments
Not yet, but of course PRs welcome :) |
Sure! I'll try to come up with a draft |
@ilopmar we will need to bump the major version of the project |
Before we can bump a major version of a dependency and include it in a minor Micronaut version, we need to make sure that there are no breaking changes in that module. In case there are breaking changes we need to think carefully if they will accept users' applications and how. I see that the PR with the upgrade pass all the test, that's a good start :-) Another thing that we need to test before the upgrade is the GraalVM integration. We already have a test application so we need to use it and make sure everything still works. Yes, you can start working on that and we could include a major version of this module in Micronaut 2.3. |
Upgraded to Lettuce 6.0.2 in #123 and released in Micronaut Redis 4.0.0 |
@ilopmar do we support latency metrics with the upgrade? I guess that was the original issue |
No, there is nothing built-it for doing that. I though it was only a matter of upgrading to 6.0. |
Hi all!
Are there any plans to support lettuce command latency metrics? Shouldn't be too hard to implement using micrometer.
The text was updated successfully, but these errors were encountered: