-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
redisreceiver Add redis instance.endpoint in ResourceAttributes #33880
Comments
Pinging code owners: See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Hello @zhangjiabin1010, can you use the resource detection processor in your data pipeline to add the resource attribute you're looking for? Something like this should work. |
This seems to only detect the resource information of the machine where the collector is located. If my collector is on host:A and redis is on host:B. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners: See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners: See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Component(s)
receiver/redis
Is your feature request related to a problem? Please describe.
redisreceiver Add redisinstance.endpoint in ResourceAttributes to distinguish different database instance connections。
Describe the solution you'd like
redisreceiver Add redisinstance.endpoint in ResourceAttributes
Describe alternatives you've considered
redis.instance.endpoint=10.10.1.0:6379
Additional context
No response
The text was updated successfully, but these errors were encountered: