Closed ashishthakur55525 closed 1 week ago
Debug mode output:
$ ./redis_exporter --debug
INFO[0000] Redis Metrics Exporter v1.58.0 build date: 2024-03-06-10:50:36 sha1: 99ff138684a6726b5d589401b1b28f7bccdb2f97 Go: go1.22.1 GOOS: linux GOARCH: amd64
DEBU[0000] Enabling debug output
DEBU[0000] NewRedisExporter options: exporter.Options{User:"", Password:"<password>", Namespace:"redis", PasswordMap:map[string]string{}, ConfigCommandName:"CONFIG", CheckKeys:"", CheckSingleKeys:"", CheckStreams:"", CheckSingleStreams:"", CheckKeysBatchSize:1000, CheckKeyGroups:"", MaxDistinctKeyGroups:100, CountKeys:"", LuaScript:map[string][]uint8(nil), ClientCertFile:"", ClientKeyFile:"", CaCertFile:"", InclConfigMetrics:false, DisableExportingKeyValues:false, RedactConfigMetrics:true, InclSystemMetrics:false, SkipTLSVerification:false, SetClientName:true, IsTile38:false, IsCluster:false, ExportClientList:false, ExportClientsInclPort:false, ConnectionTimeouts:15000000000, MetricsPath:"/metrics", RedisMetricsOnly:false, PingOnConnect:false, RedisPwdFile:"", Registry:(*prometheus.Registry)(0xd1b980), BuildInfo:exporter.BuildInfo{Version:"v1.58.0", CommitSha:"99ff138684a6726b5d589401b1b28f7bccdb2f97", Date:"2024-03-06-10:50:36"}}
DEBU[0000] parseKeyArg(): Got empty key arguments, parsing skipped
DEBU[0000] keys: []exporter.dbKeyPair(nil)
DEBU[0000] parseKeyArg(): Got empty key arguments, parsing skipped
DEBU[0000] singleKeys: []exporter.dbKeyPair(nil)
DEBU[0000] parseKeyArg(): Got empty key arguments, parsing skipped
DEBU[0000] streams: []exporter.dbKeyPair(nil)
DEBU[0000] parseKeyArg(): Got empty key arguments, parsing skipped
DEBU[0000] singleStreams: []exporter.dbKeyPair(nil)
DEBU[0000] parseKeyArg(): Got empty key arguments, parsing skipped
DEBU[0000] countKeys: []exporter.dbKeyPair(nil)
INFO[0000] Providing metrics at :9121/metrics
DEBU[0000] Configured redis addr: "redis://<myredisURL>.cache.amazonaws.com:6379"
FATA[0000] Server error: listen tcp :9121: bind: address already in use
@oliver006 any chance were you able to look into this issue?
Not yet.
Not yet.
sure, please let me know if you have any update? Also is my configuration correct?
@oliver006 i think you can close this out, i was able to scrape AWS managed redis using servicemonitor deployment, and enabling TLS.
Describe the problem Redis exporter not able to scrape metrics from AWS managed Elasticache (redis) cluster. We are running redis exporter in AWS EKS cluster which should pull data from AWS managed(redis cluster). As per Github documentation (https://github.com/oliver006/redis_exporter?tab=readme-ov-file) added both redis URL as well exporter endpoint to prometheus scraping configuration (prometheus.yml). But I was able to get metrics (below) from exporters endpoint and from redis instance target, which looks like default metrics, nothing much.
What version of redis_exporter are you running? Please run
redis_exporter --version
if you're not sure what version you're running.Redis version: 5.x
Running the exporter What's the full command you're using to run the exporter? (please remove passwords and other sensitive data) Please include details about env variables, command line parameters, your orchestration setup, etc.
Here are the env variable I used in exporter values.yaml file.
redisAddress: redis://<myredisURL>.cache.amazonaws.com:6379
Configuration form prometheus.yaml
Screenshots If applicable, add screenshots to help explain your question. this is screenshot from prometheus targets.
Additional context
What we need to do to make redis (AWS managed) scraped from EKS cluster running exporter, how to get custom metrics published, adding targets to promtheus.yaml how its gonna scrape it, can we use servicemonitor instead ro scrape it, are there two endpoints /scrape & /metrics?