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

Question: Way to map specific aws resources to custom names #4007

Open
viict opened this issue Jan 26, 2024 · 0 comments
Open

Question: Way to map specific aws resources to custom names #4007

viict opened this issue Jan 26, 2024 · 0 comments
Labels
integration-aws-sdk question Further information is requested

Comments

@viict
Copy link

viict commented Jan 26, 2024

One of the things I'd like to see is how all my services relates to each resource but it ends up automatically filling the service name with the service prefix append by the resource such as aws-dynamodb

Is there an way to specify the service name for each dynamodb table? So let's say if two different services use the same table it would appear a connection between both of them and the table? The current behavior is each service has it's own serviceName-aws-dynamodb link with all the different table resources.

If I understood correctly, DD_SERVICE_MAPPING will allow me to rename all {serviceName}-aws-dynamodb into just dynamodb for instance, but doesn't seem I can do that per resource name? Like DD_SERVICE_MAPPING="user-aws-dynamodb:user_table"

Also tried the DD_TRACE_PEER_SERVICE_MAPPING even though it matches correctly by the table name it doesn't work because it changes the "peer.service" instead of the root service tag.

So my tries for now:

DD_SERVICE_MAPPING="aws-sdk:dynamodb-user"

This works, but all aws-sdk plugins are replaced so doesn't work for the usecase
image

DD_TRACE_PEER_SERVICE_MAPPING="table_user_random_name_env:dynamodb-user"
image

Reading the code I couldn't find any alternative to achieve this, but the naming strategy is quite strange for me so don't know if I missed anything.

Otherwise, another approach would be to follow the dd-trace-py approach, where it sets all the dynamodb calls to "aws.dynamodb" and kinesis to "aws.kinesis"

@tlhunter tlhunter added question Further information is requested integration-aws-sdk labels Feb 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
integration-aws-sdk question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants