-
Notifications
You must be signed in to change notification settings - Fork 865
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
redis slow log metrics #67
Comments
@Colstuwjx - what do you think would be useful to export for the slow log? I could see the number of slow log entries being useful (e.g. export Thoughts? |
Yes, I agree that. Instead collecting the detail slow log CMD as "metrics" into prometheus, I'd like to scrape them into Elastic. Thanks a lot for your reply. |
i'd need a slow queries view in Grafana maybe showing the last 10 slow query. My idea would be to have a metric that would look like this:
where the values are the result of the wouldn't be hard to add this to the exporter. What do you think @oliver006 ? I'd prepare a PR for today |
I think that's something for log collection, not for metrics and therefor out of scope for the exporter. |
FYI, you can use Filebeat to export slow logs: https://www.elastic.co/blog/brewing-in-beats-read-redis-slow-logs-with-filebeat |
I think slow queries logs are really needed to be exported for prometheus. Atleast the top 10 |
As redis has slow log metrics to show the slowest CMD, we should export these to prom. Thus, grafana could show the topK slow CMD, and makes redis ops feel happy.
The text was updated successfully, but these errors were encountered: