Skip to content
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

Open
zhangjiabin1010 opened this issue Jul 3, 2024 · 5 comments
Open
Labels
enhancement New feature or request receiver/redis Redis related issues Stale waiting-for-code-owners

Comments

@zhangjiabin1010
Copy link

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

@zhangjiabin1010 zhangjiabin1010 added enhancement New feature or request needs triage New item requiring triage labels Jul 3, 2024
@github-actions github-actions bot added the receiver/redis Redis related issues label Jul 3, 2024
Copy link
Contributor

github-actions bot commented Jul 3, 2024

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@crobert-1
Copy link
Member

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.

@zhangjiabin1010
Copy link
Author

你好@zhangjiabin1010,您可以使用数据管道中的资源检测处理器来添加您正在寻找的资源属性吗?类似这样的方法应该可行。

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.
The IP and port of host:B should be added to the resource attributes of the redis indicator.

Copy link
Contributor

github-actions bot commented Sep 9, 2024

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 @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

Copy link
Contributor

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 @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request receiver/redis Redis related issues Stale waiting-for-code-owners
Projects
None yet
Development

No branches or pull requests

3 participants