Skip to content
This repository was archived by the owner on Mar 2, 2023. It is now read-only.
This repository was archived by the owner on Mar 2, 2023. It is now read-only.

X-Ray service map and traces are not shown #60

@arun-gupta

Description

@arun-gupta

Followed the blog https://aws.amazon.com/blogs/compute/application-tracing-on-kubernetes-with-aws-x-ray/

  • Attached AWSXrayFullAccess to the IAM user
  • k8s cluster is running in us-west-2, so updated Dockerfile to download daemon from that region
  • Pushed the image to Docker Hub
  • Deployed the Daemon Set
  • Updated Helm charts by adding AWS_XRAY_DAEMON_ADDRESS
  • invoked the app, but no traces are found
  • Service name is resolvable from greeting:
sh-4.2$ ping xray-service.default
PING xray-service.default.svc.cluster.local (172.20.32.113) 56(84) bytes of data.
64 bytes from ip-172-20-32-113.us-west-2.compute.internal (172.20.32.113): icmp_seq=1 ttl=63 time=1.15 ms
64 bytes from ip-172-20-32-113.us-west-2.compute.internal (172.20.32.113): icmp_seq=2 ttl=63 time=1.36 ms
64 bytes from ip-172-20-32-113.us-west-2.compute.internal (172.20.32.113): icmp_seq=3 ttl=63 time=1.30 ms
64 bytes from ip-172-20-32-113.us-west-2.compute.internal (172.20.32.113): icmp_seq=4 ttl=63 time=1.26 ms
^C
--- xray-service.default.svc.cluster.local ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 1.156/1.274/1.367/0.088 ms

But no service map or traces are updated in the console.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions