aws/aws-xray-daemon

Issues

• Aws xray daemon got shutdown signal after some time

  #101 opened 4 years ago
  4

• Please add ARM version in ECR Public Gallery

  #100 opened 4 years ago
  1

• Does aws-xray-daemon support SamplingRules?

  #96 opened 4 years ago
  3

• Fix Log Levels

  #95 opened 4 years ago
  4

• XRAY-DAEMON Behind Load Balancer

  #94 opened 4 years ago
  4

• When I run the program, the following error appears

  #93 opened 4 years ago
  1

• Feature: Publish to ECR Public Gallery

  #83 opened 3 years ago
  9

• EC2 Windows Server - Unable to start service

  #80 opened 4 years ago
  4

• X-Ray Service map not showing call from one micro service to another AWS EKS Fargate

  #75 opened 4 years ago
  2

• Support credential profiles

  #74 opened 3 years ago
  17

• Docker on Elastic Beanstalk Not Connecting

  #71 opened 4 years ago
  8

• AWS XRay Daemon High CPU Usage

  #70 opened 4 years ago
  2

• Arm64 / Graviton2 support via multi-arch images

  #68 opened 4 years ago
  2

• Replace logging library with zap

  #67 opened 4 years ago
  2

• Only log unprocessed segments instead of entire batch

  #63 opened 4 years ago
  1

• Reduce debug logging

  #62 opened 4 years ago
  1

• Feature: Visibility into X-ray tracing libraries for other languages

  #60 opened 4 years ago
  1

• Sending segment batch failed with: NoCredentialProviders: no valid provider

  #59 opened 4 years ago
  3

• Suggestion: Guide on managing XRay as a separate service

  #58 opened 4 years ago
  2

• Add xray daemon to aws homebrew tap

  #57 opened 4 years ago
  1

• X-Ray Sampling Rules :: Error reading response

  #56 opened 5 years ago
  1

• Support config for send batch throttling?

  #55 opened 5 years ago
  3

• Single XRay Daemon in ECS Cluster not sending traces

  #53 opened 2 years ago
  20

• Cannot start the x-ray daemon on Elastic Beanstalk host.

  #50 opened 5 years ago
  2

• unable to connect Xray using Xray-daemon from a docker app

  #49 opened 4 years ago
  4

• Failed to send telemetry 6 record(s). Re-queue records. NoCredentialProviders: no valid providers in chain. Deprecated.

  #48 opened 5 years ago
  7

• X-Ray daemon not sending traces to X-Ray service

  #43 opened 5 years ago
  3

• Adding support for ECS_ENABLE_CONTAINER_METADATA and ECS_CONTAINER_METADATA_FILE

  #40 opened 4 years ago
  5

• Skipped telemetry data as no segments found

  #39 opened 5 years ago
  2

• SignatureDoesNotMatch: Signature expired

  #38 opened 5 years ago
  5

• failed to load config file - unsupported expression

  #37 opened 5 years ago
  3

• Upgrade aws go sdk version for EKS IAM Permissions

  #31 opened 5 years ago
  0

• I can't connect x-ray console via x-ray daemon by docker

  #30 opened 4 years ago
  11

• Must be run with elevated privileges

  #28 opened 5 years ago
  4

• Unable to install X-Ray daemon by systemctrl in Ubuntu 18.04

  #27 opened 5 years ago
  2

• Lambda in VPC

  #26 opened 5 years ago
  8

• Support TCP only Segment document transfers

  #25 opened 6 years ago
  3

• Single X-ray Daemon for Multiple Containers

  #24 opened 4 years ago
  20

• Unable to see X-RAY traces

  #23 opened 6 years ago
  3

• SerializationError: failed decoding REST JSON error response

  #22 opened 4 years ago
  8

• Definition of "spilling over"

  #17 opened 6 years ago
  3

• Windows could not start the AWSXrayDaemon service on Local Computer

  #16 opened 6 years ago
  23

• Provide statically linked binary (CGO_ENABLED=0) to allow smaller docker containers.

  #15 opened 4 years ago
  5

• Lambda config support

  #14 opened 6 years ago
  3

• Rename the "daemon" directory to "xray"

  #13 opened 6 years ago
  1

• Support "NO_PROXY" args

  #12 opened 6 years ago
  2

• Consuming high amounts of memory?

  #11 opened 6 years ago
  7

• Add health endpoint

  #9 opened 7 years ago
  15

• Failed to start X-Ray Daemon

  #8 opened 6 years ago
  13

• Daemon starts before network is available

  #5 opened 7 years ago
  6