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

Future support of Redis or other BSD license alternatives? #898

Closed
thanh17 opened this issue Apr 9, 2024 · 2 comments
Closed

Future support of Redis or other BSD license alternatives? #898

thanh17 opened this issue Apr 9, 2024 · 2 comments
Assignees
Labels

Comments

@thanh17
Copy link

thanh17 commented Apr 9, 2024

Describe the problem
With the recent changes in redis/redis#13157, what will the future of redis_exporter support look like?

Will this come in the form of transitioning to other forked version of redis like Valkey?

What version of redis_exporter are you running?
Please run redis_exporter --version if you're not sure what version you're running.
[X] 1.x.x

Running the exporter
N/A

Screenshots
N/A

Additional context
Rip Redis 🥲

@oliver006
Copy link
Owner

Thanks for opening this issue.

Not sure how ioredis relates to all of this (copy-paste mistake?) but the exporter works on the redis protocol and as long as Redis continues to maintain backwards-compatibility with with ValKey then we should be fine.

That said, I should add something to the README that the exporter works with ValKey.

IMO the exporter should continue to support a broad set of Redis-like systems (it already does, see support for KeyDB, Tile38, etc) so we'll try to cover as much as Redis and ValKey and other functionality as possible.

@thanh17
Copy link
Author

thanh17 commented Apr 12, 2024

Yes, meant to say redis_exporter...Will look at support for KeyDB as reference, thank you!

@thanh17 thanh17 closed this as completed Apr 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants