-
Notifications
You must be signed in to change notification settings - Fork 877
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
RediSearch module metrics collection #942
Labels
Comments
Thanks for checking, I think that makes sense! Happy to review a PR once you're ready. |
nantiferov
added a commit
to nantiferov/redis_exporter
that referenced
this issue
Sep 10, 2024
nantiferov
added a commit
to nantiferov/redis_exporter
that referenced
this issue
Sep 11, 2024
I think PR is ready for review. Tested it manually too. |
nantiferov
added a commit
to nantiferov/redis_exporter
that referenced
this issue
Sep 19, 2024
nantiferov
added a commit
to nantiferov/redis_exporter
that referenced
this issue
Oct 29, 2024
Initially added in oliver006#953 as gauges, but usage shows that they're counters. Related: oliver006#942
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the problem
Hi,
I recently started testing RediSearch module for redis and noticed that there is no support for its metrics collection.
So I found these info commands which shows useful information about module stats:
I'm thinking would be good to add these metrics collection:
What version of redis_exporter are you running?
Please run
redis_exporter --version
if you're not sure what version you're running.Running the exporter
Not relevant, feature request.
Screenshots
Not relevant, feature request.
Additional context
I think I can implement this in a week or so by adding flag named like
check-search-module
, defaults disabled.In the future, as next step, should be possible to add per index metrics collection, where
FT._list
shows available indexes, andFT.info <index>
shows quite a lot of useful information about index stats and performance.The text was updated successfully, but these errors were encountered: