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

AWS span.resource does not give a meaningful insight on service page #374

Closed
jfrancoist opened this issue Mar 20, 2018 · 4 comments
Closed
Labels
feature-request A request for a new feature or change to an existing one integrations Involves tracing integrations
Milestone

Comments

@jfrancoist
Copy link
Contributor

When using the current :aws instrumentation. We get the following resource

image

I think it would make more sense to have the name of the AWS command listed here instead. Which would result finding out which command is performing poorly instead of having to go through each trace on the next screen?

image

This line: https://github.com/DataDog/dd-trace-rb/blob/master/lib/ddtrace/contrib/aws/instrumentation.rb#L31 could change to

span.resource = context.safely(:resource)

making the service page show a list of AWS command in the format [aws_service].[method] e.g s3.head_object

And maybe https://github.com/DataDog/dd-trace-rb/blob/master/lib/ddtrace/contrib/aws/instrumentation.rb#L30 to

span.name = RESOURCE
@delner
Copy link
Contributor

delner commented Mar 20, 2018

From a quick 2 minute look, this seems reasonable and could address your issue. Will take a deeper look at this later. Thanks for bringing it up!

@jfrancoist
Copy link
Contributor Author

jfrancoist commented Mar 20, 2018 via email

@delner
Copy link
Contributor

delner commented Mar 21, 2018

Awesome, thanks a lot. I'll take a look!

@delner delner added integrations Involves tracing integrations feature-request A request for a new feature or change to an existing one labels Apr 9, 2018
@delner delner added this to the 0.12.1 milestone Jun 7, 2018
@delner
Copy link
Contributor

delner commented Jun 7, 2018

This should be fixed in #377 and will roll with 0.12.1, closing this issue.

@delner delner closed this as completed Jun 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request A request for a new feature or change to an existing one integrations Involves tracing integrations
Projects
None yet
Development

No branches or pull requests

2 participants