Fixed issue #2260 where attributes for DynamoDB were not added becaus… (

#2272)

* Fixed issue #2260 where attributes for DynamoDB were not added because of a wrong name in the servicemap.

* ran make precommit

Co-authored-by: Tyler Yahn <MrAlias@users.noreply.github.com>

CHANGELOG.md

@@ -26,6 +26,7 @@ This project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.htm
   This makes `4xx` response codes to not be an error anymore. (#1973)
 - Fixed jaegerremote sampler not behaving properly with per operation strategy set. (#2137)
 - Stopped injecting propagation context into response headers in otelhttp. (#2180)
+- Fix issue where attributes for DynamoDB were not added because of a string miss match. (#2272)
 
 ## [1.6.0/0.31.0] - 2022-03-28
 

instrumentation/github.com/aws/aws-sdk-go-v2/otelaws/attributes.go

@@ -17,6 +17,8 @@ package otelaws // import "go.opentelemetry.io/contrib/instrumentation/github.co
 import (
 	"context"
 
+	"github.com/aws/aws-sdk-go-v2/service/dynamodb"
+
 	v2Middleware "github.com/aws/aws-sdk-go-v2/aws/middleware"
 	"github.com/aws/smithy-go/middleware"
 
@@ -32,7 +34,7 @@ const (
 )
 
 var servicemap = map[string]AttributeSetter{
-	"dynamodb": DynamoDBAttributeSetter,
+	dynamodb.ServiceID: DynamoDBAttributeSetter,
 }
 
 // OperationAttr returns the AWS operation attribute.

instrumentation/github.com/aws/aws-sdk-go-v2/otelaws/dynamodbattributes.go

@@ -25,7 +25,7 @@ import (
 	semconv "go.opentelemetry.io/otel/semconv/v1.10.0"
 )
 
-// DynamoDBAttributeSetter sets DynamoDB specific attributes depending on the the DynamoDB operation being performed.
+// DynamoDBAttributeSetter sets DynamoDB specific attributes depending on the DynamoDB operation being performed.
 func DynamoDBAttributeSetter(ctx context.Context, in middleware.InitializeInput) []attribute.KeyValue {
 	dynamodbAttributes := []attribute.KeyValue{semconv.DBSystemKey.String("dynamodb")}