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 SDK request id is using aws.requestId instead of aws.request_id defined by semantic conventions #894

Open
pingleig opened this issue Sep 23, 2024 · 3 comments

Comments

@pingleig
Copy link
Member

This should be issue in upstream https://github.com/open-telemetry/opentelemetry-java-instrumentation but there are too many issues in upstream so creating one here first so people are aware of it.

In semantic convention registry, the attribute name for request id is aws.request_id schema, while the SDK generated spans are using aws.requestId from Application Signals Sample App

{
        "aws.local.service": "vets-service-java",
        "EC2.AutoScalingGroup": "eks-ng-171f7929-8cc8d89a-078d-578b-2510-f05a45ce860e",
        "net.peer.port": 443,
        "rpc.service": "S3",
        "http.url": "https://s3.amazonaws.com/",
        "Host": "ip-192-168-13-119.ec2.internal",
        "rpc.system": "aws-api",
        "thread.name": "http-nio-8083-exec-6",
        "aws.remote.service": "AWS::S3",
        "aws.remote.operation": "ListBuckets",
        "aws.local.environment": "eks:midlina-otel/default",
        "K8s.Namespace": "default",
        "aws.local.operation": "GET /vets",
        "http.status_code": 200,
        "net.peer.name": "s3.amazonaws.com",
        "aws.span.kind": "CLIENT",
        "rpc.method": "ListBuckets",
        "aws.agent": "java-aws-sdk",
        "EC2.InstanceId": "i-0c649a0824e24ede9",
        "EKS.Cluster": "midlina-otel",
        "PlatformType": "AWS::EKS",
        "aws.requestId": "Z4GPNP2V7J4VSQXP", // requestId
        "http.method": "GET",
        "thread.id": 48
 }

Both v1 and v2 SDK in upstream repo are using aws.requestId

@pingleig
Copy link
Member Author

Created issue in upstream open-telemetry/opentelemetry-java-instrumentation#12311

@pingleig
Copy link
Member Author

pingleig commented Oct 9, 2024

Fixed in open-telemetry/opentelemetry-java-instrumentation#12352 in upstream might need to update tests when pulling upstream change.

@pxaws
Copy link
Member

pxaws commented Oct 17, 2024

I think we have a couple of places referring to this field

https://github.com/aws-observability/aws-otel-java-instrumentation/blob/main/.github/patches/opentelemetry-java-instrumentation.patch#L192

We need to take care of the changes when updating dependencies.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants