You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently redis pmda looks for a $host:$port combination for pulling the redis metrics. But it is possible that redis is using unix socket and not port like following:
@jainnikhil30 Can you share some more info about what is your use case to get the data from the socket directly?
natoscott
changed the title
[RFE] add ability to pull metrics from socket in redis pmda
[RFE] add ability to pull metrics from unix socket in redis pmda
Jan 29, 2025
@hhorak this is a mode in which redis/valkey can be run where it communicates only locally (security, efficiency) - currently the PMDA makes assumptions and is unaware of this feature.
Longer term, it would be good to rewrite this PMDA as a new (python/C) valkey PMDA, and allow Redis metrics support as a backwards-compatibility option in the updated code.
Currently redis pmda looks for a $host:$port combination for pulling the redis metrics. But it is possible that redis is using unix socket and not port like following:
redis 29103 1 0 04:05 ? 00:00:11 /usr/bin/redis-server unixsocket:/run/redis/redis.sock
With this redis pmda is not able to fetch the redis metrics. It should be able to fetch the metrics using redis.sock as well.
The text was updated successfully, but these errors were encountered: